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.
Decide whether a conversion preserves meaning
Choose the branch matching your source format; these are alternative checks, not three mandatory conversions.
- Keep XML attributes and empty repeated elements in JSON
XML input: inspect attributes, empty elements and mixed content.
- Check strings and booleans when converting JSON to YAML
JSON to YAML: check strings, booleans and ordered arrays.
- Infer optional fields without erasing null from JSON samples
JSON to TypeScript: distinguish missing fields from explicit null.
When to stop
Save the result only after checking types with the parser or compiler used by the consuming application. Keep the original when the mapping discards document structure.
Prepare evidence for a reproducible bug report
Remove secrets without deleting the detail needed to reproduce an error. Query parameters can carry credentials too.
- Prepare a log excerpt for a support ticket
Mask recognized credentials, then add application-specific fields and review the entire log.
- Find changed and repeated URL query parameters
If the bug concerns a link, compare parameter values and order using invented URLs.
When to stop
Include tool URL, browser, a minimal synthetic input, steps, expected output and actual output. Verify the reduced example still fails before sending it; do not attach production credentials.
Open the report template