Serviceability

A reverse order has two legs — collecting from the customer, and returning the item — and both must be serviceable. Which return service to check depends on where the item goes.

Code
curl "https://dale.staging.shadowfax.in/api/v1/clients/serviceability/?service=customer_pickup&pincodes=110005,110009" \
  -H "Authorization: Token your_api_token"

Code
[
  { "code": 110009, "services": ["Regular"] },
  { "code": 110005, "services": ["Regular", "Slotted", "Surface"] }
]

The pincode being listed is not enough on its own — the tier matching your supply chain has to be present. A Regular client looks for Regular on the pickup leg and RTO/RTS on the return leg; a Surface client looks for Surface, and surface_RTO/Surface_RTS.

The full mapping of services to tiers, for both supply chains, is in Serviceability.

Coverage

Shadowfax covers 20,000+ pincodes across India, and coverage grows as hubs are added. Results are safe to cache — coverage changes infrequently.

Rejected orders

Order placement re-checks serviceability and rejects with HTTP 400, naming the failing leg:

Code
{ "message": "Failure", "errors": "Reverse order Invalid Pickup Pincode. Pickup pincode 560007 is not serviceable" }

If a leg you checked comes back green but placement still rejects it, raise it with your integration POC rather than retrying — the two checks can disagree.

See Check Serviceability in the API Reference for the full schema.