Open APIs

Hi everyone,

I'm currently working on implementing the Customer360 Management API (TMF717) and have run into a bit of confusion: the Customer360 resource appears in at least three different forms across TM Forum materials:

1. Narrative Spec (PDF/HTML) 

2. Example Payloads 

3. OpenAPI customer360.yaml

Because of these discrepancies, I'm not sure which version to trust as the "canonical" schema for code generation and validation.

• Is there a single source of truth for Customer360 v4 (or v5) that we should use?

• Are the differences intentional-e.g., narrative vs. simplified vs. full‑blown schemas-or are some of these simply out of sync?

• Will there be an upcoming alignment or errata publication to reconcile the variations?

Any guidance or pointers to an authoritative spec would be greatly appreciated!

Thanks in advance for your help.

V5 uses new tooling that ensures that all the resource samples, operation samples and notification samples are in sync with the API schema (OAS).  For V4, this was very much a manual process that has, as you have pointed out, led to inconsistencies.

As a result, the TMF717 V5 API  should be more consistent than V4, but it is currently in preview state which means that there could be feedback from the wider community leading to minor corrections to the API, even potentially to some of the fields.  The latest version in development is V5.0.1 and was last updated at the end of January.  @Abhilash Prasad, @Abhilash Prasad may have a more up-to-date view as to when the API will be published.

Thank you @Dan d'Albuquerque for your response. 👍

After reviewing all materials and careful consideration, we are considering adopting the Conformance Profile document as our definitive schema reference for the implementation

Hi @TS Ph,

V5 version is generated using tool and take care of the inconsistencies of v4 versions due to manual process.

I would encourage you to use V5 version of TMF717 API

You can connect with me separately for any clarification on TMF717 Customer360 API

Thanks.