Skip to Content
SeyloDocs
API referenceSettings

Update appearance settings

POST
/api/v1/settings.updateAppearance

Changes the theme preset, color mode, accent color or custom CSS. Omitted fields keep their value. Changing customCss needs the owner role (FORBIDDEN otherwise), because CSS can restyle every screen for everyone.

Needs settings.manage, which owners and admins hold. Not available to MCP clients or the assistant.

Authorization

cookieseylo_session<token>

Request Body

application/json
  1. body
preset?string|string|string|string
colorMode?string|string|string
accent?|null
customCss?string
Lengthlength <= 65536

Response Body

Success.

application/json
  1. response
preset*string|string|string|string
colorMode*string|string|string
accent*|null
customCss*string
Lengthlength <= 65536
Example Request
curl -X POST 'https://example.com/api/v1/settings.updateAppearance' \  -H 'Content-Type: application/json' \  -d '{}'
Example Response
{  "preset": "seylo",  "colorMode": "light",  "accent": "string",  "customCss": "string"}

Get the telemetry setting GET

Returns whether anonymous usage reports are on, the random install id they carry and when the last one was sent. Needs `settings.view`, which owners and admins hold. Not available to MCP clients or the assistant.

Update branding settings POST

Changes the panel name, sign-in page message or the powered-by line. Logos and the favicon change through settings.uploadBrandAsset. Needs `settings.manage`, which owners and admins hold. Not available to MCP clients or the assistant.