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

  • I think that correlatorID is intended for a consumer to refer a refund or a payment to its own records (semantically I would have preferred to use ExternalIdentifier for this). Payment has a list of PaymentItems, where each item has an entity reference ...

  • Hi Rupen Firstly, let's reverse your question to align the terminology. You are asking if there is an attribute (or property ) to control product characteristic visibility. There is indeed a property configurable on characteristic specification, ...

  • Thanks Matthieu and Jonathan for response. Essentially to summarize we could use Refund resource defined in TMF 676 Payment Management API and associate it to an Account, but there is no means to know refund came about as part of which ProductOrder ...

  • Hi All, Is there a characteristic to control product attribute visibility in TMF 620? I presume product specification characteristics should control whether the attribute needs to be made visible whilst selling or can be visible and/or editable ...

  • Firstly, TMF as an organization doesn't generally recommend anything in API definitions. If you are looking for recommendations, they will typically be found in Implementation Guides (IGxxxx). I'm not aware of one that deals with quantity, but maybe you'll ...

Announcements