Preparing your workspace
Connecting MemonaIQ servicesPreparing your workspace
Connecting MemonaIQ servicesCompare OpenAPI 3.0 and 3.1 specifications semantically. Detect breaking changes across endpoints, parameters, request bodies, responses, enums, nullability, and security requirements.
When reviewing API changes, traditional text diffs generate noise from reordered keys, whitespace changes, and formatting shifts while missing critical contract subtleties. The API Contract & Breaking Change Analyzer resolves internal references and analyzes API semantics—identifying exact breaking risks across wire protocols, client deserializers, and generated SDKs.
Schema compatibility depends fundamentally on data flow direction. Adding an optional property to a response schema is non-breaking under the tolerant reader pattern, whereas adding a required property to a request schema breaks existing API clients. The analyzer applies inverse requiredness rules between requests and responses.
Adding a new value to a request enum relaxes server input requirements, making it safe. However, adding a value to a response enum can crash generated client SDKs with closed enum definitions. The analyzer distinguishes these impacts and offers Balanced and Strict compatibility evaluation modes.
Security changes are evaluated at both the operation and component levels. Adding authentication to previously public endpoints, introducing new required OAuth scopes, or switching security scheme types are immediately flagged as breaking wire changes.
Unlike text-based line diffs, semantic comparison parses OpenAPI 3.0 and 3.1 specifications into an abstract syntax tree to evaluate directional compatibility rules—distinguishing breaking changes from safe additions and documentation updates.
No. OpenAPI YAML and JSON parsing, reference resolution, and breaking-change rule evaluations run entirely in your local browser. Specifications are never transmitted to MemonaIQ backend servers or stored.
When an API requires a new parameter or body field in requests, existing clients that send previous request payloads will receive HTTP 400 (Bad Request) validation errors.
Existing clients and SDKs rely on documented response fields. Removing a response property causes client deserialization errors, null pointers, or missing data in downstream systems.
The analyzer recognizes OAS 3.0 nullable: true properties alongside OAS 3.1 JSON Schema type arrays (e.g. type: ["string", "null"]), normalizing them into a canonical model before applying directional rules.
For security and privacy, external HTTP and filesystem references are not fetched over the network. All referenced schemas should be bundled or supplied within the local components section.
Discover other utilities in the MemonaIQ ecosystem designed to help you analyze and optimize your digital infrastructure.
Compare deeply nested JSON and XML payloads, identify structural and type changes, merge selected values, and export JSON Patch—all locally in your browser.
Enterprise platform for high-speed URL inspection, 30x redirect analysis, SSRF-safe trust scoring, security validation, technical SEO, site crawling, and real-time site uptime monitoring.
