Genesys Cloud - Developer Community!

 View Only

Sign Up

  • 1.  Using Genesys APIs to disconnect inbound/outbound calls isn't working

    Posted 03-10-2026 16:10

    We're trying to use Genesys APIs to disconnect different interaction types.

    So far, we've been able to successfully call PATCH endpoints for:

    - Emails | /v2/conversations/emails/{interactionId}/participants/{participantId}/communications/{communicationId}

    - Messages | /v2/conversations/messages/{interactionId}/participants/{participantId}/communications/{communicationId}

    to disconnect email and message interactions respectively.


    But when we try to call PATCH /v2/conversations/calls/{interactionId}/participants/{participantId}/communications/{communicationId} to disconnect a call type interaction, we get the following error: 

    {
        "message": "This request requires a user context. Client credentials cannot be used for requests to this resource.",
        "code": "not.a.user",
        "status": 400,
        "contextId": "63338f99-c7ac-433e-858a-13ae536ece72",
        "details": [],
        "errors": []
    }

    Is this a matter of needing to update to a different OAuth type for our external web client or is there something else that we need to take a look at?


    #PlatformAPI

    ------------------------------
    Patrick Rohlf
    Contact Center Technologies Implementation Engineer
    ------------------------------


  • 2.  RE: Using Genesys APIs to disconnect inbound/outbound calls isn't working

    Posted 03-11-2026 03:55

    Good Day Patrick

    I found this on the developer API explorer - /api/v2/conversations/calls/{conversationId}/participants/{participantId}/communications/{communicationId}

    I noticed that you have /v2/conversations/calls/{interactionId} and the API is /api/v2/conversations/calls/{conversationId}
    Regards


    ------------------------------
    Stephan Taljaard
    EMBEDIT s.r.o
    ------------------------------



  • 3.  RE: Using Genesys APIs to disconnect inbound/outbound calls isn't working

    Posted 03-11-2026 11:00
    Edited by Vinod Prabhu 03-11-2026 11:05

    I'm a developer working with Patrick on this. InteractionId is a deprecated term for conversationId, but yes, we are calling /api/v2/conversations/calls/{conversationId}/participants/{participantId}/communications/{communicationId} with that value. The API succeeds for messages and emails, just not for calls. 



    ------------------------------
    Vinod Prabhu
    ------------------------------

    Original Message


  • 4.  RE: Using Genesys APIs to disconnect inbound/outbound calls isn't working

    Posted 03-13-2026 16:26

    Yes, the API you suggested is also the one that we tried which is returning this error...

    {
        "message": "This request requires a user context. Client credentials cannot be used for requests to this resource.",
        "code": "not.a.user",
        "status": 400,
        "contextId": "63338f99-c7ac-433e-858a-13ae536ece72",
        "details": [],
        "errors": []
    }



    ------------------------------
    Patrick Rohlf
    Contact Center Technologies Implementation Engineer
    ------------------------------

    Original Message


  • 5.  RE: Using Genesys APIs to disconnect inbound/outbound calls isn't working

    Posted 03-11-2026 07:34

    I found this on the developer API explorer - /api/v2/conversations/calls/{conversationId}/participants/{participantId}/communications/{communicationId}



    ------------------------------
    Alex Sander Felicio
    ------------------------------



  • 6.  RE: Using Genesys APIs to disconnect inbound/outbound calls isn't working

    Posted 03-12-2026 06:16

    Did you try using /api/v2/conversations/{conversationId}/disconnect



    ------------------------------
    Vineet Kakroo
    Senior Technical Consultant
    ------------------------------

    Original Message


  • 7.  RE: Using Genesys APIs to disconnect inbound/outbound calls isn't working

    Posted 03-12-2026 07:31

    Hi Vineet,

    Yes, what you posted is the right one. I have used /api/v2/conversations/{conversationId}/disconnect it before.



    ------------------------------
    Phaneendra
    Technical Solutions Consultant
    ------------------------------

    Original Message


  • 8.  RE: Using Genesys APIs to disconnect inbound/outbound calls isn't working

    Posted 03-13-2026 14:53

    I see. So you are suggesting we use the global disconnect API which supports the 'Disconnect Interactions' page in the Genesys Cloud app.

    This wasn't our first option, since Genesys has been threatening that the feature could go away (granted, that's been for many years now ;P )...


    But, if that's our best option, then that's what we will consider. 

    Thank you for the input. Cheers!



    ------------------------------
    Patrick Rohlf
    Contact Center Technologies Implementation Engineer
    ------------------------------

    Original Message


Related Content