Quick Commerce
Errors
All error responses follow a consistent envelope with an HTTP status code, a short message, and (where applicable) a structured errors object describing the offending field(s).
Code
Common Error Scenarios
| HTTP Status | Scenario | Applicable API |
|---|---|---|
| 400 | Edit attempted after shipment picked up | Order Update |
| 400 | Cancel attempted after rider entered customer geofence / order delivered | Cancel Order |
| 400 | Invalid store unique_code, or missing where your account requires one | Create Order |
| 401 | Invalid or expired bearer token | All APIs |
| 404 | awb_number / request_id not found | Order Update, Cancel Order |
| 409 | Duplicate client_order_id for the same client | Create Order |
A complete, continuously updated error-code reference is maintained separately and will be shared with your integration POC upon request.
Glossary
| Term | Definition |
|---|---|
| AWB | Shadowfax-generated unique tracking number assigned to a shipment at order creation |
Store unique_code | Client-defined identifier for a dark store / pickup location, mapped to a Shadowfax hub |
| ETA / SLA | Estimated and promised timing windows communicated at order creation via eta_details |
| OTP | One-time password used to verify gate entry, delivery, or return receipt |
| RTS | Return To Store — shipment being returned to the originating store |
| Serviceability ID | Reference id confirming a route/pincode was validated as serviceable prior to order creation |
For integration support, please reach out to your assigned Shadowfax onboarding POC.
Last modified on