Open APIs

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

  • Vance, I see that TMF640 is no longer applicable for Resource Activation & Configuration and that the ongoing work of TMF702 will take it up. Regarding TMF664, I think there's a misunderstanding there. Note that TMF664 is not about the resources but ...

  • Jonathan, Splitting both make the things more clear, indeed. I will take a look and follow TMF702 progress. I would then suggest that the description of TMF640 is updated. This is how it is today : " The REST API for Activation and Configuration ...

  • Ludovic, I also feel a bit "step-back" on that approach via TMF641 but I was checking if it was even a possibility. Well, instead of TMF638, I had in mind to make it via TMF640. Basically, we would need to do still the call on TMF641 to get the service ...

  • Hi Carlos This is a very good question! From my perspective the guideline did not rules against: The "depth" is used to expand the level of referenced (related) entities  But still I will be a bit unconfortable that service order will then be used ...

  • Hello Vishal In fact...both UC can be managed. See examples based on Trouble Ticket but logic is the same. If you POST a Hub with following: POST {api_url}/HUB Accept: application/json {"callback": http://in.listener.com, "query":"eventType = TicketStateChangeNotification" } ​ ...