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 Notification v2

To facilitate notifications. Allows 3PPs to register and have notifications processed to them from the applicable backends.

MTN Notification 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 Messaging, Congo, Côte d’Ivoire, Cameroon, and Ghana. The published artifact set on APIs.io includes API documentation, an API reference, and an OpenAPI specification.

This API exposes 7 operations across 5 paths, organized into 2 resource areas, and defines 9 schemas. It is described by OpenAPI 2.0, at version v2.0.

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

7 operations 5 paths 9 schemas 2 DELETE2 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 2.0
API Version
v2.0
Base URL
https://api.mtn.com/v2
Authentication
OAuth 2.0
Resource Areas
2

Authentication & Security 1

MTN Notification v2 declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2) using the application flow. By default, every request must be authenticated.

Paths & Operations 7

Across 5 paths, the API surfaces 7 operations — 2 DELETE, 2 GET, 3 POST. They span 2 resource areas: Registration, Notifications. Each is listed below with its method, path, parameters, and response codes.

Registration 5

Registration, update and delete Notifications

POST
/notification/register/3PP
Register/Update 3PP for notification.
register3PPNotificationDetailsUsingPOST 2 params → 201401403404409500
GET
/notification/register/3PP/{id}
Get 3PP notification details by id.
get3PPNotificationDetailsByIdUsingGET 2 params → 200400401403404500
DELETE
/notification/register/3PP/{id}
Delete 3PP Notification registration by id.
delete3PPNotificationDetailsByIDUsingDELETE 2 params → 200400401403404409500
GET
/notification/register/3PP/{targetSystem}/{code}/{notificationType}
Get 3PP Notification details by target system, code and notification type.
get3PPNotificationDetailsByNameAndCodeAndNotificationTypeUsingGET 4 params → 200400401403404409500
DELETE
/notification/register/3PP/{targetSystem}/{code}/{notificationType}
Delete 3PP Notification registration by target system, code and notification type.
delete3PPNotificationDetailsByNameAndCodeAndNotificationTypeUsingDELETE 5 params → 200400401403404409500
Notifications 2

Send Notifications

POST
/notification/3PP/{id}
Send notification to 3PP by id.
notification3PPByIdUsingPOST 3 params → 200400401403404500
POST
/notification/3PP/{targetSystem}/{code}/{notificationType}
Send notification to 3PP by name, code and notification type.
notification3PPByNameAndCodeAndnotificonTypeUsingPOST 5 params → 200400401403404500

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are Error (8 properties), DeleteNotificationSubscriptionResponse (6 properties), RegisterNotificationResponse (6 properties), RegisterNotificationRequest (4 properties). Each schema is shown below with its type and property counts.

NotificationData
object
The model expected to trigger a notification
2 properties
RegisterNotificationRequest
object
This is the model expected for notification registration request.
4 properties
Error
object
Generic MADAPI error response
8 properties 2 required
RegisterNotificationResponse
object
This is the response expected for a notification registration request.
6 properties 2 required
DeleteNotificationSubscriptionResponse
object
The response for deleting a notification subscription
6 properties 2 required
SendNotificationResponse
object
The response expected after triggering a notification
4 properties 2 required
DeliveryReportRequest
object
This the request send to the delivery report url received in the send notification urls. It is used to notify the status of a notification to the party trigger…
4 properties
DeliveryReportResponse
object
This the response expected from the delivery report url received in the send notification request.
2 properties
NotificationResponse
object
This the response expected when the notification is delivered.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mtn-group-notification-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 Notification 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.