Skip to main content
PATCH
Afriex SDK
Update a customer’s KYC (Know Your Customer) information. Use this endpoint to add or update verification documents for a customer.

Authorizations

x-api-key
string
header
required

Static business API key issued from the dashboard. A business can provision multiple API keys, each scoped to a configurable set of permissions (e.g. read transactions, create deposits, etc). Permissions are chosen per key at creation time in the dashboard and may be revoked by deleting the key. Requests made with a key that does not include the permission required by the target endpoint is rejected with a 401 Unauthorized response, the same response an unrecognised, malformed or revoked key returns. The API does not distinguish the two cases on the wire. Manage your keys and their permissions under Developer → API keys in the dashboard.

Headers

x-api-version
string

API version in ISO 8601 format. The only supported version is 2026-05-18, which is also the default when the header is omitted. Any other value is rejected with a 400 Bad Request.

Path Parameters

customerId
string
required

The unique identifier of the customer

Body

application/json

A flat map of KYC document types to their values. Send the document map directly as the request body (do not wrap it in a kyc field). Each key must be one of the allowed KYC document types and each value is a string.

PHONE and COUNTRY are not accepted here; they are profile fields owned by PATCH /api/v1/customer/{customerId}. BVN is not accepted either; it is owned by POST /api/v1/customer/{customerId}/verify, which writes it only after a successful bank verification. Sending any of the three returns 400 INVALID_KYC_DOCUMENT_TYPE.

{key}
string

Response

Customer updated successfully.

data
object