Skip to main content

Debug an API Response — Developer Workflow

2–4 minutes · For developers

Production API responses are the worst time to paste a JWT containing a real user identity into a random online decoder. Yet that's exactly the moment you need to inspect one — and most online tools are SaaS products that log everything you submit.

This workflow stitches together four browser-only tools that together cover 90% of API debugging: pretty-print the response, decode the auth token, decode any URL-encoded payloads, and (if you need to share results with a non-engineer) convert the JSON to a readable CSV.

The 4-step workflow

  1. JSON Formatter

    Paste the raw JSON response — get pretty-printed output with syntax highlighting and line-pinpoint errors.

  2. JWT Decoder

    Decode the Authorization Bearer token to inspect header, payload and expiry.

    Why: Safe for production tokens — the decoder runs in your browser and uses no signature-verification round-trip.

  3. URL Encoder/Decoder

    Decode any URL-encoded payload bodies or redirect URLs.

  4. JSON to CSV

    Convert the array part of the response to CSV for sharing with non-engineering stakeholders.

Every step runs in your browser — no upload, no signup.

When to use this workflow

  • Reproducing a customer-reported bug from a Sentry breadcrumb that includes a JWT
  • Validating a webhook payload from Stripe, Slack or GitHub before writing a handler
  • Inspecting an OAuth callback that shoves the user's identity into a URL fragment
  • Sharing a list of failed orders with the customer-success team as a spreadsheet

Frequently asked questions

Is it safe to decode production JWTs here?

Yes. The JWT decoder is a pure base64 + JSON.parse client-side. There is no signature verification round-trip to a server, no logging, no retention. Open DevTools → Network and watch — no request fires when you decode.

Can the JSON formatter handle very large responses?

Yes — multi-megabyte JSON works, limited only by your browser's memory. There's no upload step, so size limits don't apply.

Why convert API JSON to CSV at all?

Non-engineering stakeholders open spreadsheets, not curl output. Converting an array of records to CSV is the fastest way to share an API result with finance, support or product without writing a script.

Related workflows