Explain a changed API response
Start here when a response parses but the consuming application behaves differently. Work on invented or sanitized records.
- Why a duplicate JSON key can change an order status
Resolve conflicting keys with the producer.
- Keep a large order ID intact when processing JSON
Preserve identifier digits before parsing.
- Find a string where your JSON Schema expects an integer
Validate field types against the agreed schema.
- Compare JSON values without confusing types
Compare the corrected response against the expected one.
When to stop
Keep the original response, the agreed contract and the final diff. Re-run the consuming application; schema success alone does not establish business correctness.