Connect your own system to the same record

DawaTrack Partner API

REST and webhooks, working today

OAuth2 client credentials, a scope per kind of call, and the same traceability ledger the portal reads. Every write takes an idempotency key, so a call sent twice records once.

• Events: commission, ship, receive, dispense, quarantine and release, one at a time or up to 1,000 in a bulk job; a document cancelled in your system is retracted.
• Receipts and consignments: confirm a shipment waiting for you, and see which of your consignments each receiver has confirmed.
• Batches: a batch's distribution tree, its orphans and its events as GS1 EPCIS 2.0, for any batch you take part in.
• Recalls: open a recall or run a drill, and follow who it reached.
• Webhooks: signed pushes for recalls, orders and shipment confirmations, so you do not have to poll.
• Sandbox: test credentials with demo data, issued without review.

Our team can help you scope the integration. You or your vendor build it against our REST API and sandbox.

One call, start to finish

1. 1

   Get a token

   POST /oauth/token/ with your client ID and secret. It lasts 60 minutes.

2. 2

   Send the event

   POST /events/ with an Idempotency-Key, so a retry never records twice.

3. 3

   It's on the ledger

   201 Created. The batch's tree, its recalls and its EPCIS export now include it.

4. 4

   Hear back by webhook

   When the receiver confirms, or a recall reaches the batch, a signed push arrives.

POST /partner-api/v1/events/
Authorization: Bearer <access token>
Idempotency-Key: sapb1:ACME:PurchaseDeliveryNotes:812:0:BTH-2026-041

{
  "event_type": "RECEIVE",
  "gtin": "06164004321562",
  "batch_number": "BTH-2026-041",
  "quantity": 12000,
  "expiry_date": "2027-11-30",
  "sender": {
    "name": "Manufacturer Abroad",
    "gln": "0614141000005"
  }
}

Sending…201 Created

Example request. Shipments from that receipt then name it as their parent, so the batch can be followed onward.