π Order Status Update (From Delivery App to Blend)
π§Ύ Description
This document describes the order_updated
event that delivery platforms send to Blend
when an order's delivery status is updated β e.g., assigned to a driver, out for delivery, or marked as delivered.
Blend uses this to update the order's progress in the merchant dashboard and notify staff accordingly.
π Direction
Delivery App β Blend
The delivery partner sends this event to a webhook URL provided by Blend.
π Webhook Endpoint
Blend will issue a secure webhook URL per partner/tenant.
Example:
POST https://api.tryblend.net/webhooks/order-status
π¦ Example Payload
{
"event": "order_updated",
"event_time": "2025-01-01 00:00:00",
"branch_id": "14589",
"payload": {
"order_id": "order_id",
"status": "assigned"
}
}
π Field Descriptions
Field | Description |
---|---|
event | Always "order_updated" |
event_time | ISO timestamp of status update |
branch_id | The branch receiving the order |
payload.order_id | Unique order ID |
payload.status | Current delivery status (see below) |
π¦ Accepted Status Values
Status | Description |
---|---|
assigned | A driver has been assigned to this order |
at_pick_up | Driver has arrived at the pickup location |
on_the_way | Driver has left and is heading to the customer |
cancelled | Order has been canceled mid-delivery |
delivered | Order has been successfully delivered |
π Webhook Behavior
- The delivery app sends a
POST
with the above payload - Blend processes and links the update to the internal order record
π§Ύ Response from Blend
β
Success
{
"status": "success"
}
β Failure
{
"status": "failed"
}
- A failed response usually means the order wasn't found or validation failed
β
Notes
- The
order_id
must match an existing order received viaorder_created
- Delivery partners should retry failed attempts
- Blend stores all updates for tracking and auditing
Updated 22 days ago