I’ve been POCing with the Realtime API and it’s been great! However sometime in the last 1-2 hours, the /v1/realtime/sessions endpoint has stopped returning a valid session response and is instead returning an error about an undocumented “custom_voice_id” - I presume this is because of new functionality being rolled out, but wanted to know if anyone else was experiencing and if we could get an ETA to either restoration of the Realtime API’s functionality or documentation on what needs to be done differently if a backwards incompatible update has been rolled out.
I’m currently receiving this response from a (previously valid) request to /v1/realtime/sessions:
{
"error": {
"code": "unknown_parameter",
"message": "Unknown parameter: 'custom_voice_id'.",
"param": "custom_voice_id",
"type": "invalid_request_error"
}
}
Prior to ~1.5hrs ago, I would receive a response like this from the /v1/realtime/sessions endpoint:
{
"id": "sess_001",
"object": "realtime.session",
"model": "gpt-4o-realtime-preview-2024-12-17",
"modalities": ["audio", "text"],
"instructions": "You are a friendly assistant.",
"voice": "alloy",
"input_audio_format": "pcm16",
"output_audio_format": "pcm16",
"input_audio_transcription": {
"model": "whisper-1"
},
"turn_detection": null,
"tools": [],
"tool_choice": "none",
"temperature": 0.7,
"max_response_output_tokens": 200,
"client_secret": {
"value": "ek_abc123",
"expires_at": 1234567890
}
}
Any guidance or support would be appreciated!