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 SMS v3 API

Provides a Restful API to expose SMS capability for sending of messages , Mobile originating messages and Delivery Receipts.

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

This API exposes 4 operations across 3 paths, organized into 2 resource areas, and defines 11 schemas. It is described by OpenAPI 2.0, at version 1.0.

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

4 operations 3 paths 11 schemas 1 DELETE1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 2.0
API Version
1.0
Base URL
https://api.mtn.com/v3/sms/
Authentication
OAuth 2.0
Resource Areas
2

Authentication & Security 1

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

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 1 DELETE, 1 PATCH, 2 POST. They span 2 resource areas: Sending SMS, Subscribing for Mobile Originating and Delivery Receipts. Each is listed below with its method, path, parameters, and response codes.

Sending SMS 1
POST
/messages/sms/outbound
This operation is used to send an outbound SMS message to the provided recipients.
1 param → 200401404407500
Subscribing for Mobile Originating and Delivery Receipts 3
POST
/messages/sms/subscription
Create subscription to register a serviceCode, callback url and a delivery report url for mobile originating and Delivery Receipts.
2 params → 200401403404407500
PATCH
/messages/sms/subscription/{subscriptionId}
Update a subscription information based on an already existing subscriptionId.
3 params → 200401404407500
DELETE
/messages/sms/subscription/{subscriptionId}
Delete subscription or registration details based on the provided subscriptionId.
2 params → 200401404407500

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are DeliveryNotificationRequest (9 properties), ErrorPatch (7 properties), ForbiddenResponse (7 properties), outboundSMSMessageRequest (7 properties). Each schema is shown below with its type and property counts.

outboundSMSMessageRequest
object
7 properties 4 required
resourceReference
object
4 properties 4 required
status
string
SMS delivery status.
UpdateSubscriptionRequest
object
5 properties
ShortCodeSubscription
object
4 properties 3 required
subscriptionResponse
object
4 properties 4 required
outboundSubscriptionDeleteResponse
object
4 properties 4 required
DeliveryNotificationRequest
object
This message body highlights the json message that will be sent to a third party endpoint to report the status of a message delivery.
9 properties
ForbiddenResponse
object
7 properties 3 required
ErrorPatch
object
7 properties 3 required
Error
object
7 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mtn-group-sms-v3-api.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 SMS v3 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.