System settings endpoints allow you to configure instance-wide settings that affect all organizations and users.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/zitadel/zitadel/llms.txt
Use this file to discover all available pages before exploring further.
Language Settings
Get Supported Languages
Returns all languages supported by the ZITADEL system.HTTP Request
Permissions
Requiresauthenticated user.
Response
Array of supported language codes (e.g., [“en”, “de”, “fr”]).
Example Request
Get Allowed Languages
Returns languages that are allowed in the instance. If languages are restricted, only those are returned. Otherwise, all supported languages are returned.HTTP Request
Permissions
Requiresauthenticated user.
Get Default Language
Returns the default/fallback language used when a user’s preferred language is not available.HTTP Request
Permissions
Requiresiam.read permission.
Response
The default language code (e.g., “en”).
Set Default Language
Sets the default/fallback language for the instance.HTTP Request
Permissions
Requiresiam.write permission.
Path Parameters
The language code to set as default (e.g., “en”, “de”).
Example Request
OIDC Settings
Get OIDC Settings
Returns the OIDC settings that define token lifetimes for the instance.HTTP Request
Permissions
Requiresiam.read permission.
Response
OIDC configuration.
Lifetime of access tokens (e.g., “12h”).
Lifetime of ID tokens (e.g., “12h”).
Idle timeout for refresh tokens (e.g., “720h”).
Absolute expiration for refresh tokens (e.g., “2160h”).
Example Request
Add OIDC Settings
Creates new OIDC settings for the instance.HTTP Request
Permissions
Requiresiam.write permission.
Request Body
Lifetime for access tokens (duration format, e.g., “12h”).
Lifetime for ID tokens (duration format, e.g., “12h”).
Idle timeout for refresh tokens (duration format, e.g., “720h”).
Absolute expiration for refresh tokens (duration format, e.g., “2160h”).
Update OIDC Settings
Updates existing OIDC settings for the instance.HTTP Request
Permissions
Requiresiam.write permission.
Request Body
Same as Add OIDC Settings.Example Request
Security Settings
Get Security Policy
Returns the security settings of the ZITADEL instance.HTTP Request
Permissions
Requiresiam.policy.read permission.
Response
Example Request
Set Security Policy
Updates the security settings of the ZITADEL instance.HTTP Request
Permissions
Requiresiam.policy.write permission.
Request Body
Allow the login UI to be embedded in iframes.
List of origins allowed to embed the login UI (when iframe embedding is enabled).
Allow administrators to impersonate users.
Example Request
Secret Generators
List Secret Generators
Lists all configured secret generators that define how secrets (verification codes, OTPs, etc.) are generated.HTTP Request
Permissions
Requiresiam.read permission.
Get Secret Generator
Returns configuration for a specific secret generator type.HTTP Request
Permissions
Requiresiam.read permission.
Path Parameters
Type of generator (e.g., “PasswordResetCode”, “EmailVerificationCode”).
Update Secret Generator
Updates configuration for a secret generator.HTTP Request
Permissions
Requiresiam.write permission.
Path Parameters
Type of generator to update.
Request Body
Length of generated secrets.
How long the secret remains valid (duration format).
Include lowercase letters in the secret.
Include uppercase letters in the secret.
Include digits in the secret.
Include symbols in the secret.
Notes
- These settings apply to all organizations in the instance
- Token lifetimes affect all OIDC applications
- Security policies should be carefully configured to balance security and usability
- Secret generator settings affect password reset codes, email verification, OTP, etc.