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 Service Ordering

TMF API Reference : TMF 641 - Service Ordering Management Version 4.1 TMF641 performs the following operations on service order resource : - Retrieval of a service order or a collection of service orders by id - Creation of a service order - Deletion of service order Copyright © TM Forum 2020. All Rights Reserved.

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

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

Requests are made against the base URL https://api.mtn.com/tmf-api/serviceOrdering/v4.

2 operations 2 paths 15 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 2.0
API Version
4.1.0
Base URL
https://api.mtn.com/tmf-api/serviceOrdering/v4
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

MTN Service Ordering 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 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 3 params → 200400401403404405500
GET
/serviceOrder/{id}
Retrieves a ServiceOrder by ID
retrieveServiceOrder 4 params → 200400401404500

Schemas 15

The contract defines 15 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), Error401 (5 properties). Each schema is shown below with its type and property counts.

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

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mtn-group-service-ordering.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 BSS TT OAuth V1
MTN Balance Management V1
Where this information came from

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