Definition
Full definition of jwt
JWTs encode a JSON payload (the "claims" — user_id, scopes, expiry) and sign it cryptographically so the receiver can verify authenticity without calling a database. They look like three base64 strings separated by dots. Many APIs (Auth0, Firebase, Supabase, Clerk) issue JWTs after login; Tiny Command uses them internally to authenticate API requests. You'll occasionally see JWTs in integration setup screens.
In practice
JWT examples
JWT structure
eyJhbGciOi... (header) . eyJzdWIiOi... (payload) . SflKxwRJ... (signature)
Used by
Apps that exemplify jwt
See jwt in action across real integrations.
FAQ
Common questions about jwt
Are JWTs encrypted?
No — they're signed, not encrypted. Anyone can read the payload (base64 decode it). Don't put secrets inside.
What does the 'exp' claim do?
It's a Unix timestamp for token expiration. Receivers should reject expired JWTs.
