Overview
Mozaca documentation is written for teams evaluating Fedha white-label mobile money, Zent digital finance corridors, Hazina treasury operations, partner rails, and controlled-access operating environments.
The public examples are representative: they describe intended API shapes, event states, client boundaries, workspaces, and operating controls used during product, sandbox, and partner scoping.
Integration path
Most teams start with a product walkthrough, then move into a sandbox review when the operating model is clear.
- 01
Request a walkthrough
Share product surface, client model, region, rails, expected volume, provider dependencies, and launch timeline.
- 02
Map the operating model
Confirm identity, ledger, controls, workspaces, evidence, partner dependencies, and readiness boundaries.
- 03
Review sandbox access
Receive API shape, webhook events, test data, and integration milestones for the selected environment.
- 04
Prepare pilot scope
Define corridor, monitoring, reporting, and acceptance criteria for the operating scope.
Base URL
Use the environment-specific base URL provided during sandbox review. The examples below use the planned public guide host until approved environments are issued.
https://api.mozacalabs.com/v1First request
In the approved API, every authenticated request is sent from your backend, not from client-side browser code. Include an authorization token and an idempotency key for write operations.
curl https://api.mozacalabs.com/v1/transfers \
-X POST \
-H "Authorization: Bearer MOZACA_SANDBOX_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: tr-demo-001" \
-d '{
"source": "wallet_kes_184250",
"destination": {
"type": "mobile_money",
"network": "partner_mobile_money",
"phone": "+2547..."
},
"amount": "2500.00",
"currency": "KES"
}'Related docs