# token-introspection

Source: https://startwithidentity.com/glossary/token-introspection/
Last updated: 2026-10-30
License: content by Start with Identity. Cite the source URL.

---

OAuth 2.0 Token Introspection ([RFC 7662](https://www.rfc-editor.org/rfc/rfc7662), Proposed Standard, October 2015) defines an endpoint where a resource server sends a token to the authorization server and gets back whether it is `active` plus its scopes, client, subject, audience, and expiry.

Introspection is the alternative to self-contained JWT access tokens (RFC 9068). A resource server that introspects learns about revocation immediately, because the authorization server answers from live state, while one that only validates a JWT signature keeps accepting a revoked token until it expires. The trade-off is a network call per request (usually cached for seconds) and an availability dependency on the authorization server. Many deployments use opaque tokens for external clients and introspect at the gateway, then pass a short-lived internal token downstream. The endpoint itself must require resource server authentication, or it becomes an oracle for anyone holding a stolen token.

See also: [access token](https://startwithidentity.com/glossary/access-token/), [bearer token](https://startwithidentity.com/glossary/bearer-token/), [JWT](https://startwithidentity.com/glossary/jwt/), [authorization server](https://startwithidentity.com/glossary/authorization-server/), [transaction tokens](https://startwithidentity.com/glossary/transaction-tokens/), [token theft](https://startwithidentity.com/glossary/token-theft/)