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 productSpecification API

Operations for ProductSpecification Resource

TM Forum productSpecification 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 Product 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 74 schemas. It is described by OpenAPI 3.2.0, at version 5.0.0.

Requests are made against a single base URL, https://serverRoot/productCatalogManagement/v5/.

5 operations 2 paths 74 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.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.

productSpecification 5

Operations for ProductSpecification Resource

GET
/productSpecification
TM Forum List or Find ProductSpecification Objects
listProductSpecification 3 params → 200400401403404405500501
POST
/productSpecification
TM Forum Creates a ProductSpecification
createProductSpecification 1 param body → 201202400401403404405409
GET
/productSpecification/{id}
TM Forum Retrieves a ProductSpecification by ID
retrieveProductSpecification 2 params → 200400401403404405500501
PATCH
/productSpecification/{id}
TM Forum Updates Partially a ProductSpecification
patchProductSpecification 2 params body → 200202400401403404405409
DELETE
/productSpecification/{id}
TM Forum Deletes a ProductSpecification
deleteProductSpecification 1 param → 202204400401403404405409

Schemas 74

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

CharacteristicValueSpecification_MVO
PartyRoleRef_MVO
IntentSpecificationRef_FVO
object
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.
Attachment_MVO
ProductSpecificationRelationship_MVO
PartyRef
object
A Party reference
CategoryRef
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
CharacteristicSpecification
PolicyRef
CharacteristicSpecificationRelationship
PartyRoleRef
PartyRefOrPartyRoleRef_FVO
object
JsonPatch
object
A JSONPatch document as defined by RFC 6902
4 properties 2 required
AttachmentRef_FVO
PartyRefOrPartyRoleRef
object
CharacteristicValueSpecification_FVO
Error
Used when an API throws an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx)
ServiceSpecificationRef_FVO
PartyRoleRef_FVO
CharacteristicSpecificationRelationship_FVO
ExternalIdentifier_MVO
ProductSpecification_FVO
CategoryRef_FVO
ProductSpecification
RelatedPartyRefOrPartyRoleRef_FVO
BundledProductSpecification
Entity_FVO
object
Base entity schema for use in TMForum Open-APIs. Property.
PolicyRef_FVO
ProductSpecificationRelationship_FVO
AttachmentRef_MVO
PartyRef_MVO
object
A Party reference
IntentSpecificationRef
object
PartyRef_FVO
object
A Party reference
ExternalIdentifier
AttachmentRef
ProductSpecification_MVO
CharacteristicValueSpecification
EntityRef_FVO
ResourceSpecificationRef_FVO
BundledProductSpecification_FVO
TargetProductSchema_MVO
object
The reference object to the schema and type of target product which is described by product specification
2 properties
Extensible_FVO
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
Entity_MVO
object
Base entity schema for use in TMForum Open-APIs. Property.
Attachment
TargetProductSchema_FVO
object
The reference object to the schema and type of target product which is described by product specification
2 properties 2 required
CategoryRef_MVO
EntityRef
Addressable_FVO
object
Base schema for adressable entities
1 property
AttachmentRefOrValue_MVO
object
The polymorphic attributes @type, @schemaLocation & @referredType are related to the Attachment entity and not the AttachmentRefOrValue class itself
PartyRefOrPartyRoleRef_MVO
object
Quantity
object
An amount in a given unit
2 properties
IntentSpecificationRef_MVO
object
AttachmentRefOrValue_FVO
object
The polymorphic attributes @type, @schemaLocation & @referredType are related to the Attachment entity and not the AttachmentRefOrValue class itself
TargetProductSchema
object
The reference object to the schema and type of target product which is described by product specification
2 properties
RelatedPartyRefOrPartyRoleRef_MVO
ExternalIdentifier_FVO
CharacteristicSpecificationRelationship_MVO
ServiceSpecificationRef
AttachmentRefOrValue
object
The polymorphic attributes @type, @schemaLocation & @referredType are related to the Attachment entity and not the AttachmentRefOrValue class itself
ResourceSpecificationRef_MVO
CharacteristicSpecification_FVO
CharacteristicSpecification_MVO
Addressable
object
Base schema for adressable entities
2 properties
ServiceSpecificationRef_MVO
JsonPatchOperations
array
JSONPatch Operations document as defined by RFC 6902
RelatedPartyRefOrPartyRoleRef
BundledProductSpecification_MVO
Attachment_FVO
ResourceSpecificationRef
PolicyRef_MVO
ProductSpecificationRelationship

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs TM Forum publishes across the network.

TM Forum agreement API
TM Forum agreementSpecification API
TM Forum billFormat API
TM Forum billingAccount API
TM Forum billingCycleSpecification API
TM Forum billPresentationMedia API
TM Forum cancelProductOrder API
TM Forum cancelServiceOrder API
TM Forum category API
TM Forum customer API
TM Forum events subscription API
TM Forum exportJob API
Where this information came from

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