Input_audio_buffer.append event_id behaviour

API
, ,
1

As per documentation, this event type input_audio_buffer.append accepts a custom event_id My question is what’s the purpose of it? Does that mean the response.audio.delta and the response.done that I will be receiving will echo the event_id that I sent via input_audio_buffer.append ?

And while we are in the topic of input_audio_buffer.append , Where does it append the audio? Or that event type is not limited on appending? Meaning if there’s no input_audio_buffer then it will create its own and generate an id that I don’t know?

2

this message allows you to send audio from your user to the model. Its basically like adding to the most recent “user” message in a chat conversation, but its steaming the audio FROM the user (where traditionally in text we only stream the text that comes BACK from the model).

The buffer its appending to is the state server side that eventually feeds the input tokenizer for the realtime model when you “commit”, or in real time if you’re configured that way.