Open APIs

Expand all | Collapse all

TMF666_Account_Management_API_REST_Specification_R18.0.0 and TMF636_Billing_Management_API_REST_Specification_R14.5.1

  • 1.  TMF666_Account_Management_API_REST_Specification_R18.0.0 and TMF636_Billing_Management_API_REST_Specification_R14.5.1

    TM Forum Member
    Posted 10 days ago
    Dear Members ,

    We would like to implement TMF Billing APIs  for our existing billing products.
    We could able to manage two apis  TMF666 from below link as well one more api is available both  seems to have similarities except  TMF636 is having reference to Product Spec and SeriviceId.Which one is more  suitable to use ? Any  lead or suggestion on this will be appreciated.

    TMF636 -->

    https://www.tmforum.org/resources/interface/tmf636-billing-management-api-rest-specification-r14-5-0/

    TMF666-->

    https://projects.tmforum.org/wiki/display/API/Open+API+Table?_ga=2.77232853.1151755082.1562678902-1486349390.1553764465


    Sandeep





    ------------------------------
    sandeep singh
    Tecnotree
    ------------------------------


  • 2.  RE: TMF666_Account_Management_API_REST_Specification_R18.0.0 and TMF636_Billing_Management_API_REST_Specification_R14.5.1

    TM Forum Member
    Posted 9 days ago
    Hi Sandeep
    TMF636 was deprecated and replaced by two APIs TMF666 (Account Management) and TMF678 (Customer Bill Management).
    Probably you will need to implement both of these APIs (666 and 678) in your billing product, depending on what functionality you have.
    Hope it helps

    ------------------------------
    Jonathan Goldberg
    Amdocs Management Limited
    ------------------------------