Docs/APIs/JWT Decoder

JWT Decoder

Decode JWT tokens free; verify signatures with a public key on paid plans

OperationalCredits 1 per callp50 207msData ConversionStar

Overview

On paid plans, pass a PEM public key, certificate or JWK as publicKey to verify RS, PS, ES and EdDSA signatures and check exp and nbf. HMAC (HS*) secrets and alg none are always refused, and keys are never fetched from URLs.

Live Test JWT Decoder API →

Endpoint

One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.

POSThttps://api.apiverve.com/v1/jwtdecoder
curl -X POST https://api.apiverve.com/v1/jwtdecoder \
  -H "x-api-key: your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
  "token": "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6InNhbXBsZS1rZXktMSJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaXNzIjoiaHR0cHM6Ly9hdXRoLmV4YW1wbGUuY29tIiwiYXVkIjoiYXBpLmV4YW1wbGUuY29tIiwiaWF0IjoxNzY3MjI1NjAwLCJleHAiOjIwODI3NTg0MDB9.hP0O9ELZGk-KN3upyYqdOnPY2Ig7FAzfUY_xytzOCBIhn0_TWdzl2dbLPlj0rkCDsRIQX0I5t9Xv551VI1W9dmvRGtVztyeD3IKHnIn24baOUtjU7Eb6FHL_iWMu5PqMeQJPFytuYbYhzjjCNfFPgAciGgn1Celr8H7_q51x5naMb-nbTvBc5SIX9MBnegGzabExBYQ-OsdKOoYmK0uymNIgC3834jlPuhuJHkPsxX7ncKoSQ4wheiLaZDwFANlT1NrD2XgKyyh-LIIg9CRwqB_WDktZ_R6UusNkLRhKJ20ff29ttkyRhJZzEqRRK60xYn7iPyg4YQni1J_w-oAa_w",
  "publicKey": "-----BEGIN PUBLIC KEY-----\nMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA9MiLgWPmLJoEIpAUHVvx\nGyo9vyW9/ryejQyuDZr1m5x0qj5y1otdjN3TwLH1PBQuinSDGiL7O56dfXwy/YIa\nKOhANcJWe78eSDs4oMh3wQnzRfseWZfFgbLHU/nWyXjPE5WRa9F+H5A96KvmatER\nG+kfWUINKR0RUTzox9xSy1KmiaQ5a2GoH3vINioVWBN1zX7Uq6mjCF5nYUMfWDyv\nuUofPWRU2saYdxD2TtVlIs8F62IQU0bnMifFXqmZ5CkmXwPAFJXAIi38Lh/vkOvw\n5B8oeiZd8ZEOLhSYlmhje1IGIwlB8B/ekKnZp4BdKsJYgGka7yn9NTuRsx8U7tfr\n7QIDAQAB\n-----END PUBLIC KEY-----"
}'

Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.

Authentication

Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Parameters

Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them.

ParameterTypeDescription
tokenRequiredstringJWT token to decode; a pasted Authorization header value (Bearer <token>) is accepted
publicKeyOptionalPremiumstringPublic key to verify the signature with: a PEM public key, a PEM X.509 certificate, or a JWK (as a JSON object or string). Asymmetric algorithms only; HMAC secrets are refused and keys are never fetched from URLs. Omit it to decode only.

Response

Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.

Sample response
{
  "status": "ok",
  "error": null,
  "data": {
    "header": {
      "alg": "RS256",
      "typ": "JWT",
      "kid": "sample-key-1"
    },
    "payload": {
      "sub": "1234567890",
      "name": "John Doe",
      "iss": "https://auth.example.com",
      "aud": "api.example.com",
      "iat": 1767225600,
      "exp": 2082758400
    },
    "signature": "hP0O9ELZGk-KN3upyYqdOnPY2Ig7FAzfUY_xytzOCBIhn0_TWdzl2dbLPlj0rkCDsRIQX0I5t9Xv551VI1W9dmvRGtVztyeD3IKHnIn24baOUtjU7Eb6FHL_iWMu5PqMeQJPFytuYbYhzjjCNfFPgAciGgn1Celr8H7_q51x5naMb-nbTvBc5SIX9MBnegGzabExBYQ-…",
    "isExpired": false,
    "expiresAt": "2036-01-01T00:00:00.000Z",
    "issuedAt": "2026-01-01T00:00:00.000Z",
    "tokenAge": "309 days",
    "algorithm": "RS256",
    "expiresIn": 288757380,
    "notYetValid": false,
    "securityAnalysis": {
      "isUnsecured": false,
      "hasExpiration": true,
      "isLongLived": true,
      "issues": [
        "Token lifetime exceeds 24 hours"
      ]
    },
    "warning": "Signature verified with the supplied public key.",
    "signatureVerification": {
      "verified": true,
      "algorithm": "RS256",
      "keyType": "RSA",
      "reason": null,
      "claimsValid": true,
      "claimsReason": null
    }
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

FieldTypeExampleDescription
headerobject{...}Decoded JWT header, typically containing the signing algorithm and token type
algstring"RS256"
typstring"JWT"
kidstring"sample-key-1"
payloadobject{...}Decoded JWT payload containing the token's claims (e.g. subject, issuer, expiration, and any custom claims)
substring"1234567890"
namestring"John Doe"
issstring"https://auth.example.com"
audstring"api.example.com"
iatnumber1767225600
expnumber2082758400
signaturestring"hP0O9ELZGk-KN3upyYqdOnPY2Ig7FAzfUY_xytzOCBIhn0_TWdzl2dbLPlj0rkCDsRIQX0I5t9Xv551VI1W9dmvRGtVztyeD3IKH…"Raw signature segment of the token (the third dot-separated part); see signatureVerification for the verification result when publicKey is sent
isExpiredbooleanfalseWhether the token's expiration (exp claim) is in the past
expiresAtstring"2036-01-01T00:00:00.000Z"ISO timestamp of when the token expires (from the exp claim); null if there is no exp claim
issuedAtstring"2026-01-01T00:00:00.000Z"ISO timestamp of when the token was issued (from iat claim)
tokenAgePremiumstring"309 days"Human-readable age of the token
algorithmstring"RS256"Signing algorithm declared in the token header (alg)
expiresInnumber288757380Seconds until the token expires; negative once expired, null if there is no exp claim
notYetValidbooleanfalseWhether the token's not-before (nbf) claim is still in the future
securityAnalysisPremiumobject{...}Structural security assessment of the token: unsigned (alg:none) detection, missing expiration, over-long lifetime, and a list of issues. Does not verify the signature.
isUnsecuredPremiumbooleanfalse
hasExpirationPremiumbooleantrue
isLongLivedPremiumbooleantrue
issuesPremiumarray[Token lifetime exceeds 24 hours]
warningstring"Signature verified with the supplied public key."Without publicKey, a reminder that the token was decoded but not verified; with publicKey, the verification outcome or the reason it failed
signatureVerificationPremiumobject{...}Signature and time-claim check against publicKey; present only when publicKey is sent
verifiedPremiumbooleantrueWhether the signature matches publicKey. Always false for alg none, HS* algorithms, or an algorithm that does not match the key type
algorithmPremiumstring"RS256"Algorithm from the token header that verification used
keyTypePremiumstring"RSA"Type of the supplied key, e.g. RSA, EC P-256 or Ed25519
reasonPremiumobjectnullWhy verification failed; null when verified
claimsValidPremiumbooleantrueWhether exp and nbf hold at the current time, reported separately from the signature
claimsReasonPremiumobjectnullWhich time claim failed and when; null when claimsValid is true

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.

StatusMeaningWhat to do
400Input was rejectedRead error; it names the parameter.
401Key missing or invalidCheck the header name and the key value.
403Key valid, but not permittedA key restriction or IP allow-list; see key scoping.
429Rate limited, or out of creditsRead error to tell them apart; see rate limits.

Start from a template

A working app built on this API, ready to deploy with your own key. Vercel asks for the key when you deploy; the code is on GitHub to change first.

Use cases

Token Debugging
Debug and inspect JWT tokens during development to view header and payload contents
Token Analysis
Analyze token structure and claims for free, and verify the signature against a public key on paid plans
Expiration Check
Check token expiration status and view expiration timestamps
Token Inspection
Inspect token contents for troubleshooting authentication issues

Other ways to use JWT Decoder

Set up JWT Decoder on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKit →Reference →

More in Data Conversion:

Was this page helpful?