Order Status Template
Send a status update for a previously dispatched WhatsApp Pay order — confirm receipt, cancel, ship, refund, etc. The update is keyed by the reference_id you used when you originally sent the Order Details Carousel (or single-image variant).
Endpoint
POST https://apis.splashifypro.com/api/v1/public/messageHeaders
| Header | Value |
|---|---|
Authorization | Basic YOUR_API_KEY |
Content-Type | application/json |
Request body
{
"phoneNumber": "9999999999",
"callbackData": "",
"type": "Template",
"template": {
"name": "payment_confirmation_whatsapp_pay",
"languageCode": "en",
"bodyValues": ["200"],
"order_status": {
"reference_id": "22july25mjwapaytemp1",
"order": {
"status": "canceled",
"description": "Order failed"
}
}
}
}| Field | Required | Notes |
|---|---|---|
template.bodyValues | optional | Body variables for the template |
template.order_status.reference_id | yes | Must match the reference_id you sent earlier in the order details |
template.order_status.order.status | yes | One of processing, partially_shipped, shipped, completed, canceled |
template.order_status.order.description | optional | Free-text reason / detail shown to the customer |
Status values
status | Meaning |
|---|---|
processing | Order received, payment confirmed, being prepared |
partially_shipped | Some items dispatched, others still pending |
shipped | Fully dispatched |
completed | Delivered or fulfilled |
canceled | Cancelled — usually pair with a description explaining why |
Example
curl -X POST https://apis.splashifypro.com/api/v1/public/message \
-H "Authorization: Basic YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"phoneNumber": "9999999999",
"callbackData": "",
"type": "Template",
"template": {
"name": "payment_confirmation_whatsapp_pay",
"languageCode": "en",
"bodyValues": ["200"],
"order_status": {
"reference_id": "22july25mjwapaytemp1",
"order": { "status": "canceled", "description": "Order failed" }
}
}
}'Successful response — 201 Created
{
"result": true,
"message": "Message created successfully",
"id": "8d620ba1-640f-42ee-a8dd-15363422144b"
}Notes
- Order status updates are idempotent on
reference_id— sending the same status twice for the same order is harmless. - The customer sees the order card update in-place inside the original conversation (no new message bubble is created in some clients), so transitions feel natural.
- Combine with your fulfilment webhooks — fire
processingon payment-success,shippedwhen your courier picks up,completedon delivery.