> ## Documentation Index
> Fetch the complete documentation index at: https://developers.authlete.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## 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).

# Authlete Console Release Notes - October 2026

##### Version Number : 1.0.29

# Overview

This minor update introduces changes for the Authlete Management Console.
This new version is available from October 29th (Thu).

# Management Console

## Full payload service flag

Added new `returnFullPayload` service flag which defaults to true and can be set to false by the user to receive a simplified payload from the applicable endpoints.

## Notification banner

Implemented a banner to notify users of ongoing maintenances and incidents within the console UI.

## Dashboard overhaul

Implemented new management console dashboard.

## Other UI improvements

* Updated the font to be consistent on all console pages
* Improved client secret set and rotate UX
* Added session length expiry modal to console UI
* Fixed an issue where searching for `AND`, `OR` or `NOT` would break client search
* Fixed an issue where some loading elements on the console UI would be treated as disabled, causing the wrong state to render
* Fixed an issue where user with restricted access would be able to see the Create Organization button on the invitations page
* Minor localization fixes


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