/api/oidc/introspectPublicToken introspection
The OAuth 2.0 token introspection endpoint (RFC 7662), advertised as introspection_endpoint. A confidential client POSTs an access or refresh token issued by this server and learns whether it is currently active plus its metadata (scope, client, subject, expiry). Tokens minted for other resource-API audiences, tokens issued to a different client, expired and revoked tokens all yield { "active": false }. Public (PKCE-only) clients cannot introspect: without client authentication the endpoint would be open to token scanning. Responses carry Cache-Control: no-store and Access-Control-Allow-Origin: *.
post_api_oidc_introspectOpenID Connect / OAuth 2.0Authentication & permissionsPublic
Anyone — no credentials required
- Accepted credentials
- None required
- Notes
- Client authentication is REQUIRED (RFC 7662 §2.1):
client_secret_basic(HTTP BasicAuthorizationheader) orclient_secret_post(client_secretform field) of an app with a registered client secret. The handler performs this itself;noneis not accepted.
Request body
Required
| Property | Type | Description |
|---|---|---|
| token* | string | REQUIRED. The access or refresh token to introspect. |
| token_type_hint | "access_token" | "refresh_token" | Accepted but unused: the token kind is read from the token itself. |
| client_id | string | The confidential client's id; may be omitted with minLength: 2maxLength: 64pattern: ^[a-z0-9_-]*$ |
| client_secret | string |
|
Responses
| Header | Type | Description |
|---|---|---|
| Cache-Control | string |
RFC 7662 §2.2 introspection response.
Example request
curl -X POST 'https://auth.schemavaults.com/api/oidc/introspect' \
-H 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'token=string' \
--data-urlencode 'token_type_hint=access_token' \
--data-urlencode 'client_id=string' \
--data-urlencode 'client_secret=string'