# Authlete Documentation

> ## Agent Instructions
> ### Authlete versions
> Authlete 3.0 is the current version. Unless the user says they use another version, answer for Authlete 3.0 using the 3.x documentation.
> Documentation for Authlete 2.x (pages under `/v2/` and `/ja/v2/`) is for the legacy version. Refer to it only when the user is on Authlete 2.x.
>
> ### Authlete architecture
> Authlete is a backend engine for OAuth 2.0 and OpenID Connect processing. End users and client applications do not call it directly; the service provider's authorization server and API server call Authlete's APIs. Authlete handles protocol processing and token, client, and service management, while the service provider owns the OAuth/OIDC endpoints and user authentication.
> See [Architecture](https://developers.authlete.com/get-started/introduction-to-authlete/architecture.md).
>
> ### Concepts
> If the user is new to Authlete, read these pages first:
> - [Request and Response](https://developers.authlete.com/get-started/concepts/request-and-response.md): Core API requests pass the client's request parameters as-is, and responses return `resultCode`, `action`, and `responseContent`.
> - [Action Handling](https://developers.authlete.com/get-started/concepts/action-handling.md): Branch on `action`, never on `resultCode`, and map each action to the HTTP response your server returns.
> - [Two-Step API Calls](https://developers.authlete.com/get-started/concepts/two-step-api-calls.md): Actions such as `INTERACTION` are completed with a second call (`/auth/authorization/issue` or `/auth/authorization/fail`) linked by a `ticket`.
> - [Management API Overview](https://developers.authlete.com/get-started/concepts/overview.md): The Management API configures services, manages clients, and operates issued tokens, separately from the protocol flows handled by the Core API.
> - [API Authentication](https://developers.authlete.com/get-started/concepts/authentication.md): Authlete APIs use bearer tokens: a Service Access Token (one service) or an Organization Token (the whole organization).

- [3.x (295 pages)](https://developers.authlete.com/_llms/en/3-x.txt): Documentation for 3.x.
- [2.x (110 pages)](https://developers.authlete.com/_llms/en/2-x.txt): Documentation for 2.x.

## OpenAPI Specs

- [authlete-api-explorer-with-code-samples](https://spec.speakeasy.com/authlete/sdk-workspace/authlete-api-explorer-with-code-samples)

> The links below point to documentation indexes. Follow each `/_llms/` index recursively until you reach documentation pages.

## Indexes

- [English / 3.x (295 pages)](https://developers.authlete.com/_llms/en/3-x.txt): Documentation for English / 3.x.
- [English / 3.x / API Reference (87 pages)](https://developers.authlete.com/_llms/en/3-x/api-reference.txt): Documentation for English / 3.x / API Reference.
- [English / 2.x (110 pages)](https://developers.authlete.com/_llms/en/2-x.txt): Documentation for English / 2.x.
- [Japanese (398 pages)](https://developers.authlete.com/_llms/ja.txt): Documentation for Japanese.
- [Japanese / 3.x (298 pages)](https://developers.authlete.com/_llms/ja/3-x.txt): Documentation for Japanese / 3.x.
- [Japanese / 3.x / API リファレンス (87 pages)](https://developers.authlete.com/_llms/ja/3-x/api.txt): Documentation for Japanese / 3.x / API リファレンス.
- [Japanese / 2.x (150 pages)](https://developers.authlete.com/_llms/ja/2-x.txt): Documentation for Japanese / 2.x.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.