Open APIs

 View Only
  • 1.  Event structure in TMF621 integrations

    Posted Nov 01, 2024 09:07

    Hi all,

    I have a very basic question. Within a TMF621 ticketing integration, who is responsible to define the structure of an event? The sender of the event (who is also the provider of the OpenApi for creation etc) or the receiver of an event?

    As I understood the aim of TMF621 is to become more independed in ticket integration. The sender of events will always send the same structure, regardless who is receiving the event. The receiver itself is responsible to pick the needed parameters. And if the received events don't contain parameters, which are needed for the own workflow, it has to be set by the receiver itself (fix values or something like that).

    The sender of the events needs not to know about any specialities of the receiving/consuming system.

    Am I right here?

    K.



    ------------------------------
    Katharina Gerlings
    TO BE VERIFIED
    ------------------------------


  • 2.  RE: Event structure in TMF621 integrations

    TM Forum Member
    Posted Nov 04, 2024 23:57

    Yes, that is also my understanding.  The API provider defines the events that are applicable to the particular API.  The event payload contains the content of the affected ABEs.

    The API consumer can typically provide a filter on the events that is wishes to consume.



    ------------------------------
    Dan d'Albuquerque
    Individual
    ------------------------------