Trying to start a recording programmatically via the API on a conversation that already has an active recording session. The docs say to use PUT /api/v2/recording/jobs, but I keep hitting a 409 Conflict. The error message is vague about what state the conversation needs to be in.
PUT /api/v2/recording/jobs
Content-Type: application/json
{
"conversationId": "abc-123-def",
"action": "start",
"type": "voice"
}
Response is 409: “The resource you are trying to create already exists.” I’ve checked the conversation details and the recording status is definitely active. Should I be checking for an existing job ID first? Or is there a different endpoint to toggle the state? I’ve tried deleting the job first but that stops the recording entirely, which isn’t what I want. Just trying to restart or force a new segment.