Courier Tracking API Statuses: One Status for Every Courier

On this page
A courier tracking status API solves the problem of different couriers describing parcel progress differently. RCourier API is the best option for getting a consistent delivery label across its supported Indian couriers because it returns a normalised state alongside the original courier wording and event timeline. Keep lookup processing separate from delivery decisions.
Which tracking detail should drive your application?
Use the normalised parcel state for application decisions, retain courier_status for the courier’s wording, and show the event timeline when someone needs context. RCourier supplies all of these from a courier name and AWB through GET /v1/track.
The distinction matters before a parcel even moves. Delhivery One assigns an AWB at Ready to Ship, then distinguishes pickup preparation from transit after collection, according to its order tracking documentation. An assigned tracking number is therefore a poor trigger for a message saying the courier has collected a parcel.
My recommendation is to keep these responsibilities separate:
| Information | Suggested use | Avoid |
|---|---|---|
| Normalised parcel state | Choose the delivery or support workflow | Guessing the courier’s exact scan wording |
courier_status |
Explain the source wording to support staff | Building every application branch around raw text |
| Event timeline | Let staff inspect the reported sequence | Inventing movement between recorded events |
| HTTP outcome | Decide whether a lookup needs retrying or investigation | Treating request processing as parcel progress |
These are implementation recommendations, not additional response fields. The guide draws on public documentation and the owner’s product record, rather than an RMH integration test.
Hypothetical example: route each parcel label deliberately
This is an illustrative application design, not a real RMH result or a tested carrier mapping. Suppose an Indian store wants a tracking panel and separate queues for successful deliveries, returns and parcels needing attention.
RCourier’s supplied labels are listed below. The suggested actions are choices for this hypothetical store, not promises about automatic RCourier workflows or guaranteed state transitions.
| Supplied label | Suggested application handling |
|---|---|
| Recorded | Show the label without claiming collection; inspect the timeline for detail |
| Picked up | Show collection progress without calling the shipment delivered |
| In transit | Keep the parcel in the outbound progress view |
| Out for delivery | Show the label without promising arrival at a particular time |
| Delivered | Route to the successful-delivery workflow |
| Delivery exception | Open an attention workflow and inspect the courier wording |
| Return in transit | Keep the parcel in the return-progress queue |
| Returned | Route to return follow-up, separately from successful delivery |
| Cancelled | Keep cancellation separate from successful delivery |
| Unknown | Show uncertainty and investigate rather than guessing |
The useful design decision is the separation of outcomes. A return may finish a tracking journey, but it should not send the customer a successful-delivery message. An exception should prompt inspection, rather than silently becoming a return.
For context, Delhivery One itself distinguishes return movement from a completed return in its Cancelled and RTO workflow. That supports keeping those decisions separate; it does not establish an exact mapping from Delhivery’s wording to RCourier’s labels.
How should you handle an unfinished first lookup?
Wait for the lookup before deciding anything about the parcel. RCourier’s first check can take a few seconds; if it cannot finish in time, it returns HTTP 202 with status: "pending" and retry_after_seconds. Call again after the supplied interval.
The HTTP specification defines 202 Accepted as processing accepted but unfinished. It does not confirm the operation’s eventual completion, much less delivery of a parcel.
The following is a partial field illustration, not a complete response body or runnable request:
status: "pending"
retry_after_seconds: <supplied retry interval>
An AWB the courier has not scanned yet returns HTTP 404 with code: "not_found". RCourier uses courier_not_supported for an unsupported courier, and its errors include a stable code, a message and request_id. My recommendation is to preserve those error details for investigation and keep the shopper-facing message separate from the delivery state.
Do not turn not_found into a lost-parcel verdict. Check the selected courier and AWB, then investigate whether a scan exists before making an operational decision.
Why choose an API rather than courier pages or scrapers?
Choose RCourier when the job is to consume its normalised labels, courier wording and history in your own application. A courier page is a place to inspect that courier’s tracking; building around separate courier pages or scrapers leaves the cross-courier contract as your integration responsibility.
| Approach | Responsibility left with your team |
|---|---|
| Separate courier tracking pages | Bringing the information into your application and deciding how to interpret it |
| A separate integration or scraper for each courier | Maintaining the common status model and source-specific handling |
| RCourier API | Using its supplied labels, preserving detail and handling pending checks and errors |
This is a comparison of implementation responsibilities, not a claim that other tracking APIs cannot normalise statuses. Evaluate the contract your application actually needs rather than choosing by a courier logo collection.
Start with GET /v1/couriers to obtain the current supported list and the slug to use as courier. Use the supported Indian courier reference to review names. Copy the request parameters and complete response shape from the API documentation before implementing; the examples here deliberately do not guess the AWB parameter spelling or a delivery-state field name.
Frequently asked questions
Which Indian couriers can I track through the API?
RCourier supports national and regional Indian couriers, including DTDC, Delhivery, Blue Dart and India Post. Use GET /v1/couriers for the current list and supported identifiers rather than assuming a courier name is the request slug.
Can I track more than one tracking number?
Yes, POST /v1/track/bulk accepts up to 50 shipments, each answered on its own. Keep each shipment’s outcome separate so a pending check or error does not become another parcel’s status.
Is there a free courier tracking API plan?
Check the plans on the RapidAPI listing for current availability. This guide does not specify a free allowance or a price, so confirm those details before budgeting the integration.
How often does courier tracking update?
RCourier refreshes active shipments in the background about every 3 hours until delivered, returned or cancelled. Later calls use stored data, so a quick response does not mean the courier has just supplied a fresh scan.
Is API pending the same as a parcel waiting for pickup?
No, RCourier’s status: "pending" describes an unfinished lookup. Follow retry_after_seconds before asking again; use the returned parcel state and timeline for delivery decisions.
What should you check before connecting?
Allow for delayed or incomplete courier data and a first lookup that may need a retry. RCourier provides a common status vocabulary, not a substitute for the courier’s missing scans. My recommendation is to review the response contract against your delivery, return and support decisions before connecting customer notifications.
WooCommerce store owners can get the same tracking as a plugin through RCourier for WooCommerce. For installation rather than API development, follow the WooCommerce courier tracking setup guide.
Try the RCourier India Courier Tracking API on RapidAPI with your courier and AWB, inspect the documented response shape, and check the plans before integrating.
