Skip to content
Sudomimus

Check whether the session behind an access token is still valid.

POST
/introspect
 
curl --request POST \
  --url https://connect-api.sudomimus.com/introspect \
  --header 'Content-Type: application/json' \
  --data '{ "accessToken": "example" }'

Returns the revocation status of the refresh token (session) that the supplied access token descends from. Intended for strict applications that want near-real-time revocation: validate the access token offline as usual, then call this endpoint — caching the result for at least recommendedRecheckSeconds — to decide whether to keep trusting it.

The access token is self-authenticating: its signature is verified against the issuing application’s public key, so no client-auth JWT is required. The access token’s own expiry is NOT enforced here; the answer describes the underlying session, not the access token’s freshness.

Request Body required

Section titled “Request Body required ”
Media type application/json
object
accessToken
required

A Sudomimus-issued access token (JWT). Its signature is verified; its own expiry is not enforced.

string
Example generated
{
  "accessToken": "example"
}

Responses

Section titled “ Responses ”

200

Section titled “200 ”

Status of the session behind the access token.

Media type application/json
object
status
required

Revocation state of the session behind the access token. not_found covers an unknown session or one belonging to a different application.

string
Allowed values: active revoked expired not_found
recommendedRecheckSeconds
required

Suggested minimum number of seconds to cache this result before re-checking.

integer
Example 
{
  "status": "active"
}

401

Section titled “401 ”

Access token missing, malformed, or with an invalid signature.

Media type application/json

Error response body. The Connect service emits { "reason": "<SymbolDescription>" } for known failure modes. When the reason symbol’s description begins with PRIVATE, the body is empty (zero bytes) and only the HTTP status carries signal — both reason and the body itself are absent in that case.

object
reason

Stable machine-readable reason code.

string
Example generated
{
  "reason": "example"
}

default

Section titled “default ”

Error response.

Media type application/json

Error response body. The Connect service emits { "reason": "<SymbolDescription>" } for known failure modes. When the reason symbol’s description begins with PRIVATE, the body is empty (zero bytes) and only the HTTP status carries signal — both reason and the body itself are absent in that case.

object
reason

Stable machine-readable reason code.

string
Example generated
{
  "reason": "example"
}