What you can build with the Dawurobo Partner Platform

Who's this for

The Dawurobo Partner Platform is how you add delivery API and commerce capabilities for Ghana to your own app — no fleet, no warehouse, no separate integration per service.

• An app, store, or website that wants same-day delivery in Ghana built into checkout, without running its own riders or fleet. This is Dawurobo's delivery API — add delivery to your app with a handful of signed HTTP calls.
• An app, store, or website that wants to sell products online in Ghana without holding inventory — Dawurobo-vetted vendors' products, syndicated into your storefront, fulfilled and delivered without you touching stock, paid for by mobile money or card.

Most partners start with delivery — it's the flagship, the thing most businesses need first — and some add the syndicated catalog later as a second revenue line. Both run on the same keys, the same signing, the same integration.

One integration, many services

The Dawurobo Partner Platform is a single integration surface that fans out to multiple Dawurobo services. You authenticate once, sign requests the same way everywhere, and hold one set of API keys per app — then call whichever services your app is entitled to. Adding a new Dawurobo service to your integration later doesn't mean a new auth model, a new SDK, or a new set of credentials; it's the same keys, the same signing, a new set of endpoints.

Today that's delivery and Safe catalog. More services get added to the same platform over time.

Delivery

Plug same-day delivery into your product without operating a fleet.

• Create and track deliveries — hand off an order for pickup and drop-off with orders.create, then follow its status (accepted, picked up, in transit, delivered) via polling or webhooks. You choose per order who pays the delivery fee: the recipient in cash on delivery (the default — no wallet needed), or you.
• Fund deliveries from a prepaid wallet (optional) — when you'd rather absorb the delivery fee yourself, set payment.payer: "partner" and the fee is drawn from a prepaid wallet balance held against your account; check the balance and top it up programmatically. See Wallet top-up and How money works.

Typical use case: a marketplace, food app, or storefront that needs "get this physical thing from A to B today" without building its own logistics.

Safe catalog

Resell products from vendors who've opted into syndication, without holding inventory yourself.

• List and read syndicated products — pull a live product catalog (with pricing, availability, and vendor attribution) from vendors who've made their listings available for syndication.
• Place prepaid orders — create an order against a syndicated product, take payment through the platform's gateway (mobile money or card), and verify + settle it once payment clears.

Full endpoint-by-endpoint detail is in Safe catalog.

Typical use case: a storefront, content site, or app with an audience that wants to sell products it doesn't manufacture or stock — the platform handles fulfillment and payment settlement.

The provider → reseller → settlement pattern

Both services follow the same shape, even though the goods being moved are different:

1. Provider — the entity that actually does the thing (a rider who delivers a package, a vendor who stocks a product). Providers don't integrate with you directly.
2. Reseller (your app) — you offer the capability to your own users, under your own brand and UX, by calling the platform's API.
3. Settlement — the platform tracks who's owed what. For delivery, that's your wallet balance funding trips. For Safe catalog, that's a per-sale decomposition (vendor payout, platform fee, your margin) recorded to the ledger once an order settles.

You never talk to providers or move money directly — you call the API, the platform handles provider dispatch and settlement math, and gives you back status you can show your users.

The self-serve path

You don't need to talk to anyone to start integrating:

1. Sign up in Partner Hub and create an app.
2. Generate a staging API key and signing secret instantly — no manual provisioning step. Staging keys hit the same endpoint paths as production, so you can build and test authentication, signing, the full recipient-pays delivery flow (orders.create / orders.get / orders.track / orders.estimate / orders.cancel), and catalog reads (safe-catalog/catalog.list, catalog.get, orders.get) fully on staging. Endpoints that charge a payment gateway — the delivery wallet and placing/verifying Safe catalog orders — reject staging keys, and wallet-funded delivery orders need the delivery:wallet:spend scope; see Getting started for the full breakdown.
3. Build against the docs — Getting started walks through environments and the request lifecycle, Authentication and signing covers headers and the signature algorithm, and the API Reference has every operation with live request/response schemas.
4. Request production activation once your staging integration is tested end to end. This is a short approval step that includes KYC on your business — after that, generate a production key and swap it in. The base URL stays the same; your key decides the environment.

Where to go next

• Getting started — environments, base URLs, and the request lifecycle.
• API Reference — every operation, live and interactive, generated from the platform's OpenAPI spec.