What schema formats does this tool support?

It supports OpenAPI (Swagger) in YAML or JSON format, as well as GraphQL Schema Definition Language (SDL).

What is considered a breaking change?

Breaking changes include removing an existing endpoint, deleting a response field, changing a field's data type, or adding a new required input parameter that existing clients do not send.

Can the tool automatically detect my schema type?

Yes, you can set the Schema Type to 'Auto detect,' and the tool will infer whether you are comparing OpenAPI or GraphQL definitions based on the input syntax.

What does the impact analysis include?

The impact analysis evaluates the severity of changes, categorizing them as breaking, dangerous, or non-breaking, and assigns an overall release risk level to help teams prioritize fixes.

How do I view the comparison results?

The tool outputs a structured JSON report detailing the total changes, specific paths affected, and a summary of the impact for each modification.

Elysia Tools

Navigation

Development

OpenAPI Diff Breach Detector

Compare OpenAPI or GraphQL schemas, flag breaking changes, and generate an impact-oriented change report for API teams

Execution

Run this tool

Fill in the form, run the tool, and review the result in one place.

Prepared example runs

Click an example to fill the form automatically. File inputs still need an upload.

2 examples

Catch a removed response field before release

Compare two OpenAPI revisions and flag that a previously returned property disappeared from a 200 response payload

{"releaseRisk":"high","summary":{"breakingChanges":1},"changes":[{"path":"GET /users/{id} -> response 200.email","summary":"Response field removed"}]}

Review a GraphQL input contract change

Detect when a new required field is added to an input object so frontend and mobile teams can update mutations before rollout

{"schemaType":"graphql","summary":{"totalChanges":1,"breakingChanges":1,"dangerousChanges":0,"nonBreakingChanges":0},"impactedAreas":["field"],"releaseRisk":"high","changes":[{"severity":"breaking","area":"field","path":"input:CreatePostInput.category","summary":"Required input field added","impact":"Mutations or queries sending this input object must populate the new required field."}]}

Inputs

Set the required fields, then run the tool.

5 options

ContentPaste or type the main input values.3

Old SchematextareaRequiredNew SchematextareaRequiredInput FormattextOptional

SettingsAdjust formats, ranges, numbers, and modes.1

Schema TypeselectOptional

TogglesEnable or disable optional behavior.1

Include Impact AnalysischeckboxOptionalEnabled when checked

Result

Ready for a run

Run the tool to preview files, text, structured data, or streamed output here.

Samples

OpenAPI Diff Breach Detector

Run this tool

Prepared example runs

Inputs

Result

Examples that match this tool

Continue with connected tools and hubs

Prepared example runs

Inputs

Result

Learn when to use this tool, what it supports, and how real users apply it.

Key facts

Overview

When to use

How it works

Use cases

Examples

1. Catching a removed response field

2. Reviewing a GraphQL input contract change

FAQ

OpenAPI/Swagger Samples

OpenAPI/Swagger Samples

Android Image Processing Java Samples

Android Image Processing Kotlin Samples

API Contract Stress Tester

Cron Expression Explainer

CSS Masonry Layout Generator

cURL to Go (net/http) Converter

OpenAPI Documentation, Codegen, and Contract Review Tools

API Contract Testing, Mocking, and Schema Review Tools

API Versioning, Breaking Change, and Release Readiness Tools

JSON Schema, Mock Data, and API Fixture Generators