Recording API 404 when starting recording for specific conversation

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 trying to update the recording state for the conversation using the API 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. 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?

3 Likes