JWT Claims

JWT claims are the key-value statements inside a JWT payload: registered claims with reserved meaning, plus public and private claims defined by the issuer.

Updated: 2026-08-11

Lookup

JWT Claims
Definition
iss (Issuer)Identifies who issued the token.
sub (Subject)Identifies the token's principal, e.g. a user or service id. Should be checked alongside iss, not treated as globally unique alone.
aud (Audience)Identifies the intended recipient(s). A verifier should reject tokens whose aud doesn't include itself.
exp (Expiration Time)A NumericDate (seconds since epoch) after which the token must be rejected.
nbf (Not Before)A NumericDate before which the token must be rejected.
iat (Issued At)A NumericDate recording when the token was issued.
jti (JWT ID)A unique identifier for the token, useful for detecting replay.

Examples

Payload with registered, public, and private claims

json
{
  "iss": "https://auth.example.com",
  "sub": "user_123",
  "aud": "https://api.example.com",
  "exp": 1735689600,
  "iat": 1735686000,
  "https://example.com/plan": "pro",
  "internalRole": "admin"
}

Common Mistakes

!
Treating sub as globally unique
sub is only unique within the issuer (iss) — always validate iss and sub together.
!
Skipping aud validation
Without checking aud, a token minted for one service can be replayed against a different service that trusts the same issuer.
!
Putting sensitive PII directly in claims
The payload is not encrypted (see the JWT reference), so claims are visible to anyone holding the token.

Related Concepts

JWT

Related Tools

Related Guides