REST API. JSON in, JSON out. Idempotent writes. HMAC-signed webhooks. RFC 7807 errors. A free sandbox with simulated M-PESA, MTN, Airtel, Vodacom, and bank rails for Kenya, Tanzania, and Uganda.
# Check the API is live $ curl https://api.sharet.africa/v1/health # → 200 OK { "status": "ok", "version": "v1", "rails": [ "mpesa_ke", "mtn_ug" ], "ts": "2026-09-16T10:42:00Z" }
The full contract. If it is not here, it is in the OpenAPI spec. If it is not in the OpenAPI spec, write to us and we will add it.
| Base URL | https://api.sharet.africa/v1 |
| Sandbox URL | https://sandbox.api.sharet.africa/v1 |
| Auth | Bearer JWT (short-lived, 15 min) + HMAC-SHA256 signed request body |
| Idempotency | Required on all POST/PUT. Header: Idempotency-Key. 24-hour window. |
| Content-Type | application/json |
| Rate limits | 100 req/s standard · 1,000 req/s on Tier 03. Headers: X-RateLimit-Remaining. |
| Errors | RFC 7807 problem+json |
| Webhooks | HMAC-SHA256 signed · retried 24h with exponential backoff |
| SLA | 99.9% uptime target (contractual on Tier 03) |
| Status page | status.sharet.africa |
| OpenAPI spec | /openapi/v1.yaml |
One call. Sharet detects the country, resolves the network, checks liquidity, and returns a transaction ID and fee. Here is exactly what the request and response look like.
curl -X POST https://api.sharet.africa/v1/transactions \ -H "Authorization: Bearer $TOKEN" \ -H "Idempotency-Key: 7f3a-4c1b-8e2d" \ -H "Content-Type: application/json" \ -d '{ "source": "wallet_abc", "destination": { "type": "phone", "value": "+255754000000", "country": "TZ" }, "amount": { "value": "10000", "currency": "KES" } }'
{
"id": "tx_8f3a2b9e",
"status": "processing",
"rail": "vodacom_tz",
"country": "TZ",
"amount": {
"value": "10000",
"currency": "KES"
},
"fee": {
"value": "320",
"currency": "KES"
},
"eta": "2026-09-16T10:45:00Z",
"webhook": "transaction.settled"
}
Idempotent · retry-safe · webhook fires on settle with HMAC signature
Nine endpoints. Everything you need to send money, query the ledger, monitor treasury, and receive webhooks. No hidden magic.
Every error response follows the same shape. No HTML. No stack traces. No surprises. Parse type to branch, detail to show the user.
| Status | Meaning | Retry? |
|---|---|---|
| 400 | Malformed request body | No |
| 401 | Missing or invalid token | No |
| 403 | Insufficient permissions | No |
| 409 | Idempotency conflict — key reused with different body | No |
| 422 | Business rule violation (insufficient balance, over limit) | No |
| 429 | Rate limit exceeded — see Retry-After | Yes |
| 502 | Upstream rail unavailable | Yes, with backoff |
| 503 | Sharet temporarily unavailable | Yes, with backoff |
# Error response shape { "type": "https://api.sharet.africa/errors/insufficient_funds", "title": "Insufficient funds", "status": 422, "detail": "Wallet balance is KES 5,000; requested transfer is KES 10,320.", "instance": "/v1/transactions", "trace_id": "t_9c2e8f1a" }
The sandbox is real and running. It simulates M-PESA Kenya and MTN Uganda today. Vodacom Tanzania is in integration. Airtel and card simulation are planned for Q1 2027.
| Rail | Status | Notes |
|---|---|---|
| mpesa_ke | ● Live | Full simulation: success, failure, delay |
| mtn_ug | ● Live | Full simulation |
| vodacom_tz | ● In integration | Expected Q4 2026 |
| airtel_tz | ○ Planned | Q1 2027 |
| airtel_ug | ○ Planned | Q1 2027 |
| card | ○ Planned | Q1 2027 |
| bank_ke | ○ Planned | Q1 2027 |
Request access and you will receive a sandbox token, a set of test phone numbers, and a Postman collection. Test success, failure, delay, and rail-degraded scenarios deterministically.
Deterministic test numbers · real webhooks · real idempotencyEvery test phone number is documented. +254700000001 succeeds. +254700000002 fails. +254700000003 delays by 30 seconds.
Sandbox webhooks are signed exactly like production. Test your retry logic and signature verification before going live.
Python, Node, PHP, and Flutter SDKs are in development. Until then, the API is a plain REST interface that works from any HTTP client. Community SDKs welcome.
Python · Node · PHP · Flutter · Q1 2027For banks, fintechs, SACCOs, and platforms that want their own branded wallet — the entire Sharet ledger, treasury, and adapter stack is licensable. You bring the customers and the brand. We bring the rails and the settlement.
A fully-branded wallet with your logo, your colour, and your domain. Your customers see your brand. Sharet runs the ledger, treasury, and rails underneath. Deployment options include Sharet-hosted, single-tenant, or self-hosted in your cloud.
Banks · fintechs · SACCOs · platforms · insurersDirect API access with reserved capacity, custom rate limits, and priority routing. Ideal for high-volume platforms.
Sharet operates the country-level liquidity pools, reconciles them daily, and reports to you in real time. Or you operate your own pools and we reconcile across them.
If your business needs a rail or corridor Sharet does not yet support, we build the adapter. You get first access. The adapter then becomes part of the Sharet network for future customers.
Custom corridors · bespoke rails · dedicated engineeringLicensing models: revenue share · platform fee · bespoke commercial terms. Contact us to discuss.
Documented paths
Every request is read by a human on the engineering team. Sandbox access is granted within one working day. Licensing conversations are scheduled within a week.
A working API. A live sandbox. A contractual SLA on Tier 03. Whatever your team needs to ship payments across East Africa — it starts here.