WebSearchActionSearch.query is marked required but deprecated and no longer sent by the API

[nezhyborets]

The WebSearchActionSearch schema has query listed in its required array, but the field description marks it as [DEPRECATED] and the API has stopped including it in responses:

WebSearchActionSearch:
  properties:
    query:
      type: string
      description: "[DEPRECATED] The search query."
    queries:
      type: array
      ...
  required:
    - type
    - query   # ← still here

This causes strict decoders (e.g. generated Swift clients via swift-openapi-generator) to fail with a keyNotFound error when a web search call event arrives, because query is absent from the JSON payload while the generated struct treats it as a non-optional field.

Expected: query should be removed from required since it is deprecated and no longer present in API responses. queries appears to be its replacement.

Observed error (Swift):

DecodingError.keyNotFound: Key 'query' not found in keyed decoding container.
Path: item.action.

[jbeckwith-oai]

Thank you for the precise report and for including the Swift decoding failure—it made the contract problem and its impact on generated clients very clear.

I verified this against the current specification on main (db3e531):

• WebSearchActionSearch.query is still present and marked deprecated: true, preserving compatibility with older payloads.
• query has been removed from the schema’s required array.
• The only required property is now type.
• queries remains available as the replacement array.
• I also checked the generated beta variant, BetaWebSearchActionSearch; it has the same corrected required set and does not require query.

As a result, generated strict decoders should now treat the deprecated singular query field as optional and accept the API payload described here without a keyNotFound failure.

This is exactly the change requested, so I’m closing the issue as resolved. Thanks again for identifying the mismatch and providing a concrete downstream decoding symptom.