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 Trouble Ticket - TMF621

TMF621 Trouble Ticket Management Aggregator This service provides endpoint to fetch the ticket details with ticket id, create ticket, fetch list of tickets by customer id and update the existing tickets.

MTN TMF Trouble Ticket - TMF621 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, TMF621, Benin, Congo, and Cameroon. The published artifact set on APIs.io includes API documentation, an API reference, and an OpenAPI specification.

This API exposes 7 operations across 5 paths, and defines 28 schemas. It is described by OpenAPI 3.0.1, at version V1.

Requests are made against a single base URL, http://localhost:8083.

7 operations 5 paths 28 schemas 4 GET2 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

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

Paths & Operations 7

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

trouble-ticket-aggregator-controller 7
GET
/troubleTicket
This operation retrieves trouble ticket
listTickets 8 params → 200400401500
POST
/troubleTicket
This operation Creates a trouble ticket
createTicket 3 params body → 200400401500
GET
/troubleTicket/{id}
This operation retrieves a trouble ticket
viewTicket 6 params → 200400401500
PATCH
/troubleTicket/{id}
This operation updates a trouble ticket
updateTicket 4 params body → 200400401500
PATCH
/incident/{id}
This operation updates a trouble ticket category
updateIncidentCategory 4 params body → 200400401500
GET
/troubleTicket/category
This operation retrieves a trouble ticket category and sub category
getTroubleTicketCategory 11 params → 200400401500
GET
/incident/category
This operation retrieves a trouble ticket category and sub category
getIncidentCategory 11 params → 200400401500

Schemas 28

The contract defines 28 schemas that model the data the API accepts and returns. The most detailed are TroubleTicketResponse (51 properties), DCLMTroubleTicketAPIResponse (44 properties), CreateRequest (13 properties), TicketActivity (11 properties). Each schema is shown below with its type and property counts.

Attachments
object
5 properties
Channel
object
7 properties
CountryInformation
object
3 properties
CreateRequest
object
13 properties
RelatedEntity
object
5 properties
ValidFor
object
2 properties
ContactMedium
object
6 properties
EngagedParty
object
4 properties
Medium
object
4 properties
Note
object
5 properties
RelatedParty
object
10 properties
UpdateTicketRequest
object
9 properties
UpdateIncidentRequest
object
6 properties
Assignee
object
2 properties
Assignees
object
3 properties
CustomFields
object
4 properties
DCLMTroubleTicketAPIResponse
object
44 properties
ExternalSystem
object
1 property
Groups
object
4 properties
StatusChange
object
4 properties
TicketActivity
object
11 properties
TicketRelationship
object
7 properties
TroubleTicketRelationship
object
1 property
TroubleTicketResponse
object
51 properties
WorkFlowRef
object
7 properties
BadRequestErrorResponse
object
5 properties
UnauthorizedErrorResponse
object
5 properties
ServerErrorResponse
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mtn-group-tmf-trouble-ticket-tmf621.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 Trouble Ticket - TMF621, 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.