Legacy Dev Forum Posts

 View Only

Sign Up

Disconnect conference call

  • 1.  Disconnect conference call

    Posted 06-05-2025 18:10

    lasator | 2016-09-26 18:31:17 UTC | #1

    I'm using the REST API directly. I have a three party conference call going and attempt to use:

    https://api.mypurecloud.com/api/v2/conversations/calls/ + idofcall

    I get a 403 unauthorized response with a basic agent. However, this call works if the user is also an administrator. Is this expected behavior?

    I can use:

    https://api.mypurecloud.com/api/v2/conversations/calls/ + idofcall + /participants/ + idofagent_participant

    This removes the agent from the call but the other parties are still talking. What is the proper way for an agent to terminate the entire conference call?


    anon53696493 | 2016-09-27 16:47:59 UTC | #2

    https://api.mypurecloud.com/api/v2/conversations/calls/ + idofcall This request requires the conversation:communication:disconnect permission as it allows you to end conversations that you are not a part of.

    If you want to have a way for one person to end the entire conference, then you would need to have them issue the https://api.mypurecloud.com/api/v2/conversations/calls/ + id_of_call + /participants/ + id_of_agent_participant request for each active participant on the conversation. Or you can assign the permission above to the user to allow them to do it with a single request.


    lasator | 2016-09-27 16:52:52 UTC | #3

    It might be useful to have any permission based limitations included in the api documentation


    chuck.pulfer | 2016-09-28 13:16:29 UTC | #4

    The 403 error response body should include the name of the missing permission. Check the response body and if it doesn't include the permission let me know and we'll get it added.


    system | 2017-08-28 19:27:31 UTC | #5


    This post was migrated from the old Developer Forum.

    ref: 434