OAuth Token Response Inspector
Parse OAuth token endpoint JSON, decode JWT access or ID tokens, and review expires_in and refresh token fields locally.
Inspect OAuth token endpoint JSON responses
After a successful authorize redirect, your app exchanges the authorization code (and PKCE verifier) at the
token endpoint. The JSON body typically includes access_token,
token_type, expires_in, optional refresh_token, and scope.
OpenID Connect adds an id_token JWT. Paste the raw JSON here to list fields, estimate expiry, and
decode JWT segments without verifying signatures.
Error responses
Failed token requests return OAuth error JSON such as invalid_grant or
invalid_client. The inspector surfaces error and error_description at the
top so you can distinguish configuration issues from expired codes.
For full signature checks use JWT Verify RSA ES or JWT Claims Validator.
Frequently Asked Questions
Are tokens uploaded?
No. Parsing runs entirely in your browser. Treat pasted tokens as secrets and clear the field after debugging.
Why is signature verification omitted?
Token debugging often starts with structure and claim mistakes. Signature verification requires issuer keys and is handled by dedicated JWT tools once payloads look correct.
Related Tools
Recent Visits
Finance Calc Kit
Focused calculators on Finance Calc Kit for loans, compounding investments, contractor tax estimates, and reti...
Explore Finance Calc Kit