GLOSSARY

What is a Bearer token?

A Bearer token authenticates API requests via the Authorization header — whoever holds it can use it. Learn how it works and decode a JWT bearer free.

A Bearer token is a credential sent in the HTTP Authorization header — "Authorization: Bearer <token>" — that grants access to whoever presents it. It is the standard way APIs authenticate requests after login.

Whoever bears it, uses it

The word "bearer" is the key: the token itself is the credential, with no extra proof of identity. Anyone who obtains it can make requests as you until it expires or is revoked — so bearer tokens must be sent only over HTTPS and never logged, cached, or exposed in front-end code.

JWTs as bearer tokens

Bearer tokens are often JWTs, which carry their claims and expiry inside the token itself. You can decode a JWT bearer to inspect its payload and exp, but the signature still needs the key to verify.

Try it now — free, no signup

Use the JWT decoder in your browser. Then, when you need it at scale with an API key and higher limits, grab the full Eveses API.

FAQ

Is a Bearer token the same as a JWT?›
Not necessarily. A JWT is one common format for a bearer token, but a bearer token can also be an opaque random string.
How do I send a Bearer token?›
In the header: Authorization: Bearer <token>, over HTTPS only.

Related