@supabase/server - v0.2.0
    Preparing search index...

    Interface JWTClaims

    Standard JWT claims as defined by RFC 7519, extended with Supabase-specific fields.

    This is the raw JWT payload — use UserClaims for a normalized, camelCase view.

    https://datatracker.ietf.org/doc/html/rfc7519#section-4.1

    interface JWTClaims {
        sub: string;
        iss?: string;
        aud?: string | string[];
        exp?: number;
        iat?: number;
        role?: string;
        email?: string;
        app_metadata?: Record<string, unknown>;
        user_metadata?: Record<string, unknown>;
        [key: string]: unknown;
    }

    Indexable

    • [key: string]: unknown

      Additional custom claims.

    Index

    Properties

    sub iss? aud? exp? iat? role? email? app_metadata? user_metadata?

    Properties

    sub: string

    Subject — the user's unique ID.

    iss?: string

    Issuer — typically your Supabase project URL.

    aud?: string | string[]

    Audience — who the token is intended for.

    exp?: number

    Expiration time (seconds since epoch).

    iat?: number

    Issued at (seconds since epoch).

    role?: string

    Supabase role (e.g. "authenticated", "anon").

    email?: string

    User's email address from Supabase Auth.

    app_metadata?: Record<string, unknown>

    Application-level metadata set via Supabase Auth admin APIs.

    user_metadata?: Record<string, unknown>

    User-editable metadata set via Supabase Auth.

    Settings

    Member Visibility

    On This Page

    Properties