Unknown parameter custom_voice_id when getting ephemeral token

This was working fine an hour ago, but now suddenly calls to /v1/realtime/sessions is returning the error:
“error”: {
“message”: “Unknown parameter: ‘custom_voice_id’.”,
“type”: “invalid_request_error”,
“param”: “custom_voice_id”,
“code”: “unknown_parameter”
}
I’ve checked its not a bug in my code by doing a plain curl:
$ curl -X POST --stripped–/v1/realtime/sessions \

-H “Authorization: Bearer sk-proj-V–obfuscated–O”
-H “Content-Type: application/json”
-d ‘{
“model”: “gpt-4o-realtime-preview-2024-12-17”,
ities": [“audio”> “modalities”: [“audio”, “text”],
“instructions”: “You are a friendly assistant.”
}’
{
“error”: {
“message”: “Unknown parameter: ‘custom_voice_id’.”,
“type”: “invalid_request_error”,
“param”: “custom_voice_id”,
“code”: “unknown_parameter”
}
}

Has something changed? Anybody else seeing this?

4 Likes

I encounter the same issue.

3 Likes

I’m also getting this error via the WebSocket API

3 Likes

The same problem :frowning: Playground also doesn’t work

2 Likes

We are having the same issue!

1 Like

Thanks for taking the time to flag this, I’ve passed it on.

1 Like

Realtime API is coming back now! Thanks again!

1 Like

It looks like they work on the file storage at the moment.
Like everything file related is messed up.
Image upload, downloads of chatgpt exports, … I’d say just give them 1-2 weeks to fix it :smiling_face_with_tear:

Seems to be working again - thanks for quick response @Foxalabs

2 Likes