JWT Decoder
Paste a JSON Web Token and read its header, claims and expiry in plain words.
- Next.js
- TypeScript
Read claims, headers, and expiration details from any JWT.
JWT Decoder decodes JWT tokens to reveal header and payload information, and on paid plans verifies the signature against a public key you supply. It handles JSON web token decode from any language over REST, so you can inspect claims and expiry without adding a JWT library.
No key required to try it. Get a key to use it in your app.
{
"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-OsdKOoYmK0uymNIgC3834jlPuhuJHkPsxX7ncKoSQ4wheiLaZDwFANlT1NrD2XgKyyh-LIIg9CRwqB_WDktZ_R6UusNkLRhKJ20ff29ttkyRhJZzEqRRK60xYn7iPyg4YQni1J_w-oAa_w",
"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
}
}
}
Paste a JSON Web Token and read its header, claims and expiry in plain words.
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.
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
Same data, same APIVerve account, same credit balance — one key works on all of them.
Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
| Parameter | Type | Example | Description |
|---|---|---|---|
tokenRequired | string | eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6InNhbXBsZS1rZXktMSJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaXNzIjoiaHR0cHM6Ly9hdXRoLmV4YW1wbGUuY29tIiwiYXVkIjoiYXBpLmV4YW1wbGUuY29tIiwiaWF0IjoxNzY3MjI1NjAwLCJleHAiOjIwODI3NTg0MDB9.hP0O9ELZGk-KN3upyYqdOnPY2Ig7FAzfUY_xytzOCBIhn0_TWdzl2dbLPlj0rkCDsRIQX0I5t9Xv551VI1W9dmvRGtVztyeD3IKHnIn24baOUtjU7Eb6FHL_iWMu5PqMeQJPFytuYbYhzjjCNfFPgAciGgn1Celr8H7_q51x5naMb-nbTvBc5SIX9MBnegGzabExBYQ-OsdKOoYmK0uymNIgC3834jlPuhuJHkPsxX7ncKoSQ4wheiLaZDwFANlT1NrD2XgKyyh-LIIg9CRwqB_WDktZ_R6UusNkLRhKJ20ff29ttkyRhJZzEqRRK60xYn7iPyg4YQni1J_w-oAa_w | JWT token to decode; a pasted Authorization header value (Bearer <token>) is accepted |
| Parameter | Type | Example | Description |
|---|---|---|---|
publicKeyOptionalPremium | string | -----BEGIN PUBLIC KEY-----
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA9MiLgWPmLJoEIpAUHVvx
Gyo9vyW9/ryejQyuDZr1m5x0qj5y1otdjN3TwLH1PBQuinSDGiL7O56dfXwy/YIa
KOhANcJWe78eSDs4oMh3wQnzRfseWZfFgbLHU/nWyXjPE5WRa9F+H5A96KvmatER
G+kfWUINKR0RUTzox9xSy1KmiaQ5a2GoH3vINioVWBN1zX7Uq6mjCF5nYUMfWDyv
uUofPWRU2saYdxD2TtVlIs8F62IQU0bnMifFXqmZ5CkmXwPAFJXAIi38Lh/vkOvw
5B8oeiZd8ZEOLhSYlmhje1IGIwlB8B/ekKnZp4BdKsJYgGka7yn9NTuRsx8U7tfr
7QIDAQAB
-----END PUBLIC KEY----- | Public 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. |
curl -X POST "https://api.apiverve.com/v1/jwtdecoder" \
-H "x-api-key: YOUR_API_KEY" \
-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-----"}'Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
content-typeRequired | POST body | application/json |
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.
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"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-OsdKOoYmK0uymNIgC3834jlPuhuJHkPsxX7ncKoSQ4wheiLaZDwFANlT1NrD2XgKyyh-LIIg9CRwqB_WDktZ_R6UusNkLRhKJ20ff29ttkyRhJZzEqRRK60xYn7iPyg4YQni1J_w-oAa_w",
"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
}
}
}
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.
| Field | Type | Example | Description |
|---|---|---|---|
header | object | {...} | Decoded JWT header, typically containing the signing algorithm and token type |
alg | string | "RS256" | |
typ | string | "JWT" | |
kid | string | "sample-key-1" | |
payload | object | {...} | Decoded JWT payload containing the token's claims (e.g. subject, issuer, expiration, and any custom claims) |
sub | string | "1234567890" | |
name | string | "John Doe" | |
iss | string | "https://auth.example.com" | |
aud | string | "api.example.com" | |
iat | number | 1767225600 | |
exp | number | 2082758400 | |
signature | string | "hP0O9ELZGk-KN3upyYqdOnPY2Ig7FAzfUY_xytzOCBIhn0_TWdzl2dbLPlj0rkCDsRIQX0I5t9Xv551VI1W9dmvRGtVztyeD3IKHnIn24baOUtjU7Eb6FHL_iWMu5PqMeQJPFytuYbY… | Raw signature segment of the token (the third dot-separated part); see signatureVerification for the verification result when publicKey is sent |
isExpired | boolean | false | Whether the token's expiration (exp claim) is in the past |
expiresAt | string | "2036-01-01T00:00:00.000Z" | ISO timestamp of when the token expires (from the exp claim); null if there is no exp claim |
issuedAt | string | "2026-01-01T00:00:00.000Z" | ISO timestamp of when the token was issued (from iat claim) |
tokenAgePremium | string | "309 days" | Human-readable age of the token |
algorithm | string | "RS256" | Signing algorithm declared in the token header (alg) |
expiresIn | number | 288757380 | Seconds until the token expires; negative once expired, null if there is no exp claim |
notYetValid | boolean | false | Whether the token's not-before (nbf) claim is still in the future |
securityAnalysisPremium | object | {...} | 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. |
isUnsecuredPremium | boolean | false | |
hasExpirationPremium | boolean | true | |
isLongLivedPremium | boolean | true | |
issuesPremium | array | [Token lifetime exceeds 24 hours] | |
warning | string | "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 |
signatureVerificationPremium | object | {...} | Signature and time-claim check against publicKey; present only when publicKey is sent |
verifiedPremium | boolean | true | Whether the signature matches publicKey. Always false for alg none, HS* algorithms, or an algorithm that does not match the key type |
algorithmPremium | string | "RS256" | Algorithm from the token header that verification used |
keyTypePremium | string | "RSA" | Type of the supplied key, e.g. RSA, EC P-256 or Ed25519 |
reasonPremium | object | null | Why verification failed; null when verified |
claimsValidPremium | boolean | true | Whether exp and nbf hold at the current time, reported separately from the signature |
claimsReasonPremium | object | null | Which time claim failed and when; null when claimsValid is true |
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | JWT Decoder calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 200 | Free |
| Starter | $29.99 | 200,000 | 200,000 | $0.15 |
| Pro | $99.99 | 1,000,000 | 1,000,000 | $0.10 |
| Mega | $299.99 | 4,000,000 | 4,000,000 | $0.07 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
No SDK to install — this is a plain HTTPS call to /v1/jwtdecoder with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/jwtdecoder" \
-H "x-api-key: YOUR_API_KEY"Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Install the Node.js SDK, then call the JWT Decoder API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/jwtdecoderconst res = await fetch("https://api.apiverve.com/v1/jwtdecoder", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
No SDK to install — this is a plain HTTPS call to /v1/jwtdecoder with your key in the x-api-key header. Swap in a real key and it runs as-is.
import requests
res = requests.get(
"https://api.apiverve.com/v1/jwtdecoder",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Install the C# / .NET SDK, then call the JWT Decoder API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.JWTDecoderusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/jwtdecoder");
Console.WriteLine(json);Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
No SDK to install — this is a plain HTTPS call to /v1/jwtdecoder with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/jwtdecoder", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
No SDK to install — this is a plain HTTPS call to /v1/jwtdecoder with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/jwtdecoder");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
No SDK to install — this is a plain HTTPS call to /v1/jwtdecoder with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/jwtdecoder")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyOnly the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Drop an interactive JWT Decoder form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the JWT Decoder API.
API Authentication Best Practices in 2026Stop overthinking auth. API keys for servers, OAuth for users, JWTs for stateless. Here's what actually matters.Read
Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read
Generate PDFs from HTML with an APIConvert HTML to PDF programmatically. Tutorial covering invoices, reports, receipts, and certificates with code examples.Read