Queue a clear order update for a customer.
An order system can trigger an SMS after it records a real status change. Keep the text short and direct so the recipient can recognize the order without placing payment details in the message.
Keep the message specific and brief.
Your order 482913 has shipped. Check your account for tracking updates.
This text, sender ID and phone number are illustrative. Use your own verified sender, real recipient and applicable message category. The example does not submit traffic.
Send through the documented endpoint.
Record the order event in your own system, choose the recipient and destination, then submit the send request. Review the returned batch status and subsequent delivery log separately.
The request requires a scoped Bearer key with sms:send, an active plan, an approved sender ID and enough wallet funds. The route value auto asks the account’s route selection logic to choose a suitable published route; it may still reject the request.
Authorization: Bearer YOUR_API_KEY
Idempotency-Key: 11111111-1111-4111-8111-111111111111
Content-Type: application/json
{
"to": [
"+12025550147"
],
"message": "Your order 482913 has shipped. Check your account for tracking updates.",
"sender_id": "SHOPUP",
"route": "auto",
"destination": "United States",
"operator": "all"
}Check permission and message content.
Send to the customer connected to the order, use an approved sender identity, and respect recipient preferences and opt-outs. Check the applicable destination rules and avoid promotional content in a service alert unless you have the right permission.
A successful send request queues locally. Carrier delivery requires a connected provider; review delivery logs rather than treating the API response as a receipt.