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

TM Forum Trouble Ticket Specification API

Operations for TroubleTicketSpecification Resource

TM Forum Trouble Ticket Specification API is one of 38 APIs that TM Forum publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

Requests are made against a single base URL, {apiRoot}/tmf-api/troubleTicket/v5/.

5 operations 2 paths 34 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
5.0.1
Server
{apiRoot}/tmf-api/troubleTicket/v5/
Resource Areas
1

Paths & Operations 5

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

troubleTicketSpecification 5

Operations for TroubleTicketSpecification Resource

GET
/troubleTicketSpecification
TM Forum List or Find TroubleTicketSpecification Objects
listTroubleTicketSpecification 7 params → 200400401403404405500501
POST
/troubleTicketSpecification
TM Forum Creates a TroubleTicketSpecification
createTroubleTicketSpecification 1 param body → 201202400401403404405409
GET
/troubleTicketSpecification/{id}
TM Forum Retrieves a TroubleTicketSpecification by ID
retrieveTroubleTicketSpecification 2 params → 200400401403404405500501
PATCH
/troubleTicketSpecification/{id}
TM Forum Updates Partially a TroubleTicketSpecification
patchTroubleTicketSpecification 2 params body → 200202400401403404405409
DELETE
/troubleTicketSpecification/{id}
TM Forum Deletes a TroubleTicketSpecification
deleteTroubleTicketSpecification 1 param → 202204400401403404405409

Schemas 34

The contract defines 34 schemas that model the data the API accepts and returns. The most detailed are JsonPatch (4 properties), Extensible (3 properties), TimePeriod (2 properties), Addressable (2 properties). Each schema is shown below with its type and property counts.

Addressable
object
Base schema for addressable entities
2 properties
TroubleTicketSpecification
RelatedPartyRefOrPartyRoleRef_MVO
RelatedPartyRefOrPartyRoleRef
EntityRef
CharacteristicSpecification_MVO
PartyRef_FVO
object
A Party reference
EntityRef_MVO
PartyRefOrPartyRoleRef_FVO
object
JsonPatch
object
A JSONPatch document as defined by RFC 6902
4 properties 2 required
TroubleTicketSpecification_FVO
CharacteristicSpecificationRelationship_MVO
PartyRoleRef_MVO
TroubleTicketSpecification_MVO
CharacteristicSpecificationRelationship
PartyRefOrPartyRoleRef
object
CharacteristicValueSpecification
Entity
object
Base entity schema for use in TMForum Open-APIs. Property.
Error
Used when an API throws an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx)
TimePeriod
object
A period of time, either as a deadline (endDateTime only) a startDateTime only, or both
2 properties
TroubleTicketSpecification_RES
object
Response object for TroubleTicketSpecification
2 required
RelatedPartyRefOrPartyRoleRef_FVO
CharacteristicSpecificationRelationship_FVO
PartyRefOrPartyRoleRef_MVO
object
CharacteristicSpecification_FVO
PartyRoleRef
JsonPatchOperations
array
JSONPatch Operations document as defined by RFC 6902
PartyRef_MVO
object
A Party reference
PartyRef
object
A Party reference
CharacteristicSpecification
CharacteristicValueSpecification_FVO
CharacteristicValueSpecification_MVO
PartyRoleRef_FVO
Extensible
object
Base Extensible schema for use in TMForum Open-APIs - When used for in a schema it means that the Entity described by the schema MUST be extended with the @type
3 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tm-forum-troubleticketspecification-api-openapi.yml Raw ↑

Other APIs TM Forum publishes across the network.

TM Forum Agreement API
TM Forum Agreement Specification API
TM Forum Bill Format API
TM Forum Billing Cycle Specification API
TM Forum Bill Presentation Media API
TM Forum Cancel Product Order API
TM Forum Cancel Service Order API
TM Forum Category API
TM Forum Customer API
TM Forum events subscription API
TM Forum Individual API
TM Forum notification listener API
Where this information came from

This is an independent, third-party profile of TM Forum Trouble Ticket Specification 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.