Recording API POST /recordings/recordings/stop returning 404 during active call

Trying to programmatically start and stop call recordings via the Recording API. The start call works fine when updating the recording state. When I try to stop the recording, I get a 404. I verified the ID is correct from the start response. Is there a delay before the stop operation becomes valid? Here is the payload I am sending: {“reason”: “agent_request”}. The recording is definitely active in the UI.

2 Likes