DOCUMENTATION / RULE REFERENCE
OpenAPI & JSON Schema Breaking Change: Endpoint removed from the contract
By Soumik Ghosh ยท Published
The previous method and path no longer appear in the compared specification. Find callers of that operation and verify the replacement and any rollout overlap.
- Rule ID
operation.endpoint_removed- Direction
- operation
- Classification
- Breaking
What does a minimal example look like?
These examples illustrate the rule with contract fragments or detector evidence. The rule ID applies to detector findings with the relevant direction and policy context.
Before
{
"paths": {
"/reports": {
"get": {
"responses": {
"200": {
"description": "OK"
}
}
}
}
}
}After
{
"paths": {}
}What should I check in my application?
Find the operation and affected field in the scanned commit. Confirm the server policy and application intent, inspect any missing coverage, then test the complete candidate. This rule alone does not prove repository impact, runtime failure, or a safe automatic fix.
Replay classifier inputs and policy choices or compare these schemas in both directions.
API compatibility guides and tools
- GraphQL breaking changes in schemas and operations
- gRPC and Protobuf breaking changes
- AsyncAPI breaking changes in events and messages
- SOAP and WSDL breaking changes
- Self-healing API integrations with checked migration drafts
- How to detect API contract drift before it breaks consumers
- oasdiff and API code impact analysis answer different questions.
- Detect breaking API changes in a GitHub workflow.
- Why a TypeScript build can pass after an API changes.
- OpenAI OpenAPI breaking changes: a captured response change.
- Sentry OpenAPI breaking changes: removed replay query values.
- Inspect classification rules interactively
- Check captured OpenAPI changes
- Compare JSON Schemas
- Plan your business evaluation
Use public API change evidence in your IDE with MCP
Browse public API change history, including OpenAI and Sentry.
Rule reference
schema.request_acceptance_narrowed: Request schema accepts fewer valuesoperation.endpoint_removed: Endpoint removed from the contractrequest.content_removed: Request media type removedlevel.error: Detector error falls back to breakingrequest.enum_removed: Request enum value removedrequest.now_required: Request property becomes requiredresponse.removed: Response property removedresponse.now_optional_or_nullable: Response property becomes optional or nullablerequest.removed_unknown_strictness: Request property removed, server strictness unknown