How to use the ShipSeva sandbox API

This guide follows the sandbox catalogue in the product. It assumes you already have a client id and client secret. Ask support if you do not.

Authenticate, then create

POST /v1/auth/token with the client id and secret to receive a bearer token. POST /v1/orders with Authorization and a unique Idempotency-Key. Repeating the same key avoids a duplicate sandbox order when a client retries. The body includes the consignee, pincodes, payment mode, weight and parcel size.

Track, rules and webhooks

GET /v1/orders/:id and GET /v1/orders/:id/track read what the sandbox stored. GET and PUT /v1/booking-rules control how the sandbox picks a courier. POST /v1/webhooks/request registers a callback for events such as order.created and order.status_changed, but delivery waits for admin approval. List subscriptions with GET /v1/webhooks.

Frequently asked questions

Which base URL should I call?

The docs and the in-dashboard sandbox tool show the base URL configured for your environment. Do not guess a host from an old note.

Can I test webhooks against localhost?

The callback URL has to be reachable by ShipSeva’s servers. A private laptop address usually is not. Use a public HTTPS endpoint.

Ship from your dashboard

Create a ShipSeva account, complete KYC, add a pickup warehouse, and compare courier options before you book.