🚚 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

FieldDescription
eventAlways "order_updated"
event_timeISO timestamp of status update
branch_idThe branch receiving the order
payload.order_idUnique order ID
payload.statusCurrent delivery status (see below)

🚦 Accepted Status Values

StatusDescription
assignedA driver has been assigned to this order
at_pick_upDriver has arrived at the pickup location
on_the_wayDriver has left and is heading to the customer
cancelledOrder has been canceled mid-delivery
deliveredOrder 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 via order_created
  • Delivery partners should retry failed attempts
  • Blend stores all updates for tracking and auditing