Introduction

Myaza Identity is a KYC (Know Your Customer) verification platform. You use it to verify a person's government-issued identity — confirming an ID number against the source government database, matching a selfie to the document holder, and running liveness checks — across multiple African countries.

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.

See the Quickstart for a complete walkthrough of a verification from start to finish.

Base URL

All API requests are made to the /api/kyc path on the environment host:

Which environment you hit is determined by the API key you use — pk_live_… keys target production, pk_test_… keys target staging. 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.