Service management · CONFIGURATION
Manage your service connections
Configure JMAP, Telegram, LLM, access allowlist and runtime parameters. Business configuration is stored in external Redis and hot-reloaded immediately after a successful save.
Create a short-lived admin session using the CONFIG_ENCRYPTION_KEY value.
Setup guide
Service startup configuration
Checking service startup configuration…
Startup secrets must be configured in the deployment environment. Secrets are never saved or echoed in the page.
Authorization required
Create admin session
Enter the value of the required startup key CONFIG_ENCRYPTION_KEY. The server issues a 15-minute admin session; the key and session exist only in the current page memory.
Full replacement
Business connections and auth
Business configuration is not read from the server.
To avoid secret echo, the API does not expose a business configuration GET. Every submission must re-fill the complete configuration, including all required secrets; optional LLM fields are sent as
null when left blank. The mailbox primary account is always used.
Outbound requests
Timeouts and retries
Runtime parameters are read by GET /api/config and updated by PUT /api/config; new values apply immediately to subsequent requests after saving.