Skip to main content
Utilnivo

Developer workflow

Debug a failing API

When an endpoint returns unexpected status codes or payloads, you need a repeatable loop: send the request, pretty-print the body, inspect auth tokens, and diff against a known-good response. This workflow chains Utilnivo API and JSON tools in that order.

Reproduce the request, format the JSON response, inspect JWTs, and compare payloads.

  • 5 steps
  • About 10 minutes
  • Data stays on this device
  • Updated 2026-07-24
Copy & customize

Workflow

Steps to complete

Work through each step in order. Progress is saved in this browser. Utilnivo does not save uploaded files permanently between tools.

Progress: 0 of 5 steps complete (0%)

  1. Send the request

    API Tester

    Reproduce method, URL, headers, and body against the failing endpoint.

    • On your device
    • No signup
    Open API Tester

  2. Format the response

    JSON Formatter

    Pretty-print JSON bodies so nested fields are easy to scan.

    • On your device
    • No signup
    Open JSON Formatter

  3. Inspect auth tokens

    JWT Decoder

    Decode bearer JWTs to check exp, iat, roles, and audience claims.

    • On your device
    • No signup
    Open JWT Decoder

  4. Diff against expected

    JSON Compare

    Compare the live response with a known-good fixture or prior capture.

    • On your device
    • No signup
    Open JSON Compare

  5. Export as cURL

    cURL Builder

    Build a cURL command teammates can paste into terminals or docs.

    • On your device
    • No signup
    Open cURL Builder

Track progress

Your progress

0 of 5 complete (0%). Your progress is saved in this browser.

Printable step list with checkboxes—generated on your device.

Results

Overall output

What you entered and what each step produced appear here. Values used in the next step are passed when supported. Data stays in this browser only.

Run each step and submit the calculator form. Key results will appear here as a connected summary.

Progress: 0 of 5 steps marked complete (0%).

When to use this workflow

  • An integration fails intermittently and you need a clean request/response trail.
  • Staging and production payloads look different and you want a structured diff.
  • You need a shareable cURL for a teammate or ticket.
  • Bearer tokens may be expired or missing claims.

Tips

Tips for better results

  • API Tester is subject to browser CORS—use it for public or CORS-enabled endpoints.
  • Never paste production secrets into shared screenshots or tickets.
  • Save a golden JSON fixture, then use JSON Compare after each fix attempt.

FAQ

Frequently asked questions

Why does a request fail in the browser but work in Postman?

Browsers enforce CORS. If the API does not allow your origin, use a server-side client or enable CORS for local debugging.

Is request data uploaded to Utilnivo?

Formatting, JWT decoding, and compare steps run on your device. Network requests go directly from your browser to the URL you enter.

Does JWT Decoder verify signatures?

It decodes claims for inspection. Cryptographic verification belongs in your backend with the correct keys.

Keep going

Related workflows

Debug a JWT or API token

Developer

Decode a bearer token, pretty-print JSON claims, and inspect Base64 segments.

3 steps

  1. Decode JWT
  2. Format JSON
  3. Decode Base64

Validate JSON before deploy

Developer

Validate syntax, pretty-print, generate a schema draft, and diff against the previous payload.

4 steps

  1. Validate syntax
  2. Format for review
  3. Draft a schema
  4. Diff versions

Provision staging credentials

Developer

Generate passwords, UUIDs, and hashes for dev, QA, and fixture data.

3 steps

  1. Generate password
  2. Generate UUIDs
  3. Hash sample input