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

  • Thanks Frederic for these alerts. I've checked the beta-published OAS files for 653 and 697, and they appear to be correct, both in the area of characteristics and for the Fields directive on retrieve. Perhaps you had an earlier version? '/serviceTest/{id}': ...

  • Another issue we noticed on these APIs (I already posted it some time ago on the TMForum) is that the Fields request parameter is missing from the retrieveXXX operations. ------------------------------ Frederic Thise Proximus SA ---------------- ...

  • Hi Jonathan, as far as we know in our implementations of TMF v5 APIs, TMF653 and TMF697 suffer the same issue. We fixed it internally by adding the missing definitions (from an API that was ok). Best regards, ------------------------------ Frederic ...

  • Hi Jan The whole area of Cost (and hence P&L) is not covered in the Open API at this time (I'm not sure what the situation is in the SID - information framework). There was some work being done by a CSP on a separate Cost API, but I don't know what ...

  • Hi George I'm afraid it's a defect, and I'll be opening a report to get this fixed. The OAS file for TMF629 should treat characteristics in the same way as for TMF632. You could in the meantime try making a private fix to the OAS file, but there's no ...