ShipOpsRun Courier
ShipOps connects to your Run Courier account with the auth key and client code from portal.runcourier.com. It lists your parcels directly, reads Run Courier's statuses into plain words, books and prints labels, and marks each parcel Run Courier says it has paid, with your payout statement read in beside it.
Run Courier is the third courier ShipOps knows on the iCargos platform, after ShipKartex and CouriersNext. Same portal shape, same API document with the host changed to portal.runcourier.com, same status list. One adapter serves all three; each courier gets its own connection, cooldowns and pages.
Run Courier's portal is a broker's: its public pages list the partner couriers it books onto, which is why a Run Courier trail can carry a partner courier's scans and why the status table below includes phrases like "Delivered To Vendor" that are returns. Booking needs a client code as well as the auth key, which the other two tenants do not ask for.
The API has no advice call, no settlement report and no webhooks. It carries a per-parcel Paid or Pending flag that ShipOps reads as the courier's word, never as an amount.
What ShipOps does with Run Courier
| Live tracking | Yes. ShipOps lists parcels from your Run Courier account directly, then follows each one. A parcel you booked outside ShipOps is still found. |
|---|---|
| Retry / return instruction | Run Courier has no API for a retry or return instruction. ShipOps still shows the parcel in your inbox with the reason, and links you to the Run Courier portal to answer by hand. |
| Booking and labels | Yes. Book from the order, print the label, cancel a booking. Services: Account default. Label layouts: ShipOps label (4×6 in). |
| COD payouts | Automatic · statement upload. Run Courier answers "was this parcel paid?" per parcel; ShipOps asks for every delivered parcel and marks what the courier attests. Drop in the payout statement Run Courier sends you and ShipOps reads it. How Run Courier pays COD, in detail → |
| What you type to connect | Auth key · Client code Then pick your shipper profile. |
| Recognised as | run courier · run courier · run couriers |
Connecting Run Courier
In the Run Courier portal, copy your account's API auth key (a UUID) and, from the same page, the client code shown above it. ShipOps needs both: the key to read, the code to book. Pick the shipper profile your bookings are created under.
Parcels come from the portal's own list, so a parcel booked outside ShipOps is still found. Nothing is written to your store until you switch a write-back on.
There is no advice API. A parked parcel lands in your inbox with the reason, and ShipOps links you to the portal to answer by hand.
What Run Courier's statuses mean
13 phrases, read the way the app reads them| What Run Courier prints | What it means | What to do |
|---|---|---|
| New Booked · Order Is Booked | Booked | Booked on Run Courier, awaiting the rider. |
| Pick Up In Progress | Booked | A rider is on the way to collect. |
| Picked Up · Parcel Received At Office · Parcel In Transit To Destination · Parcel Received At Destination | In transit | Moving inside Run Courier's network. |
| Out For Delivery | In transit | With the rider today. |
| Delivery Unsuccessful · Pending · Attempted | Attempt failed | A failed visit; the reason follows. Run Courier will retry. Reach the customer first. |
| Refused By Consignee · Consignee Not Responding · Consignee Not Available · Incomplete Address · Allow To Open Demand | Attempt failed | The reason for the failed visit, printed as the status. Still in the courier's hands; fix what you can with the customer. |
| Re-Attempt | Attempt failed | The same failed visit being redispatched. Not counted as a new attempt. |
| Shipper Advice · Ready For Return · Hold For Self Collection | Needs your decision | Run Courier is waiting for your word. There is no advice API: answer in the Run Courier portal. ShipOps keeps the parcel in your inbox until it moves. |
| Non Service Area · Lost · Claim | Needs your decision | Needs a person: the destination is outside coverage, or the parcel is reported lost or under claim. Talk to your account manager. |
| Return Confirmation · Return In Process · Return In Transit · Parcel Return To Office · Returned To Origin City · Return Received At Origin | Coming back | Coming back. "Return Received At Origin" is at the courier's hub, not yet handed to you. |
| Returned To Shipper · Return To Sender · Returned To Warehouse · Delivered To Warehouse · Delivered To Vendor | Returned to you | Back with you. The last two are return-side phrases despite the word "delivered". Check the parcel in. |
| Delivered · Replacement Delivered | Delivered | Delivered. Run Courier's payment flag flips to Paid once the COD is settled; the statement carries the amount. |
| Cancelled · Order Is Cancelled | Cancelled | Cancelled before pickup. |
Why a Run Courier delivery fails, as ShipOps names it
| Customer refused | Refused to accept |
|---|---|
| Customer not available | Consignee not available · Consignee out of city |
| Other | COD cash issue · Wanted to open parcel first · Item complaint · Needs review |
| Address problem | Address issue · Non-service area |
| Phone problem | Phone not responding |
| Courier-side | Duplicate order · Fake order · Delayed by courier · Courier awaits your instruction |
| Held | Held for self-collection |
| Lost or damaged | Parcel reported lost · Claim opened |
These are the reasons Run Courier gives on a failed visit, normalised to one label each so your team sees "Customer not available", never the raw string. The family decides what the Action Inbox suggests: an address problem asks the customer for a landmark, a phone problem tries WhatsApp, a refusal asks whether to return.
Questions merchants ask about Run Courier
Which Run Courier credentials does ShipOps need?
The API auth key (a UUID) and the client code from the same portal page. The key reads your account; the code is needed to book. Both are stored encrypted.
Why does the Run Courier status list look like ShipKartex's?
All three run on the iCargos platform. One adapter, three separate connections and three sets of pages.
Can I tell Run Courier to retry or return from ShipOps?
No, there is no advice API. The parcel shows in your inbox with the reason, and ShipOps links you to the portal to answer by hand.
Who prints the Run Courier label?
ShipOps, from the booking's data, as a 4×6 slip, so your customer's details never sit on the portal's open label URL.
Can I book Run Courier parcels from ShipOps?
Yes, under the shipper profile you choose, with a label and cancellation, on your own account.
Connect Run Courier in a minute
Install ShipOps, paste the key Run Courier already gave you, and your parcels and payouts land in one place. Free to start, no card.