OpenAPI breaking change checker

Compare OpenAPI or Swagger specs in the browser to flag parameters that became required, new required request-body fields, removed required response fields, and additive operations before release review.

InputEnter a value to inspect

Base Spec

Target Spec

新增接口

只比较你粘贴的 OpenAPI / Swagger 文本。公开结果链接只应使用合成或脱敏规范，避免客户字段、内部域名、token、cookie 和私有路径进入 URL。

Waiting

The result will appear here as structured cards.

Example results you can open

Short, high-intent examples that are easy to open, share, and understand for search engines and AI systems.

Breaking review

Review an OpenAPI required-field removal

Check removed required response fields, a query parameter becoming required, and additive operations before release.

Open example

Request change

Check a Swagger request-body required-field addition

Use a synthetic Swagger spec pair to inspect request-body required-field additions and one added health endpoint.

Open example

FAQ

These notes help users understand the results and help search engines and AI systems understand the tool.

What does OpenAPI breaking change checker do?

It helps you inspect or process this value and get a readable result quickly.

Is my input saved?

Local tools run in the browser when possible. Server-side checks only use the input needed to complete the lookup.

What counts as a breaking change in this checker?

It currently flags parameters that became required, new required request-body fields, and removed required response fields. Added operations are reported separately as additive changes.

Does this tool request a live API or Swagger URL?

No. It only parses the OpenAPI or Swagger text pasted into the browser, which makes it appropriate for synthetic or redacted release-review samples.