One API for every shipment
Rates, orders, booking, labels, pickups and tracking for your website, ERP or own tools, with keys you control.
The portal's jobs, as endpoints
Give each key only what it needs
Tick the permissions for this integration, for example rates and orders but not wallet. Keep the key on your server as a secret, never in browser code or a public repository. If it leaks, revoke it and it stops at once.
120 calls a minute per key. Every call logged.
Plan a queue or retries for busy moments. When something does not behave, the developer page shows the log of every call. Register a webhook so status changes are pushed to your server instead of asking repeatedly.
Three shapes of integration
Checkout asks for rates and shows Economy, Standard and Express; after payment the server creates and books the order and saves the AWB.
An approved dispatch note triggers a script that creates, books and downloads the label and commercial invoice for the warehouse to print.
Fetches tracking for up to 50 AWBs in one call and raises tickets or returns, with a key limited to just that.
Developer questions
Something else? Ask us from Support in the seller portal.
Log in to the seller portal and open Settings, then Developers. Create a key, choose its permissions and copy it when it is shown. Treat it like a password. If you lose it, make a new one and revoke the old one rather than trying to recover it.
It covers rates, orders (create, edit, cancel, book), labels, invoices, pickups, tracking, returns, NDR, customers, leads, tickets, wallet and webhooks. In short, most of what you do in the portal can be done from code, within the permissions of the key you use.
Each key can make 120 calls a minute. If you cross it, slow down and retry after a short wait. For tracking, use the call that takes up to 50 shipments at once instead of 50 separate calls, which keeps you well inside the limit.
Keep it on your server only, never in a mobile app, a web page or a shared chat. Give it the fewest permissions it needs. Every call is logged on your developer page, so you can spot odd activity, and a leaked key can be revoked at once.
Instead of asking for tracking again and again, you register a webhook and status changes are pushed to your server. This saves calls from your 120 a minute and keeps your own order status current. Your endpoint should answer quickly and handle the same event twice safely.
Ask us in the portal. Until then, take care with booking calls, because a booked order is paid from your wallet. Create and edit orders freely while they are unbooked, check the details, and only then book. Do not test with real parcels you do not intend to ship.
Yes, for some things. Key creation, team members, GSTIN and Settings live in the portal, and so do Billing, Weight disputes and Reports. Many teams use the API for booking and the portal for review and support. Settings and money questions stay there.
