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 Group Service Order API

The serviceOrder API from MTN Group — 2 operation(s) for serviceorder.

MTN Group Service Order API is one of 148 APIs that MTN Group publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 2 operations across 2 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version 4.1.0.

Requests are made against a single base URL, https://serverRoot/tmf-api/serviceOrdering/v4.

2 operations 2 paths 14 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

MTN Group Service Order API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2) using the clientCredentials flow. By default, every request must be authenticated.

Paths & Operations 2

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

serviceOrder 2
POST
/serviceOrder
Creates a ServiceOrder
createServiceOrder 2 params body → 200400401403404405500
GET
/serviceOrder/{id}
Retrieves a ServiceOrder by ID
retrieveServiceOrder 4 params → 200400401404500

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are ServiceOrder_Create (7 properties), Error500 (6 properties), CreateServiceOrder_SuccessResponse (6 properties), Package (5 properties). Each schema is shown below with its type and property counts.

Feature
object
2 properties 2 required
Error404
object
5 properties
Error400
object
5 properties
Package
object
5 properties 1 required
Error405
object
5 properties
Error401
object
5 properties
Error403
object
4 properties
Error500
object
6 properties
Service
object
3 properties
ServiceOrderItem
object
3 properties 2 required
ServiceOrder_Create
object
7 properties 5 required
Product
object
3 properties 2 required
GetServiceOrderResponse
object
5 properties
CreateServiceOrder_SuccessResponse
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mtn-group-serviceorder-api-openapi.yml Raw ↑

Other APIs MTN Group publishes across the network.

MTN MoMo Collection API
MTN MoMo Disbursements API
MTN MoMo Remittance API
MTN MoMo Sandbox User Provisioning API
MTN Group Accessible to 3PP API
MTN Group Accessible to USSD Gateway API
MTN Group Activation API
MTN Group Add User API
MTN Group Admin Suspend API
MTN Group Adverts API
MTN Group Advice Reconcile API
MTN Group Agents API
Where this information came from

This is an independent, third-party profile of MTN Group Service Order 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.