Genesys Cloud - Developer Community!

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?

Good Day Patrick

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

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

Original Message:
Sent: 03-10-2026 16:10
From: Patrick Rohlf
Subject: Using Genesys APIs to disconnect inbound/outbound calls isn't working

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
------------------------------

Good Day Patrick

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

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?

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?

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

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?

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

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

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?

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

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

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?