How to connect Rehbar Post to your ecommerce website
One API key, one warehouse, and one structural quirk that will confuse you for an hour if nobody explains it first.
The short version: get your API key and customer id from Rehbar Post, register a pickup warehouse, and connect. Then remember the one thing that trips people up: creating an order books nothing. Booking the shipment is a separate call, and that is what returns the AWB.
TL;DR
- • A single Bearer API key. No login, no token refresh, no expiry.
- • You also need your customer id — it goes on the create-order payload.
- • Register a pickup warehouse before booking anything.
- • Order and shipment are separate resources. Pushed is not booked.
- • No webhooks documented, so tracking is pulled on a schedule.
Step 1 — Get your API key and customer id
Rehbar Post issues a single Bearer API key per merchant. It goes in the Authorization header of every request, and that is the whole of the authentication — no login call, no refresh cycle, nothing that expires at an inconvenient moment.
You also need your customer id, which their create-order payload requires. It is easy to miss because it is not part of authentication, and its absence produces a validation error that does not obviously point at it.
Step 2 — Register a pickup warehouse
As with every aggregator, register the address you actually ship from before you try to book anything. A missing or mismatched pickup location is the number-one cause of a first booking failing, across all three of the aggregators covered on this site.
Step 3 — Order, then shipment. They are not the same call.
This is the part worth reading twice. Rehbar Post models the order and the shipment as separate resources:
- Create the order. Rehbar Post now has a record. No courier is involved, no AWB exists, nothing is booked.
- Book the forward shipment. This is the call that picks the courier and returns the AWB. Until it runs, nothing is shipping.
- Print the label and hand the parcel over. There is no separate pickup-scheduling step — booking covers it.
If you are building this yourself, model those as two visibly different states in your own data. A UI that shows 'pushed' and 'booked' as one thing will eventually tell a merchant a parcel is on its way when it is sitting in a draft state.
Step 4 — Tracking without webhooks
Rehbar Post documents no inbound webhooks, so shipment status has to be pulled from their track endpoints. The workable pattern is a scheduled job over active shipments plus a manual per-order sync for when a customer is on the phone.
Do not poll every order you have ever created. Scope the job to shipments that are actually in transit, or you will hit rate limits and get nothing.
The errors you are most likely to hit
| Symptom | Usual cause |
|---|---|
| Create order rejected as invalid | Missing customer id in the payload — it is separate from the API key. |
| Order created but nothing ships | You never booked the shipment. Creating the order books nothing. |
| Booking fails | No pickup warehouse registered, or a mismatched one. |
| Tracking never moves | Status is pulled, not pushed. Check your sync job is running and scoped to active shipments. |
| Rate limited | Polling every order rather than only shipments in transit. |
If you do not have the website yet
Everything above assumes you already have a store to connect Rehbar Post to. If you are still taking orders in Instagram DMs, that is the part worth fixing first — the integration is the easy half.
A SitesPlaced store is free to build and publish, with 0% commission on every sale, on every plan. Every integration listed on this page is included — you connect your own accounts and nobody takes a cut in the middle. You can import your catalogue straight from Instagram rather than typing products in one at a time.
On SitesPlaced the two-step model is a stepper in the order drawer, so 'pushed' and 'booked' are visibly different states rather than something you have to infer. Shiprocket and Shipmozo are included free too.
Frequently asked questions
What do I need to connect Rehbar Post?
A Bearer API key and your customer id from Rehbar Post, plus a registered pickup warehouse. The key does not expire, so there is no refresh cycle to build.
I created the order but nothing shipped. Why?
Because creating an order books nothing. Rehbar Post treats order and shipment as separate resources, and booking the forward shipment is the call that picks a courier and returns the AWB.
Do I need to schedule a pickup separately?
No. Unlike some aggregators, booking the shipment returns the AWB and covers the pickup — there is no additional scheduling step.
How does tracking work?
Rehbar Post documents no inbound webhooks, so status is pulled from their track endpoints on a schedule, with a manual sync for when you need an answer immediately.
Skip the integration work entirely
Build the store free and connect Rehbar Post, Shiprocket and Shipmozo from Settings. 0% commission on every sale, on every plan.
