OpenAI breaking change: POST /live/sessions/{session_id}/accept
/requestBody/content/application~1json/schema/properties/session/properties/triggers: undefined -> 2
Specification capture: . Published evidence last updated . This is captured contract evidence, not an observed outage or a result from scanning your code.
Which field and classification rule changed?
- Changed field
/requestBody/content/application~1json/schema/properties/session/properties/triggers- Rule ID
level.error- Classifier version
2026-10-15.2- Direction
- request
- Finding ID
chg_b9c81e06ff62d47fa98d37fbf522d42f6f6bf31a0bc9a43067af8fb8069d139f
What is the recorded before and after evidence?
Previous specification SHA-256: ca9d52673f7c6670ea4bd3eaa6d10db189dfb0b8462794dce4820c4013953bbf
Revised specification SHA-256: 6192daf366457d9f11b03b342dd9ac12209a4fc5296c048ab457d35a31c85521
Publisher version: 2.3.0 to 2.3.0.
No before/after schema excerpt is available in this bounded snapshot. Use the source revisions and public finding to inspect the contract; no replacement behavior is inferred here.
Inspect the complete release · Public source findings · Publisher specification source
How do I check whether this affects my code?
Confirm the affected operation and field in the repository commit you authorize. Inspect supported SDK and HTTP call-site matches, review dynamic or unmatched patterns, and choose the intended application behavior before approving a proposal. Schema validation, type checks, configured runtime checks, and your CI provide different evidence.
Check an authorized repository · Review coverage · Inspect classification rules