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 KYC Consent

The Customer KYC Consent API facilitates the consent from the customer while capturing and retrieval of Customer Information. This aggregator service provides comprehensive Know Your Customer (KYC) consent management capabilities, enabling secure customer data capture, consent validation, and information retrieval operations across...

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

Tagged areas include Customers, Congo, Cameroon, Eswatini, and Zambia. The published artifact set on APIs.io includes API documentation, an API reference, and an OpenAPI specification.

This API exposes 3 operations across 3 paths, organized into 2 resource areas. It is described by OpenAPI 3.0.1, at version 2.0.

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

3 operations 3 paths 0 schemas 3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
2.0
Base URL
https://api.mtn.com/v1
Authentication
OAuth 2.0, HTTP Bearer
License
Resource Areas
2

Authentication & Security 2

MTN KYC Consent declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (OAuth2) using the clientCredentials flow. It accepts HTTP bearer tokens (JWT) (Bearer). By default, every request must be authenticated.

  • Bearer — Bearer token received from OAuth2.0 authentication with the MADAPI

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 3 POST. They span 2 resource areas: Callback, Kyc. Each is listed below with its method, path, parameters, and response codes.

Callback 1
POST
/callback
The user consent information posted here as a callback from consent application
Callback_post_consentCallback_callback 1 param body → 200400401403404500502503
Kyc 2
POST
/{customerId}
Endpoint for KYC with Consent.
Kyc_post_initiateKycWithConsentRequest_customerId 9 params body → 200400401403404500502503
POST
/consents
Consent By MSIDN - Customer id
Kyc_post_getConsentByMsisdn_consents 2 params body → 200400401403404500502503

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mtn-group-kyc-consent.yml Raw ↑

Other APIs MTN Group publishes across the network.

MTN Account Decisioning
MTN TMF Customer Bill Management - TMF678
MTN Loans
MTN Subscriber Details
MTN Subscriber Type
MTN Provisioning
MTN Unified Balance V1
MTN TMF Resource Inventory Management - TMF639
MTN Sales Lead
MTN Service Activation and Configuration
MTN Service Ordering
MTN BSS TT OAuth V1
Where this information came from

This is an independent, third-party profile of MTN KYC Consent, 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.