Skip to main content
POST
Submit customer KYC πŸ”’

Authorizations

X-Numero-Api-Key
string
header
required

Your business API key (live_key_...). Issued on approval; managed in Dashboard β†’ Settings β†’ Developer.

X-Numero-Signature
string
header
required

Base64(HMAC-SHA256(publicApiKey, input)) over the raw request body (POST) or canonicalized query string (signed GET). Also send X-Numero-Signature-Version: v2. Required on money-movement / state-changing endpoints (marked πŸ”’).

The HMAC key is your Public Key as raw UTF-8 bytes β€” a SECRET despite the name, and a different value from the X-Numero-Api-Key authentication header. Signing with the API key will never produce a valid signature.

Path Parameters

id
integer<int64>
required

Body

application/json

Give type plus the matching identifier in payload. A bare { "bvn": "..." } body is still accepted for back-compatibility and is treated as a BVN check.

type
string

Verification product code, e.g. BVN or NIN.

payload
object

Identifiers for the check, e.g. { "bvn": "22222222222" }.

bvn
string

Back-compat shorthand for a BVN check.

Response

The customer

Canonical response envelope for the public surface. data on success, error on failure.

data
object
required

One customer, with everything they own attached.

error
object | null
required
meta
object
required