MedsGH Developers
v0.1 · draft

Logistics Provider Standard

Integrate your delivery service with MedsGH

One contract for every logistics provider: four calls, six statuses, and signed status callbacks. New providers receive credentials and configuration, never a different API.

Example · status callback
POST/api/webhooks/provider/jobs/MG-1042-P17/status?tok=…
X-Provider-Id:        3
X-Provider-Signature: 9f2c…e41a
X-Event-Id:           evt_7f3a91
X-Event-At:           2026-09-13T11:02:00Z

{
  "job_id": "MG-1042-P17",
  "provider_reference": "uuu24Rres",
  "status": "in_transit",
  "at": "2026-09-13T11:02:00Z"
}

Integration surface

Four calls

Three calls go from MedsGH to your API. Status events flow back to a per-job URL that MedsGH supplies with every job.

MedsGHProvider
1GET rates

Price a trip. Returns a quote_reference that locks the price.

2POST job

Hand over the job packet. Idempotent on Idempotency-Key.

3Status callbacks

Signed events POSTed to the job's callback_url.

4Cancel

Valid before pickup only.

Design

Contract guarantees

STATUSES

Fixed vocabulary

Six values: accepted, picked_up, in_transit, delivered, failed, cancelled. Unknown values are rejected, never inferred.

PROOF

Verified delivery

delivered requires a verified customer OTP or a photo URL.

RETRIES

Idempotent booking

Resending a job with the same idempotency key returns the original booking.

INTEGRITY

Signed callbacks

HMAC-SHA256 signature, event timestamp window and event-id deduplication.

Documentation

Where to start