Open APIs

 View Only

  • 1.  TMF680 API, adding MSISDN additional query parameter

    Posted Sep 04, 2020 09:07

    Hi Members,

    Recently, we are working on a recommendation API implementation as per   TMF680 Recommendation API Specification,  Release:18.0.0, Version:v2.0 (found here https://projects.tmforum.org/wiki/display/API/Open+API+Table).

     

    We got a requirement of   "getting recommendation for a party associated by  its MSISDN (Mobile Subscriber ISDN Number)" i.e. we need to use  MSISDN value as one of the query parameters in the recommendation API.

     

    It seems, in our case, we can use Party object or extend it to support MSISDN as additional query parameter. Could anyone please suggest what would be the recommended way of doing it.

     

    Best Regards

    Abdul Wazed

    Ericsson Inc



    ------------------------------
    Abdul Wazed
    Ericsson Inc.
    ------------------------------


  • 2.  RE: TMF680 API, adding MSISDN additional query parameter

    Posted Sep 06, 2020 03:43
    Hi Abdul
    Please note that as part of our republication effort for APIs v4, including alignment with latest design guidelines, Recommendation API has been released for early adoption in v4, see the early adoption table here. So you may want to consider adopting this latest version. @Gregoire Laurent leads this API, so he may be able to give advice on your specific use case.
    Hope it helps.​

    ------------------------------
    Jonathan Goldberg
    Amdocs Management Limited
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
    ------------------------------



  • 3.  RE: TMF680 API, adding MSISDN additional query parameter

    Posted Sep 08, 2020 02:43

    Hi Jonathan,

    Thanks a lot for your reply. I have gone through the latest release v4.0 swagger specification found here , but still it does not mention about use of the MSISDN attribute as additional query parameter. So, adopting the latest specification would not solve our use case as of now. @Gregoire Laurent: Could you please recommend solution approach for this use case.



    ------------------------------
    Abdul Wazed
    Ericsson Inc.
    ------------------------------

    Original Message


Related Content