Trying to kick off a recording via the API instead of relying on the default queue settings. The goal is to start recording only when a specific skill is applied, then stop it later.
I’m hitting the POST /api/v2/recordings/conversations/{conversationId} endpoint with the standard auth header. The conversation ID is definitely active and valid, pulled directly from the WebSocket stream.
{
"recordingType": "internal"
}
Getting a 404 Not Found. The docs say this endpoint returns 200 OK or 404 if the conversation doesn’t exist. I’ve double-checked the ID format. It matches the UUID in the URI.
Tried adding externalRecordingId but that didn’t help. Also tested with a POSTMAN collection generated from the docs, same result.
Is there a specific permission required on the user profile to trigger recordings via API? The user has Supervisor role but maybe missing a specific capability? Or is the endpoint only available after the conversation has been bridged to an agent?