staticdata.dev
Menu
Datasets About Contact

JWT Claims

A complete listing of all registered JWT claim names from the IANA JSON Web Token Claims Registry. Covers the seven core RFC 7519 registered claims (iss, sub, aud, exp, nbf, iat, jti), the full set of OpenID Connect identity claims, SIP-related claims, ACE profile claims, CDNI claims, Entity Attestation Token (EAT) claims, SD-JWT claims, 3GPP network function claims, and OpenID Federation claims.

v1.0.0 MIT 163 records Updated 2026-10-05 stable Source:  IANA JSON Web Token Claims Registry

Quick fetch

Stable URL. CORS-enabled. No auth.

bash 
curl https://staticdata.dev/v1/jwt-claims.json

Or use as a typed import: import { jwtClaims } from "https://staticdata.dev/v1/jwt-claims.ts"

Formats

  • JSON 31.2 KB

    /v1/jwt-claims.json

    Open

    min: 26.4 KB · /v1/jwt-claims.min.json

  • CSV 18.5 KB

    /v1/jwt-claims.csv

    Open
  • TypeScript 31.4 KB

    /v1/jwt-claims.ts

    export const jwtClaims

    type JwtClaim = (typeof jwtClaims)[number]

    Open

Schema

Each record in the dataset has the following shape.

Schema
Field Type Description Example
claim string The registered claim name (short identifier used in the token) sub
name string Human-readable name of the claim Subject
description string Plain-language description of what the claim represents Identifies the principal that is the subject of the JWT.
reference string Normative reference (RFC, spec, or standard) defining the claim RFC7519 Section 4.1.2

Preview

First 10 records.

Data preview
claimnamedescriptionreference
issIssuerIdentifies the principal that issued the JWT.RFC7519 Section 4.1.1
subSubjectIdentifies the principal that is the subject of the JWT.RFC7519 Section 4.1.2
audAudienceIdentifies the recipients that the JWT is intended for.RFC7519 Section 4.1.3
expExpiration TimeIdentifies the expiration time on or after which the JWT must not be accepted for processing.RFC7519 Section 4.1.4
nbfNot BeforeIdentifies the time before which the JWT must not be accepted for processing.RFC7519 Section 4.1.5
iatIssued AtIdentifies the time at which the JWT was issued.RFC7519 Section 4.1.6
jtiJWT IDProvides a unique identifier for the JWT.RFC7519 Section 4.1.7
nameFull nameEnd-user's full name in displayable form including all name parts.OpenID Connect Core 1.0 Section 5.1
given_nameGiven name(s) or first name(s)Given name(s) or first name(s) of the end-user.OpenID Connect Core 1.0 Section 5.1
family_nameSurname(s) or last name(s)Surname(s) or last name(s) of the end-user.OpenID Connect Core 1.0 Section 5.1

Showing 10 of 163. View full data:  JSON · CSV

Fetch examples

Drop-in snippets in five languages.

curl 
curl -sSL https://staticdata.dev/v1/jwt-claims.json | jq '.[0]'
JavaScript 
import type { JwtClaim } from "https://staticdata.dev/v1/jwt-claims.ts";

const res = await fetch("https://staticdata.dev/v1/jwt-claims.min.json");
if (!res.ok) throw new Error(`Fetch failed: ${res.status}`);
const jwtClaims: JwtClaim[] = await res.json();
console.log(jwtClaims[0]);
Python 
import urllib.request, json

with urllib.request.urlopen("https://staticdata.dev/v1/jwt-claims.min.json") as r:
    jwtClaims = json.load(r)

print(jwtClaims[0])
Go 
package main

import (
	"encoding/json"
	"fmt"
	"net/http"
)

func main() {
	resp, err := http.Get("https://staticdata.dev/v1/jwt-claims.min.json")
	if err != nil { panic(err) }
	defer resp.Body.Close()

	var data []map[string]any
	if err := json.NewDecoder(resp.Body).Decode(&data); err != nil {
		panic(err)
	}
	fmt.Println(data[0])
}
Rust 
use serde_json::Value;

fn main() -> Result<(), Box<dyn std::error::Error>> {
    let body = ureq::get("https://staticdata.dev/v1/jwt-claims.min.json").call()?.into_string()?;
    let data: Vec<Value> = serde_json::from_str(&body)?;
    println!("{:?}", data.first());
    Ok(())
}

Sources and methodology

This dataset contains all registered entries from the IANA JSON Web Token (JWT) Claims Registry, the authoritative source for standardized JWT claim names. The registry is maintained by IANA and covers claims defined across multiple RFCs and specifications including RFC 7519 (the core JWT specification), RFC 7800, RFC 8225, RFC 8693, RFC 9449, and many others, as well as claims from OpenID Connect Core, OpenID Federation, and 3GPP network function specifications.

Each record includes the registered claim name (the short string used as the JSON key in a token payload), a human-readable name, a plain-language description of the claim’s semantics, and the normative reference where the claim is formally defined. The dataset covers the full breadth of the registry: core authentication and identity claims, distributed/aggregated claim pointers, proof-of-possession confirmation claims, telephony and SIP claims, content delivery network claims, entity attestation claims, selective disclosure claims, and telecommunications network function claims.

Data was sourced directly from the IANA JSON Web Token Claims Registry at https://www.iana.org/assignments/jwt/jwt.xhtml. The IANA registry is updated periodically as new RFCs are published; this snapshot reflects the state of the registry as of October 2026 (163 claims). The name field is a short label; where IANA gives a longer description, the description field paraphrases it. Implementers building JWT parsers, validators, or documentation tools should cross-reference the live registry for any claims registered after that date.

Versioning

URLs under /v1/ are stable: field names and types will not change in a way that breaks consumers. Values can be corrected or records added when the upstream source changes; schema-incompatible updates ship under a new version path. See the jwt-claims changelog for this dataset's history.

More Code datasets