How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

MTN Group Customer KYC API

The Customer KYC API from MTN Group — 7 operation(s) for customer kyc.

MTN Group Customer KYC API is one of 148 APIs that MTN Group publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Customer KYC. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 9 operations across 7 paths, and defines 28 schemas. It is described by OpenAPI 3.2.0, at version 1.0.2.

Requests are made against a single base URL, https://api.mtn.com/v1/kycVerification/.

9 operations 7 paths 28 schemas 2 GET7 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.2
Base URL
https://api.mtn.com/accountDecisioning/v1
Authentication
HTTP Basic, API Key
Resource Areas
1

Authentication & Security 2

MTN Group Customer KYC API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). An API key is passed in the header as X-API-Key (ApiKeyAuth). By default, every request must be authenticated.

Paths & Operations 9

Across 7 paths, the API surfaces 9 operations — 2 GET, 7 POST. Each is listed below with its method, path, parameters, and response codes.

Customer KYC 9
GET
/customers
Verify multiple customer kyc information by submitting an array of only msisdn or BVNs as a query params
3 params → 200400401403404405406415
POST
/customers
Verify multiple customer kyc information by submitting an array of customer information
4 params body → 200400401403404405406415
POST
/customers/{customerId}
Verify mtn customer kyc information against 3PP customer kyc information
4 params body → 200400401403404405406415
GET
/customers/{customerId}
Verify if customer MSISDN is active on either the bank or MTN
7 params → 200400401403404405406415
POST
/customers/{customerId}/kycScore
Verify mtn customer kyc information against 3PP customer kyc information
2 params body → 200400401403404405406415
POST
/customers/{customerId}/nameScore
Verify mtn customer kyc information against 3PP customer kyc information
2 params body → 200400401403404405406415
POST
/customers/{customerId}/addressScore
Verify mtn customer kyc information against 3PP customer kyc information
2 params body → 200400401403404405406415
POST
/customers/{customerId}/biometric/verify
Verify customer kyc information by uploading customer biometric data
5 params body → 200400401403404405406415
POST
/biometric-roc/customers/identityStatus
Get Identity Status by Customer ID
1 param body → 200400401404

Schemas 28

The contract defines 28 schemas that model the data the API accepts and returns. The most detailed are BVNVerificationResponseData (21 properties), KYCVerificationResponseData (17 properties), BasicKYCRequestData (14 properties), FaceMatchingResponse (9 properties). Each schema is shown below with its type and property counts.

Error400
object
5 properties
ErrorPayload
object
6 properties
FaceMatchingRequest
object
Request for biometric matching
7 properties
BVNVerificationResponseData
object
21 properties
MsisdnVerificationData
object
5 properties
BasicKYCRequestData
object
14 properties
KYCVerificationResponseData
object
17 properties
Error401
object
5 properties
KYCAddressVerificationScoreResponse
object
5 properties
KYCNameRequestDataScore
object
3 properties
CustomerKYCVerificationMultipleRequest
object
3 properties
identityStatusRequest
object
3 properties
KYCNameVerificationScoreResponse
object
5 properties
KYCRequestDataScore
object
9 properties
FaceMatchingResponse
object
Response object
9 properties
KYCVerificationResponse
object
7 properties
KYCVerificationScoreResponseData
object
9 properties
CustomerVerificationKYCMultiResponse
object
5 properties
KYCNameVerificationScoreResponseData
object
3 properties
identityStatusResponse
object
5 properties
CustomerVerificationResponse
object
7 properties
KYCVerificationScoreResponse
object
5 properties
KYCAddressRequestDataScore
object
5 properties
BinaryAttachmentData
array
KYCAddressVerificationScoreResponseData
object
5 properties
CustomerVerificationKYCMultiResponseData
object
1 property
BIOMetricResponse
object
6 properties
Error404
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mtn-group-customer-kyc-api-openapi.yml Raw ↑

Other APIs MTN Group publishes across the network.

MTN MoMo Collection API
MTN MoMo Disbursements API
MTN MoMo Remittance API
MTN MoMo Sandbox User Provisioning API
MTN Group Accessible to 3PP API
MTN Group Accessible to USSD Gateway API
MTN Group Activation API
MTN Group Add User API
MTN Group Admin Suspend API
MTN Group Adverts API
MTN Group Advice Reconcile API
MTN Group Agents API
Where this information came from

This is an independent, third-party profile of MTN Group Customer KYC API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.