Introduction
Myaza Trust is a KYC (Know Your Customer) verification platform. You use it to verify a person's government-issued identity — reading and validating their ID document, matching a selfie to the document holder, and running liveness checks. Five African markets (Nigeria, Ghana, Kenya, South Africa, Côte d'Ivoire) are backed by a direct government-database check; any other country is supported through document verification. See Countries & ID types.
This documentation covers everything you need to integrate: authenticating with API keys, uploading capture media, creating verifications, reading results, and receiving webhooks.
How the integration works
Verification is asynchronous. You submit a verification request and receive a verification ID immediately with a pending status; the result arrives later via webhooks or by polling for status.
You can drive a verification two ways: pass the configuration in code (country, ID types, steps), or build the flow once in the dashboard as a workflow and reference it by id — adding extra checks and an approve / decline / review decision without changing your code. Every flow runs in one of our SDKs or as a shareable hosted link.
See the Quickstart for a complete walkthrough of a verification from start to finish.
Base URL
All API requests — sandbox and production alike — are made to the same base URL:
| Environment | Base URL |
|---|---|
| Production | https://trust.myaza.co/api/kyc |
| Sandbox | https://trust.myaza.co/api/kyc |
Which environment you hit is determined entirely by the API key you use — pk_live_… keys target production, pk_test_… keys target sandbox. The base URL is the same for both. See Environments.
Conventions
- All request and response bodies are JSON, except media upload which is
multipart/form-data. - Timestamps are ISO 8601 strings in UTC (e.g.
2026-04-27T12:00:00.000Z). - IDs are opaque strings — do not parse them.
- Statuses in responses are lower-case (
pending,verified,failed,not_found,error).
Next steps
- Quickstart — a full verification end to end.
- Authentication — create and use API keys.
- Create a verification — the core endpoint in detail.
- Workflows — configure a flow visually and reuse it by id or hosted link.