Shadowfax Quick Commerce API

Order management APIs for integrating quick-commerce (dark-store / hyperlocal) clients with the Shadowfax delivery platform. All APIs are exposed via the Shadowfax unified client gateway. See the Quick Commerce guides for integration walkthroughs.

Placeholders such as <CLIENT_ID>, <STORE_UNIQUE_CODE>, and <AWB_NUMBER> must be replaced with values specific to your integration. Contact your Shadowfax integration POC for client credentials and store code mapping.

Authentication

Quick Commerce supports OAuth2 client-credentials only — Token Authentication is not available. Tokens expire after 1 hour and must be refreshed before expiry. See Authentication for the full token-exchange flow.

Code
Authorization: Bearer <access_token>

Live Order Location Sharing

In addition to the request/response APIs below, Shadowfax pushes the assigned rider's live GPS position to your registered webhook while an order is out for pickup/delivery. This is an outbound server-to-server POST from Shadowfax to the client — no request is made by the client. Each push contains a locations array and may carry multiple GPS samples for one or more AWBs; treat (awb_number, captured_time_epoch) as the dedupe key. See Live Order Location for the payload schema.

Error Format

All error responses follow a consistent envelope:

Code
{
  "message": "<short human-readable summary>",
  "errors": { "<field_name>": ["<validation message>"] }
}