API Tools for Tokens, Schemas and Webhooks

Debug the pieces that sit between services: auth tokens, webhook signatures, API specs and the JSON that flows through them.

Debugging tokens, payloads and API specs

Authentication problems usually start with a token. The JWT decoder shows the header and claims of a token in readable form, including issued-at and expiry times. Decoding is not verifying, though: anyone holding a JWT can read it, and only a signature check proves it came from the right issuer. Use JWT Verify with the secret or public key for that, and the JWT Security Inspector to flag weak algorithms or missing claims.

Webhooks fail in a different way. When a provider reports a signature mismatch, the webhook HMAC signer recomputes the signature for GitHub, Stripe or Slack style payloads so you can compare. The usual culprit is hashing a re-serialized body instead of the exact raw bytes received; a single changed space breaks the match. Our guide to verifying webhook signatures covers the details.

For contracts and code, OpenAPI Studio helps you explore a spec, OpenAPI to Postman builds a collection from it, and GraphQL Studio assists with queries. When you have a sample response and need types, JSON to TypeScript and the Go, Java, C# and Python converters generate starting models. Review optional fields afterwards, because a single sample cannot show which keys are sometimes absent.

Decoding, signing and code generation run locally in your browser. The API tester is the deliberate exception: it sends the request you build straight from your browser to the endpoint you enter, so that API must allow cross-origin requests. Formatting the JSON itself is easier in the code tools.

All API Toolkit (24)

Common questions

Is it safe to paste a production JWT into a decoder?

A JWT is encoded, not encrypted, so its claims are readable by anyone who holds it. Decoding here happens in your browser, but treat a live token like a password: prefer expired or test tokens, and revoke any token you think has been exposed.

Why does the API tester fail when curl works?

Browsers enforce CORS, so a request made from a web page only succeeds if the API returns headers that allow your origin. Command line tools such as curl are not bound by that rule. Run the request from a terminal or your own server instead.

What is the difference between HS256 and RS256?

HS256 signs tokens with one shared secret, so every service that can verify tokens can also create them. RS256 signs with a private key and verifies with a public key, which lets many services check tokens without being able to issue them.