How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Authelia OIDC API

OpenID Connect 1.0 / OAuth 2.0 provider endpoints.

Authelia OIDC API is one of 4 APIs that Authelia publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include OIDC. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a GitHub repository.

This API exposes 12 operations across 8 paths, organized into 2 resource areas, and defines 24 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://{authelia_host}.

12 operations 8 paths 24 schemas 3 GET8 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://auth.example.com
Authentication
API Key, OpenID Connect
Contact
License
Resource Areas
2

Authentication & Security 2

Authelia OIDC API declares 2 security schemes for authenticating requests. An API key is passed in the cookie as authelia_session (authelia_auth). It supports OpenID Connect (openid) discovered at https://auth.example.com/.well-known/openid-configuration.

Paths & Operations 12

Across 8 paths, the API surfaces 12 operations — 3 GET, 8 POST, 1 PUT. They span 2 resource areas: OAuth 2.0, OpenID Connect 1.0. Each is listed below with its method, path, parameters, and response codes.

OAuth 2.0 10

OAuth 2.0 Endpoints

GET
/api/oidc/authorization
OpenID Connect 1.0 Authorization Endpoint
getOpenIDConnectAuthorization 21 params → 200303400500
POST
/api/oidc/authorization
OpenID Connect 1.0 Authorization Endpoint
postOpenIDConnectAuthorization body → 200303400500
POST
/api/oidc/device-authorization
RFC8628 OAuth 2.0 Device Authorization Grant Endpoint
postOAuth2DeviceAuthorization body → 200400500
PUT
/api/oidc/device-authorization
RFC8628 OAuth 2.0 Device Authorization Grant Endpoint
putOAuth2DeviceAuthorization body → 200400500
POST
/api/oidc/pushed-authorization-request
OAuth 2.0 Pushed Authorization Endpoint
postOAuth2PushedAuthorizationRequest body → 200400413429500
POST
/api/oidc/token
OpenID Connect 1.0 Token Endpoint
postOpenIDConnectToken body → 200401403500
POST
/api/oidc/revocation
OAuth 2.0 Token Revocation Endpoint
postOAuth2Revocation body → 200401403500
POST
/api/oidc/introspection
OAuth 2.0 Token Introspection Endpoint
postOAuth2Introspection body → 200401403500
GET
/api/oidc/consent
OpenID Connect 1.0 Consent Information
getOpenIDConnectConsent 2 params → 200403
POST
/api/oidc/consent
OpenID Connect 1.0 Consent Response
postOpenIDConnectConsent body → 200403
OpenID Connect 1.0 2

OpenID Connect 1.0 Endpoints

GET
/api/oidc/userinfo
OpenID Connect 1.0 UserInfo Endpoint
getOpenIDConnectUserInfo 1 param → 200401403500
POST
/api/oidc/userinfo
OpenID Connect 1.0 UserInfo Endpoint
postOpenIDConnectUserInfo 1 param body → 200401403500

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are openid.implementation.Claims.Object (30 properties), openid.spec.AuthorizeRequest (18 properties), openid.spec.IntrospectionResponse (12 properties), openid.request.consent.body (7 properties). Each schema is shown below with its type and property counts.

openid.spec.AccessResponse
object
7 properties 3 required
openid.response.consent
object
2 properties
openid.spec.ResponseType
string
The OAuth 2.0 / OpenID Connect 1.0 Response Type.
openid.spec.AccessRequest.ClientAuth.JWT
object
3 properties 2 required
openid.spec.AccessServerTokenAssertionRequest
object
2 properties 1 required
openid.spec.AccessRequest.RefreshTokenFlow
openid.request.consent.body
object
The consent decision submitted by the user during the consent workflow.
7 properties
openid.spec.AccessRequest.DeviceCodeFlow
openid.spec.IntrospectionResponse
object
12 properties 1 required
openid.spec.DeviceAuthorizeRequest.Parameters
object
5 properties 1 required
openid.spec.DeviceAuthorizeRequest
openid.spec.ResponseMode
string
Informs the Authorization Server of the mechanism to be used for returning parameters from the Authorization Endpoint. This use of this parameter is NOT RECOMM…
openid.implementation.Claims.Object
object
OpenID Connect 1.0 User Claims.
30 properties
openid.spec.AccessRequest.ClientAuth.None
object
Client authentication for public clients registered with the 'none' client authentication method.
1 property 1 required
openid.spec.ErrorResponseGeneric
object
An OpenID Connect 1.0 and OAuth 2.0 error response Note this is a generic error response and may describe a possible response for a given endpoint that is not…
6 properties 1 required
openid.spec.AccessRequest.ClientCredentialsFlow
openid.spec.AccessRequest.ClientAuth
The client authentication parameters included in the request body. Clients using the clientsecretbasic method authenticate via the Authorization header rather…
openid.spec.AuthorizeRequest
object
18 properties 4 required
openid.request.consent
object
2 properties
openid.spec.CodeChallengeMethod
string
The RFC7636 Code Challenge Verifier Method.
openid.spec.AccessRequest.ClientAuth.Secret
object
2 properties 2 required
openid.spec.DisplayType
string
ASCII string value that specifies how the Authorization Server displays the authentication and consent user interface pages to the End-User.
openid.spec.AccessRequest.AuthorizationCodeFlow
openid.spec.Prompt
string
Not Supported: Space delimited, case sensitive list of ASCII string values that specifies whether the Authorization Server prompts the End-User for reauthentic…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

authelia-oidc-api-openapi.yml Raw ↑

Other APIs Authelia publishes across the network.

Authelia OpenID Connect 1.0 Provider
Authelia API
Authelia Discovery API
Where this information came from

This is an independent, third-party profile of Authelia OIDC API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.