Open APIs

 View Only
  • 1.  TMF641 - Account level disconnect

    TM Forum Member
    Posted 8 days ago

    Want to support account level disconnect without listing all the services belonging to the account/customer.

    My view is to use POST /serviceOrder with action = delete & accountNumber. May be add a service.Category = AccountDisconnect

    In the body can I only use seviceOrderItem with action and service.characteristics with accountNumber name-value? What about serviceOrderItem.service.id, is this mandatory?



    ------------------------------
    Muna Munshi
    Nokia
    ------------------------------


  • 2.  RE: TMF641 - Account level disconnect

    TM Forum Member
    Posted 7 days ago
    Edited by Abel Ruiz Huerta 7 days ago

    Hi Muna,

    I'm not entirely sure what you mean by "Account level disconnect." If you're referring to the deactivation of a customer's billing account, I'd say that API 641 might not be the most suitable option for that, as it's primarily designed to manage services through orders.

    In the case of a disconnection, I'd say it's absolutely necessary to provide the ID of the service you want to deactivate.

    Instead, there is the TMF666 Account Management API, which is intended to manage the account lifecycle. The deactivation of an account could eventually trigger the deactivation of any active services associated with the account by internally calling API 641.

    Best regards,



    ------------------------------
    Abel Ruiz Huerta
    alvatross
    ------------------------------