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

MTN SMS Messaging API allowing developers to include SMS messaging in their applications.

MTN SMS 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 and Nigeria. The published artifact set on APIs.io includes API documentation, an API reference, and an OpenAPI specification.

This API exposes 5 operations across 4 paths, and defines 9 schemas. It is described by OpenAPI 2.0, at version 1.0.0.

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

5 operations 4 paths 9 schemas 1 DELETE2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 2.0
API Version
1.0.0
Base URL
https://api.mtn.com/v1/messages/
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

MTN SMS declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2) using the application flow.

Paths & Operations 5

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

Communication 5
POST
/sms
Send SMS
sendSMS 1 param → 201400401403404405415500
GET
/sms
Receive SMS Responses
Retrieve SMS Responses 1 param → 200400401403404405415500
GET
/sms/{messageId}/status
Delivery status
Get SMS Status 1 param → 200400401403404405415500
POST
/sms-listeners
Register listener
registerCallback 1 param → 201400401403404405409500
DELETE
/sms-listeners/{accessCode}
Remove callback listener
deregister Callback 1 param → 204400401403404405409500

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are SendSMS (5 properties), CallbackResponse (4 properties), Message (4 properties), OutboundPollResponse (4 properties). Each schema is shown below with its type and property counts.

Error
object
3 properties 2 required
CallbackResponse
object
4 properties 2 required
CallbackInfo
object
3 properties 1 required
MessageSentResponseSMS
object
1 property 1 required
Message
object
4 properties 4 required
OutboundPollResponse
object
4 properties
Status
string
SendSMS
object
5 properties 2 required
ReceivePollResponse
object
Poll for incoming messages specifying the number of messages to receive
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mtn-group-mtn-sms-api-v1.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, 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.