Shipments
Create a B2B or B2C shipment on a courier account and pickup location that already belong to the account. Cancel a shipment that has not been picked up.
Part of the platform
Shipping API for logistics and courier businesses
ShipRabbit is the cloud platform a logistics business uses for sellers, shipments, and connected courier accounts. The API lets that business connect its own application to the shipment, pickup, and tracking work already on the account.
When the operation lives in another system
Orders often start on a website, an ecommerce tool, a seller portal, or an internal application. The logistics desk still has to create the shipment, use a connected courier account, and know what happened next.
Copying those steps between systems is the gap. An API call keeps the shipment on the ShipRabbit account the business already runs. It does not remove the courier relationship, the seller setup, or the work of maintaining the integration.
What the API can do
These are the integration areas in the ShipRabbit developer catalog. Each call is for a seller on the account, using that seller’s API key.
Tracking
Fetch tracking for a waybill on the account. A label can be retrieved for a shipment, and proof of delivery can be requested where that shipment has it.
Warehouses and pickups
Save a warehouse or pickup location, then schedule a B2B or B2C pickup against a connected courier account.
Coverage and rates
Check stored pincode coverage for the account. Freight is calculated from the rate cards configured on the account, not from a live quote to every courier.
Status webhooks
Register a URL for shipment created, shipment status, and pickup created. The status event is sent when ShipRabbit receives a tracking update. The signing secret is shown once.
A seller API key
External calls use a seller key. An aggregator generates or rotates that key for a seller in the app. An aggregator-level key is not issued.
How a call fits the platform
- 1
Your application holds the seller API key for one seller on the ShipRabbit account.
- 2
It sends a shipment, warehouse, pickup, tracking, or coverage request for that seller.
- 3
ShipRabbit records the work on the same account the logistics team uses in the app.
- 4
Booking and tracking use a courier account already connected for that seller. The application names that courier. The API does not assign one.
- 5
The application can read tracking back, or receive shipment and pickup events at a URL it registered.
Where teams use it
An order system
Create the shipment from an order that already exists in another application, on a seller that belongs to the logistics account.
A logistics business
Connect an internal tool to the same sellers, warehouses, and courier accounts the team already runs in ShipRabbit.
A seller workflow
The key is the seller’s. An aggregator can generate it and can book for a seller on the account. The API does not create the seller record by itself.
A custom application
Any application that can send the seller key can use the same shipment, pickup, and tracking calls. Request shapes stay in the in-app catalog.
One platform, with an API on it
The API does not replace courier aggregator software . The same account still holds sellers, rate cards, tracking, COD, and NDR management . Website widgets for tracking, rates, and coverage are previewed on the tools page . Membership is on pricing .
For the developer on the account
The request catalog, key management, and webhook registration live in the ShipRabbit app for someone who already has an account. This page does not repeat those requests. Read them at API documentation in the app after signing in.
Frequently Asked Questions
What is a shipping API?
A shipping API is a way for your own application to create and follow shipments through another system. On ShipRabbit, that system is the same logistics platform the account already uses for sellers, courier accounts, and shipments.
What can I connect with ShipRabbit's API?
An application can create B2B and B2C shipments, cancel a shipment that has not been picked up, save warehouses, schedule pickups, fetch tracking for a waybill, check stored pincode coverage, and register a URL for shipment and pickup events. The calls use a seller API key.
Can I use ShipRabbit with my existing application?
Yes, if that application can send requests with the seller API key. ShipRabbit does not replace the application. It receives the shipment, warehouse, or pickup request and runs it on that seller's account.
Does ShipRabbit provide shipment tracking through its API?
Yes. A signed-in request can fetch tracking for a waybill on the account. A registered webhook can also receive a shipment status event when ShipRabbit gets a tracking update for that shipment. That does not mean every courier pushes updates the same way.
Does the API support multiple courier workflows?
A shipment is booked on a courier account already connected to that ShipRabbit account. The API does not add a courier that the account has not connected, and it does not choose the courier for you.
Who is the ShipRabbit shipping API for?
It is for the logistics business and the sellers on its account: an ecommerce or order system, an internal tool, or a custom application that needs to book and follow shipments. It is not a consumer tracking page, and it is not a separate product from the platform.
Do I need a ShipRabbit account to use the API?
Yes. Keys are issued per seller. An aggregator generates or rotates a seller key from the app. An aggregator-level key is not issued. The key is sent as an API token. The developer catalog in the app is where that account reads the request details.
Use the platform first, then connect the application
Start a 7-day trial or book a demo. The trial uses the existing aggregator registration. The API key is created later, for a seller on that account.