DELETE /api/v2/conversations/conferences/{conversationId}/participants/{participantId} hanging on active call

  • Genesys Cloud v2 API
  • Python requests library
  • JWT token with conversation:control scope

Quick question about disconnecting a specific participant from a conference call. I’m hitting the endpoint DELETE /api/v2/conversations/conferences/{conversationId}/participants/{participantId} and it just hangs. No timeout, no error, just silence until my client gives up after 60s.

The call is live. The participant is definitely in the conference. I’ve verified the token scopes. Here’s the snippet:

import requests

headers = {
 'Authorization': f'Bearer {token}',
 'Content-Type': 'application/json'
}

resp = requests.delete(
 f'https://api.mypurecloud.com/api/v2/conversations/conferences/{conv_id}/participants/{part_id}',
 headers=headers,
 timeout=30
)
print(resp.status_code)

I’m seeing this behavior consistently for calls that have been active for more than 5 minutes. Fresh calls work fine. Is there a server-side lock on long-running conferences? Or am I missing a header? The docs don’t mention any special conditions for active participants. Feels like a race condition on the server. i’ve tried adding X-Genesys-Idempotency-Key but that didn’t help. any ideas?