Examine and introspect a token for the given Connected Apps client. All standard OIDC claims, as well as custom claims, will be returned.
The active status can be used to determine if the token is active.
This endpoint supports both access tokens and refresh tokens.
This endpoint is an RFC-7662 compliant token introspection endpoint.
- This endpoint supports passing the
client_id and client_secret within the request body as well as within a HTTP-Basic Auth header.
- This endpoint supports the
application/x-www-form-urlencoded content type.
We recommend using the Custom Domain whenever possible. For backwards compatibility reasons, this endpoint is also available at https://test.stytch.com/v1/public/${projectId}/oauth2/introspect.
Body
A hint for the type of the token. Possible values are access_token and refresh_token.
The ID of the Connected App client.
The secret of the Connected App client. Required for confidential clients
Response
Whether the token is active.
The scopes granted to the token.
The ID of the Connected App client.
The type of the token. Possible values are access_token and refresh_token.
The expiration time of the token, expressed as a Unix timestamp.
The time at which the token was issued, expressed as a Unix timestamp.
The subject of the token. This is a unique identifier for the user.
The issuer of the token. This is the domain of your project, e.g. https://$ by default, or stytch.com/PROJECT_ID if the token was retrieved using the stytch.com domain. See the Custom Domain guide for more information.
The audience (client_id) that the token is intended for. Additional custom audiences can be defined for the token by setting the access_token_custom_audience parameter on the client object.
Globally unique UUID that is returned with every API call. This value is important to log for debugging purposes; we
may ask for this value to help identify a specific API call when helping you debug an issue.
The HTTP status code of the response. Stytch follows standard HTTP response status code patterns, e.g. 2XX values
equate to success, 3XX values are redirects, 4XX are client errors, and 5XX are server errors.