OpenAI API
- OpenAPI contract
Vendor coverage
OpenAI API changes & breaking changes
OpenAI's API surface moves as fast as its models: new endpoints, new parameters, response schemas that grow and shift between releases. Detektu diffs the published OpenAPI specification so your integration keeps up.
Coverage
What Detektu monitors
Official products and contracts checked for changes.
Change model
How OpenAI ships changes
The release patterns that shape your integration risk.
OpenAI publishes an OpenAPI specification covering its API surface: chat completions, responses, embeddings, files, and more. It changes often, mostly additively, with occasional sharp edges. Parameters change shape, and response fields appear or move as capabilities roll out.
Detektu diffs every revision of the spec and classifies each change by severity, so a new optional parameter reads as signal while a changed response schema on an operation you call escalates with exact before/after evidence.
From change to finding
Findings you'd see
Illustrative examples. Every real finding carries exact before/after evidence, severity, and source provenance.
Response schema changed on chat completions
openapi:POST /v1/chat/completions ::response.200.choicesLegacy completions endpoint marked deprecated
openapi:POST /v1/completionsNew request parameter on the Responses API
openapi:POST /v1/responses ::includeMonitored for you
Do OpenAI's changes affect your integration?
Choose the operations and fields your services use. Detektu matches OpenAI findings to that declared usage so your team can review the relevant evidence. No agent or repository access required.