Integration partners
Quote, book, track, invoice and reconcile Kenyan mobility from inside your own product. Server-priced, idempotent, signed and certified before a single production request.
Behind the endpoints sit dispatch, pricing governance, compliance, tax invoicing and a ledger-grade financial spine. You integrate once and inherit all of it.
Prices, policies and cancellation outcomes are decided server-side and recorded immutably.
Rides, charter, delivery and rental share a single order lifecycle and event vocabulary.
Sealed, hash-verifiable receipts, tax invoices and proof of delivery on every order.
Desk-issued credentials carry only the scopes named in your integration scope document.
The API surface is organised by business capability, not by internal service boundaries. Your integration scope names the domains you are granted.
Server-priced quotes for rides, charter, delivery and rental. Prices are computed by the governed pricing engine — never assembled client-side.
Callable today: Air-charter quotes are live at POST /v1/air/quotes. Rental quotes are live at POST /v1/rentals/quotes. Ride quotes are live at POST /v1/rides/quotes for partners with a linked TaxiD rider account.
Create and manage mobility orders from inside your own product journey, with idempotent writes and explicit lifecycle states.
Callable today: Logistics orders and shipments are live at /v1/orders and /v1/shipments. Ride, rental and charter bookings are live at /v1/rides/bookings, /v1/rentals/bookings and /v1/charters/bookings (sandbox keys get simulated bookings).
Live assignment, position and ETA for in-flight orders, plus signed public tracking links you can hand to end customers.
Callable today: Logistics tracking, routes, delivery attempts and proof of delivery are live. Ride tracking is not yet exposed.
Receipts, invoices, trip evidence and compliance documents issued with cryptographic seals and independently verifiable.
Callable today: Settlement statement documents with a SHA-256 content hash are live at GET /v1/documents/statements/{id}. Receipts and tax invoices are still issued inside TaxiD portals.
Ledger-grade financial data: transaction records, statements, fees and payout positions that reconcile to the cent.
Callable today: Read-only statements (GET /v1/settlements, /v1/settlements/{id}) and your ledger (GET /v1/ledger) are live for production keys; test keys return empty lists.
Scoped credentials, actor attribution and policy checks so every API action is traceable to a named integration and purpose.
Callable today: OAuth 2.0 client-credentials is live at POST /v1/oauth/token (one-hour scoped tokens). client_id:secret keeps working.
Representative endpoints per domain, with runnable samples. The full OpenAPI 3.1 schema is issued with your sandbox credentials.
Production https://pvbgymafdxdcdencsmbk.supabase.co/functions/v1/logistics-partner-api/v1
Sandbox https://pvbgymafdxdcdencsmbk.supabase.co/functions/v1/logistics-partner-api/v1
/air/quotesServer-priced quotes for every live partner aircraft on a route. Nothing is booked.
curl -X POST https://pvbgymafdxdcdencsmbk.supabase.co/functions/v1/logistics-partner-api/v1/air/quotes \
-H "Authorization: Bearer $TAXID_CLIENT_ID:$TAXID_SECRET" \
-H "Content-Type: application/json" \
-d '{"origin":"WIL","destination":"MRE","depart_date":"2026-11-02","passengers":4}'/rentals/quotesServer-priced rental quotes from the live rate card. Nothing is booked.
curl -X POST https://pvbgymafdxdcdencsmbk.supabase.co/functions/v1/logistics-partner-api/v1/rentals/quotes \
-H "Authorization: Bearer $TAXID_CLIENT_ID:$TAXID_SECRET" \
-H "Content-Type: application/json" \
-d '{"start_at":"2026-11-02T08:00:00+03:00","days":3}'/rides/quotesLocked server price for the partner's linked rider account.
curl -X POST https://pvbgymafdxdcdencsmbk.supabase.co/functions/v1/logistics-partner-api/v1/rides/quotes \
-H "Authorization: Bearer $TAXID_CLIENT_ID:$TAXID_SECRET" \
-H "Content-Type: application/json" \
-d '{"pickup":{"lat":-1.2864,"lng":36.8172,"address":"Nairobi CBD"},"dropoff":{"lat":-1.3192,"lng":36.9278,"address":"JKIA"}}'TaxiD pushes state to you. Every delivery is HMAC-SHA-256 signed with a timestamp; reject unsigned or stale payloads, respond 2xx to acknowledge, and let backoff handle the rest.
import { createHmac, timingSafeEqual } from "node:crypto";
export function verifyTaxiDWebhook(rawBody: string, header: string, secret: string) {
const [tsPart, sigPart] = header.split(","); // "t=...,v1=..."
const timestamp = tsPart.replace("t=", "");
const expected = createHmac("sha256", secret)
.update(`${timestamp}.${rawBody}`)
.digest("hex");
const received = sigPart.replace("v1=", "");
const fresh = Math.abs(Date.now() / 1000 - Number(timestamp)) < 300;
return fresh && timingSafeEqual(Buffer.from(expected), Buffer.from(received));
}| Event | Meaning |
|---|---|
order.confirmedorder_idpartner_referenceservicetotal | Order accepted and entered the fulfilment pipeline. |
order.assignedorder_idassignmenteta_seconds | A driver, vehicle or operator has been assigned. |
order.startedorder_idstarted_at | Journey or delivery has begun. |
order.completedorder_idcompleted_atfinal_total | Fulfilment closed; documents are being sealed. |
order.cancelledorder_idreasoncancellation_fee | Order cancelled, with the policy outcome and any fee. |
payment.settledorder_idamountmethodreference | Funds settled against the order or wallet. |
document.issuedorder_iddocument_idkindcontent_hash | A sealed receipt, invoice or evidence document is available. |
reconciliation.exceptionexception_idseverityorder_id | A financial exception was raised and needs partner attention. |
Credentials are never self-serve. Access is granted stage by stage, and each stage has an explicit exit criterion — so both sides know what "done" means.
Architecture session with the integration desk: your product journey, the service lines you need, data residency, volumes and settlement model.
Exit criteria: Signed integration scope naming the endpoints, webhooks and environments you will use.
Sandbox client credentials issued with least-privilege scopes, webhook signing secret and a dedicated integration channel.
Exit criteria: Successful client-credentials exchange and a verified webhook signature in sandbox.
Full-fidelity sandbox with deterministic scenario seeds: happy path, driver reassignment, cancellation with fee, payment failure and reconciliation exception.
Exit criteria: Every contracted scenario implemented against the sandbox, including failure handling.
The desk replays the agreed scenario matrix against your integration and reviews idempotency, retry behaviour, webhook acknowledgement and evidence handling.
Exit criteria: Certification record passed, with any findings closed and re-tested.
Production credentials issued, traffic ramped under agreed limits, with joint monitoring of error rates, latency and settlement accuracy.
Exit criteria: Ramp completed at full rate limit with SLOs met and a named support route in place.
What your security review will ask for, stated up front.
One-hour bearer tokens minted from approved client credentials. Static client_id:secret authentication is also supported; keep both server-side.
Each credential carries only the scopes named in your integration scope document; scope changes are a governed request.
Every delivery carries an HMAC-SHA-256 signature and timestamp; reject unsigned or stale payloads and reply 2xx to acknowledge.
Transactional endpoints marked in the reference require Idempotency-Key. Quote, OAuth and configuration operations do not imply the same guarantee.
Use HTTPS. IP restrictions can be configured per credential; trusted proxy and DNS-rebinding-safe outbound delivery remain unverified. Mutual TLS is not offered as a verified capability.
Every request is attributed to a named integration and actor, retained in an append-only audit trail.
Only the passenger and payment fields required for fulfilment are accepted; card data never touches partner integrations.
Receipts and invoices are sealed with content hashes that you or your customer can verify independently.
Sandbox is for correctness. Production carries the commitments.
| Metric | Sandbox | Production |
|---|---|---|
| Availability | NO DATA — no certified baseline | NO DATA — no certified availability SLO |
| Latency | Measured request records where available | Measured request records where available |
| Webhook delivery | Endpoint-configured retry budget | Endpoint-configured retry budget; recovery unverified |
| Rate limit | Credential-specific: 2,000 / 10,000 / 25,000 per minute | Credential-specific: 2,000 / 10,000 / 25,000 per minute |
| Incident acknowledgement | As agreed with the integration desk | As agreed; no verified response-time guarantee |
code, a human-readable message and a request_id to quote when you contact the desk.Pricing is contracted, not published per call — because volume, service lines and settlement model change the economics. Here is the shape of each engagement.
Single-market platforms adding TaxiD to an existing product journey.
Aggregators and multi-brand platforms running material daily volume.
Enterprise, institutional and government programmes embedding TaxiD as core mobility infrastructure.
Bring your architecture and your volumes. You will leave with a named integration scope, a sandbox timeline and the certification scenarios you have to pass.
Technical enquiries: sales@taxid.app · +254 747 700004