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 Customer Pin Management v2

To facilitate the capability for customer to create/validate/change Pin Information.

MTN Customer Pin Management v2 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, Cameroon, Liberia, and Nigeria. The published artifact set on APIs.io includes API documentation, an API reference, and an OpenAPI specification.

This API exposes 6 operations across 2 paths, and defines 17 schemas. It is described by OpenAPI 2.0, at version 1.0.2.

Requests are made against the base URL https://api.mtn.com/customerPinManagement/v2.

6 operations 2 paths 17 schemas 2 GET1 PATCH1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 2.0
API Version
1.0.2
Base URL
https://api.mtn.com/customerPinManagement/v2
Authentication
API Key, OAuth 2.0
Resource Areas
1

Authentication & Security 2

MTN Customer Pin Management v2 declares 2 security schemes for authenticating requests. An API key is passed in the header as X-API-Key (ApiKeyAuth). It supports OAuth 2.0 (OAuth2) using the application flow. By default, every request must be authenticated.

Paths & Operations 6

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

PIN 6
POST
/customer/{customerId}/pin
To create Pin customer will provide mandatory(customerId, secret, alternateNumber, securityQuestion, tncDetails,channel,transId) attributes. Also will provide emailID as optional input
createCutomerPin 17 params → 200400401403404405500
GET
/customer/{customerId}/pin
To validate Pin Details user will enter (customerId, secret, channel, transId) Attributes
validateCutomerPin 5 params → 200400401403404405500
PUT
/customer/{customerId}/pin
To change Pin Details user will enter (customerId, operationType, currentSecret, newSecret,channel,transId) Attributes
changeCutomerPin 13 params → 200400401403404405500
PATCH
/customer/{customerId}/pin
To reset Pin Details user will enter (customerId, operationType, validateAnswers, motherName,dateOfBirth,stateOfOrigin,channel,transId) Attributes
resetCutomerPin 11 params → 200400401403404405500
PUT
/customer/{customerId}/pinProfile
To change Pin Details user will enter (customerId, operationType,securityQuestion,securityAnswer,channel,emailID,tncDetails) Attributes
chanageSecurityQnACutomerPin 8 params → 200400401403404405500
GET
/customer/{customerId}/pinProfile
To get Pin profile Details user will enter (customerId, operationType,securityQuestion,securityAnswer,channel) Attributes
getProfileDetails 5 params → 200400401403404405500

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are ValidatePinResponseData (7 properties), Error (7 properties), ChangePinResponse (5 properties), CreatePinResponse (4 properties). Each schema is shown below with its type and property counts.

SecurityQuestionAnswers
array
securityquestionAnswer
object
2 properties 1 required
ValidatePinResponse
object
4 properties 1 required
ValidatePinResponseData
object
7 properties
ChangePinResponse
object
5 properties 1 required
ChangePinResponseData
object
2 properties
resetPinResponse
object
4 properties 1 required
ResetPinResponseData
object
2 properties
ValidateSecurityAnswerResponse
object
4 properties 1 required
ValidateSecurityAnswerResponseData
object
1 property
GetProfileDetailsResponse
object
4 properties 1 required
GetProfileDetailsResponseData
object
1 property
chanageSecurityQnAResponse
object
4 properties 1 required
chanageSecurityQnAData
object
1 property
CreatePinResponse
object
4 properties 1 required
CreatePinResponseData
object
1 property
Error
object
7 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mtn-group-customer-pin-management-v2.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 Customer Pin Management v2, 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.