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 TMF Service Activation - TMF640

Service Activation and Configuration API goal is to provide the ability to activate and configure Service. This API features Monitor pattern allowing to manage service configuration/activation asynchronous request (server side will provide monitor as POST/PATCH response).

MTN TMF Service Activation - TMF640 is one of 119 APIs that MTN Group publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include TM Forum, TMF640, Benin, Eswatini, and Zambia. The published artifact set on APIs.io includes API documentation, an API reference, and an OpenAPI specification.

This API exposes 10 operations across 6 paths, organized into 3 resource areas, and defines 29 schemas. It is described by OpenAPI 3.0.1, at version 1.0.0.

Requests are made against a single base URL, https://api.mtn.com/.

10 operations 6 paths 29 schemas 1 DELETE2 GET2 PATCH4 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0.0
Base URL
https://api.mtn.com/
License
Resource Areas
3

Paths & Operations 10

Across 6 paths, the API surfaces 10 operations — 1 DELETE, 2 GET, 2 PATCH, 4 POST, 1 PUT. They span 3 resource areas: service-activation-controller, netflix-integration-controller, license-aggregator-controller. Each is listed below with its method, path, parameters, and response codes.

service-activation-controller 2
GET
/service/{id}
Retrieves a Service by ID
retrieveStatus 10 params → 200400401500
PUT
/service/{id}
Updates the status of a Service
updateStatus 3 params body → 200400401500
netflix-integration-controller 5
DELETE
/service/{id}
This operation deletes a Subscriber
netflixIntegrationDeleteReq 6 params body → 204400401500
PATCH
/service/{id}
This operation upgrades a Service entity
netflixIntegrationUpgrade 5 params body → 200400401500
POST
/service
This operation creates a Service entity
netflixIntegrationEnroll 4 params body → 200400401500
POST
/service/callback/{countryCode}/{consumer}/{requestType}
This operation deletes a Subscriber
bokuCallBack 4 params body → 200400401500
POST
/bundle/callback/{entitlementType}
Boku Call Back
callBack 1 param body → 200400401500
license-aggregator-controller 3
POST
/service/license
Create a new license for a specified target system.
createLicense 2 params body → 200400401500
GET
/service/license/{id}
Retrieve license details using ID
esetGetLicense 4 params → 200400401500
PATCH
/service/license/{id}
Update license details for a given ID
updateLicense 6 params body → 200400401500

Schemas 29

The contract defines 29 schemas that model the data the API accepts and returns. The most detailed are ApiResponse (31 properties), LicenseRequest (16 properties), Service (14 properties), BokuCallback (9 properties). Each schema is shown below with its type and property counts.

ActHLRfresh
object
2 properties
APIResponse
object
1 property
Links
object
AdditionalInfo
object
2 properties
Feature
object
1 property
RelatedEntity
object
4 properties
RelatedParty
object
6 properties
RelatedServiceOrderItem
object
7 properties
Service
object
14 properties
ServiceCharacteristics
object
3 properties
ServiceSpecification
object
4 properties
LicenseRequest
object
16 properties
Note
object
2 properties
Payment
object
4 properties
ServiceOrderItem
object
4 properties
Validity
object
2 properties
BokuCallbackResponse
object
5 properties
BokuCallback
object
9 properties
ApiResponse
object
31 properties
Bundle
object
3 properties
FeatureCharacteristics
object
3 properties
Plan
object
2 properties
SpServiceCharacteristics
object
2 properties
Subscription
object
1 property
SupportingService
object
2 properties
BadRequestErrorResponse
object
5 properties
UnauthorizedErrorResponse
object
5 properties
ServerErrorResponse
object
5 properties
Link
object
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mtn-group-tmf-service-activation-tmf678.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 TMF Service Activation - TMF640, 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.