Test Data

Staging runs at https://dale.staging.shadowfax.in/api. Use the same credentials flow as production — see Authentication.

The AWB and pincode guidance below covers Forward, Reverse, and Exchange. Hyperlocal runs on https://hlbackend.staging.shadowfax.in and ships its own sandbox endpoints for simulating order status and rider location — see the sandbox testing page in that section.

Getting a Test AWB

AWBs are scoped to your client account, so there are no shared sample AWBs — one issued to another client returns Invalid AWB Number for you. Generate your own:

• Pre-generate a batch via the AWB generation endpoint, then pass one in order_details.awb_number when placing an order, or
• Place an order without an AWB and use the awb_number that comes back.

The second is the quickest route to a trackable order:

Code
curl -X POST https://dale.staging.shadowfax.in/api/v1/clients/pickup/orders/ \
  -H "Authorization: Token your_api_token" \
  -H "Content-Type: application/json" \
  -d '{
    "customer_details": {"name":"Test Customer","contact":"9999999999","address":"123 Test Street","city":"Bangalore","pincode":560001},
    "return_details": {"return_type":"origin","name":"Warehouse","address":"456 Hub Road","pincode":560002},
    "order_details": {"client_order_id":"test_001"},
    "sku_details": [{"sku_name":"Blue T-Shirt","price":500,"return_reason":"Size mismatch"}]
  }'

The awb_number in the response is your tracking reference for every subsequent call.

Test Pincodes

Available service tiers vary by pincode, so don't assume a fixed set. A pincode that is well-formed but outside the network returns a default tier list rather than an empty result — only a malformed pincode (like 000000, which fails the 6-digit format rule) gives you [].

Staging Notes

• Staging mirrors production topology: same hub network, pincode mapping, and routing rules.
• Orders in staging do not dispatch real riders. State transitions are simulated.
• Webhooks fire on staging with the same payload format as production.
• Use client_order_id with a test_ prefix to easily identify staging orders.
• Throttling applies on staging too — expect 429 if you poll tracking tightly while testing. See Rate Limits.