API Response Comparison Across Environments
Compare API responses from DEV, QA and PROD. Ignore timestamps and request IDs, match arrays by ID and get a clear breaking-change report.
API Response Comparison tool
Comparison workspace
Runs entirely in your browser. Nothing you paste is uploaded or stored.
QA payload
PROD payload
About this tool
Call the same endpoint in two or three environments (QA and PROD, or DEV, QA and PROD) and paste the responses side by side. IntegrateKit lines them up against a baseline and reports what differs, ranked by impact: removed fields and type changes are breaking, value changes are warnings, new fields are informational.
Timestamps, request IDs and correlation IDs change on every call, so they're handled for you: their values are ignored, but the engine still checks that they're present and keep the same type. Every ignored difference stays visible in the results, so nothing is hidden silently.
How to use it
- Paste the response from each environment into its panel and name the panels (for example QA and PROD).
- Choose the baseline, usually PROD. Add a third environment with Pro.
- Adjust Options if needed: ignore extra fields or paths, change how arrays are matched, or treat null as missing.
- Press Compare. Use the summary per environment, the filters and F8 / Shift+F8 to work through the findings, then copy a summary or download the JSON report.
Limitations
- JSON responses only for now. XML comparison is available as a separate tool.
- You provide the responses: IntegrateKit does not send requests to your environments.
- Inputs up to 25 MB per environment.
Example
PROD: { "status": "SHIPPED", "total": 149.9, "customer": { "phone": "+1 555 0100" }, "meta": { "requestId": "4ad0…" } }
QA: { "status": "IN_TRANSIT", "total": 149.9, "customer": { }, "meta": { "requestId": "b27e…" } }QA vs PROD: 1 breaking, 1 warning, 1 ignored
Breaking Field removed $.customer.phone "+1 555 0100" → missing
Warning Value changed $.status "SHIPPED" → "IN_TRANSIT"
Ignored Value changed $.meta.requestId (request ID rule)Common use cases
Release verification
Before promoting a release, compare responses from QA and PROD for key endpoints and confirm that only expected fields changed.
Environment-specific bugs
When something only fails in one environment, line up DEV, QA and PROD to find the field, mapping or type that differs.
Integration and middleware changes
After changing a MuleSoft flow, Spring Boot mapper or gateway policy, compare the downstream response with the baseline to catch contract changes.