BUG : `file_search` annotations are coming up as `ResponseAudioDeltaEvent`

[dominpm]

Confirm this is an issue with the Python library and not an underlying OpenAI API

• This is an issue with the Python library

Describe the bug

When using the Responses API, file_search annotations are being returned as ResponseAudioDeltaEvent instead of the expected annotation type. This appears to be a bug in how file search events are handled in the response payload.

Expected Behavior

file_search annotations should be returned with their correct event type (e.g., FileSearchEvent), not as ResponseAudioDeltaEvent.

Actual Behavior

All file_search annotations are appearing as ResponseAudioDeltaEvent in the response annotations.

To Reproduce

1. Call the Responses API with a request that triggers a file_search annotation.
2. Inspect the annotations in the response.
3. Notice that file_search results are incorrectly labeled as ResponseAudioDeltaEvent.

Code snippets

ResponseAudioDeltaEvent(delta=None, sequence_number=345, type='response.output_text.annotation.added', item_id='XX', output_index=1, content_index=0, annotation_index=3, annotation={'type': 'file_citation', 'file_id': 'file-XX', 'filename': 'XX.pdf', 'index': 1364})

OS

Windows

Python version

v3.12.0

Library version

v1.82.0

[dominpm]

Also happening on code_interpreter #2382

[jihun-im-open]

web_search_preview as well. and ResponseTextAnnotationDeltaEvent is removed from openai.types.responses

[AnneMayor]

I am trying to figure out the problem and fix it. I will let you know til this weekend(~6.8)

[tancredibosi]

I also confirm to have the same issue, obtaining the event.type 'response.output_text.annotation.added' instead of the expected 'response.output_text_annotation.added' that is documented

[dominpm]

still hapenning on 1.84.0

[rohanlad]

I am also getting this issue

[tancredibosi]

Hi, someone know if the issue is in working status?

[AnneMayor]

Sorry for the late response. I am handling it.

[dominpm]

Hi, has this been fixed in latest updates?

[RobertCraigie]

Sorry for the delay, I believe this should be fixed in the latest release. Please re-open if it is not fixed.

[hayescode]

@RobertCraigie I'm still getting the error on 1.93.3. I'm using AzureOpenAI.