Open APIs

 View Only
Login to Join

About this Community:

Use this community as your go-to resource to discuss anything and everything relating to TM Forum Open APIs:

  • learn how to implement them
  • post ideas and requirement for new types of APIs
  • share how you are using APIs
  • discuss domain specific applications

This is an open discussion area. TM Forum also has collaborative project work on Open APIs. To find out more click here

Latest Discussion Posts

  • Hi, The latest TMF717 specification (v4.0.0) does not specify any placeholder for information related to Mobile number Portability (ex. Porting DateTime, Donor Operator, Recipient Operator etc.). The last version of API document was released on Feb2021 ...

  • Hi, I think nodoby will ever be happy with address attributes. Each country has different rules and needs! If you look at the information model (SID) for the Geographic Address ABE (GB922), you will see they've created multiple variations of address ...

  • Hi, The current TMF681 specification requires that the whole content of the customer notification needs to be passed from the API client. However that often leads to inconsistent communication going to the customers from different channels in a ...

  • Hi All, On the Medium Characteristics object , we are capturing the site address where engineer visit need to be done? But there are no placeholders available to capture building name and building number - does anyone know if TMF have any plans to ...

  • Hi Sylvie The latest update to TMFS008 - Service/Resource Catalog View for a Postpaid Mobile Line use case (3.1.0) has added a relationship directly between the eSIM product spec and the eSIM profile logical resource (see below). In earlier versions ...