Create deliveries
Send a delivery with the recipient, address and packages. Each request can carry your own request ID, so a retry after a timeout finds the delivery it already created instead of making a second one.
Integration
Healthcare TMS and pharmacy delivery API
A transport management system is only as useful as the way work gets into it and status gets out. The NoazRX delivery API lets another system create, update and cancel deliveries, submit a day’s work in batches, fetch the labels, and read back where each delivery stands — without anyone retyping an address.
What is a healthcare TMS?
A healthcare transport management system (TMS) is the layer that plans and records the movement of medication, specimens and supplies between the parties that hold them. In a general freight TMS the unit is a shipment and the job ends at a dock. In healthcare the unit is often a single prescription for a single person, the job ends at a door, and the system has to keep a record of the handoff that holds up afterwards.
In NoazRX the TMS and the day-to-day pharmacy delivery software are the same system: the dashboard, the driver app and the records all sit on it. This page is about the part another system talks to. For where it fits in the wider chain, see pharmaceutical logistics.
Delivery API
What the delivery API does
A server-to-server REST API, authenticated with an API key. Everything below is available to an integration today.
Submit a batch
Send a day’s deliveries in one call. The batch is accepted straight away and processed in the background; you can look it up by your own batch reference and list the deliveries it produced.
Update and cancel
Correct a delivery after it has been created, or cancel one that should no longer go out, from the same system that created it.
Labels
Fetch the label for one delivery, or every label for a batch, ready to print. Formats are described on pharmacy shipping labels and manifests.
Status
Read where a delivery stands by its NoazRX ID, your own reference number or its tracking number. The proof of delivery itself stays in the pharmacy’s dashboard and reports.
Keys
API keys are issued per integration by NoazRX, can be rotated and revoked, and their owners are warned before a key expires.
Identity
Your references, not ours
The most common integration failure is two systems that disagree about which delivery is which. So a delivery can be found by the reference number your system already uses, a batch by your own batch ID, and a create request by the request ID you sent with it. Your system never has to store a NoazRX identifier just to ask a question about its own order.
The same thinking applies to the barcode on the package. A pharmacy can link its own existing barcodes to a delivery, so drivers can scan the label the pharmacy already prints alongside the NoazRX label.
Order intake
Other ways deliveries get in
Not every pharmacy system can call an API, and not every pharmacy needs to. Deliveries can also be entered in the pharmacy dashboard, uploaded as a CSV file and processed in the background, or queued offline with encrypted QR labels when the internet drops. All of them land in the same delivery record as an API call, with the same scans, proof and reports downstream — see getting deliveries into NoazRX.
What happens after intake — dispatch, routing, service levels — is covered on pharmacy delivery dispatch and SLA management.
Planning
Integration checklist
The questions worth settling before the first delivery goes through an API.
- Which system owns the order? Decide whose reference number identifies a delivery, and send it on every request.
- How are retries handled? Send a request ID with every create, so a network retry cannot produce a duplicate stop.
- One at a time, or in batches? Batches suit a pharmacy that releases the day’s work in one go; single calls suit a system that creates deliveries as prescriptions are filled.
- Who prints the labels? Fetch them per delivery or per batch, and agree which printer format the pharmacy uses.
- When does your system check status? Agree the moments that matter — picked up, delivered, not delivered — and how often to ask.
- What can be changed after creation? Agree the cut-off for edits and cancellations once a driver has the package.
- Who holds the keys? Name an owner for each API key, and plan rotation before the expiry notice arrives.
Healthcare TMS and API questions
Does NoazRX have an API?
Yes. A server-to-server REST API for creating, updating, cancelling and looking up deliveries, submitting batches and fetching labels, authenticated with an API key issued by NoazRX.
How does our system find out a delivery’s status?
By asking the API for the delivery by its NoazRX ID, your own reference number or its tracking number. Proof of delivery, photos and signatures stay in the pharmacy dashboard and its reports.
Can it connect to our pharmacy management system?
Any system that can call a REST API or export a CSV file can send deliveries to NoazRX. Tell us what your pharmacy runs and we will say which route in fits it.
Do we need the API to use NoazRX?
No. Most pharmacies start in the dashboard or with a CSV upload; the API is for teams that want deliveries created straight from another system.
Talk to us about an integration
Tell us where your deliveries start today — which system, which format, how many a day — and we will tell you the simplest way to get them into NoazRX.