Version 5.x has been out of support since December 13, 2022, and this corresponding section of the documentation is no longer maintained. We strongly recommend upgrading to a supported version.

Introspection Endpoint

The introspection endpoint is an implementation of RFC 7662.

It can be used to validate reference tokens (or JWTs if the consumer does not have support for appropriate JWT or cryptographic libraries). The introspection endpoint requires authentication - since the client of an introspection endpoint is an API, you configure the secret on the ApiResource.

POST /connect/introspect
Authorization: Basic xxxyyy


A successful response will return a status code of 200 and either an active or inactive token::

    "active": true,
    "sub": "123"

Unknown or expired tokens will be marked as inactive::

    "active": false,

An invalid request will return a 400, an unauthorized request 401.

.NET client library

You can use the IdentityModel client library to programmatically interact with the protocol endpoint from .NET code.

using IdentityModel.Client;

var client = new HttpClient();

var response = await client.IntrospectTokenAsync(new TokenIntrospectionRequest
    Address = "",
    ClientId = "api1",
    ClientSecret = "secret",

    Token = accessToken