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

JSON
{
  "paths": {
    "/reports": {
      "get": {
        "responses": {
          "200": {
            "description": "OK"
          }
        }
      }
    }
  }
}

After

JSON
{
  "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

Use public API change evidence in your IDE with MCP

Browse public API change history, including OpenAI and Sentry.

Rule reference