Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Kin Lane

Chat with Kin

AI assistant · trained on my blog

TM Forum

TM Forum troubleTicketSpecification API

Operations for TroubleTicketSpecification Resource

Documentation Provider Profile APIs.io OpenAPI GitHub

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

Tagged areas include troubleTicketSpecification. 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.0.1, at version 5.0.0.

Requests are made against a single base URL, https://serverRoot/productCatalogManagement/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.0.1
API Version
5.0.0
Server
https://serverRoot/productCatalogManagement/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.

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

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
AE Profile APIs.io
TM Forum agreementSpecification API
AE Profile APIs.io
TM Forum billFormat API
AE Profile APIs.io
TM Forum billingAccount API
AE Profile APIs.io
TM Forum billingCycleSpecification API
AE Profile APIs.io
TM Forum billPresentationMedia API
AE Profile APIs.io
TM Forum cancelProductOrder API
AE Profile APIs.io
TM Forum cancelServiceOrder API
AE Profile APIs.io
TM Forum category API
AE Profile APIs.io
TM Forum customer API
AE Profile APIs.io
TM Forum events subscription API
AE Profile APIs.io
TM Forum exportJob API
AE Profile APIs.io
#troubleTicketSpecification
← Back to T APIs
API Details
ID
tm-forum:tm-forum-troubleticketspecification-api
Server
https://serverRoot/productCatalogManagement/v5/
Docs
https://www.tmforum.org/resources/specification/tmf620-product-catalog-management-api-rest-specification-r17-5-0/
Provider
TM Forum
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network