API RESPONSES · CONFIGURATION · LOG DEBUGGING

Inspect the data.
Find the problem.

Separate syntax, types and meaning before choosing a tool. Each core workflow includes a runnable sample, a reference result and explicit limits. Inputs are processed in your browser.

Start with your problem ↗
Reproducible samplesNo sign-upLocal processing
Valid JSON ≠ a valid contract
{"name":"Ada","age":"30"}

age is a string. If the API requires an integer, formatting will not repair that type mismatch.

Work through a debugging task

Explain a changed API response

Start here when a response parses but the consuming application behaves differently. Work on invented or sanitized records.

  1. Why a duplicate JSON key can change an order status

    Resolve conflicting keys with the producer.

  2. Keep a large order ID intact when processing JSON

    Preserve identifier digits before parsing.

  3. Find a string where your JSON Schema expects an integer

    Validate field types against the agreed schema.

  4. 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.

  1. Keep XML attributes and empty repeated elements in JSON

    XML input: inspect attributes, empty elements and mixed content.

  2. Check strings and booleans when converting JSON to YAML

    JSON to YAML: check strings, booleans and ordered arrays.

  3. 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.

  1. Prepare a log excerpt for a support ticket

    Mask recognized credentials, then add application-specific fields and review the entire log.

  2. 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

What counts as a completed check?

  1. Keep the original data and reproduce the issue with a small sample.
  2. Compare the actual result with the reference, its types and the business contract.
  3. Verify the fix in the consuming application before converting, submitting or sharing.

Read about maintenance and verification limits · Report an incorrect result or instruction

YOUR EVERYDAY ESSENTIALS

Find your next tool

Continue reading and checking

The directory retains other everyday utilities. Start with a guide when you need to understand encodings, random identifiers, digests or regular expressions; each has different limits.

Developer guides · Maintenance history