Update branding settings
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.
seylo_session<token>application/json- body
name?stringShown in the sidebar, the browser tab and emails. Defaults to the product name.
1 <= length <= 40loginMessage?stringlength <= 280hidePoweredBy?booleanSuccess.
application/json- response
name*stringShown in the sidebar, the browser tab and emails. Defaults to the product name.
1 <= length <= 40logoLight*|nulllogoDark*|nullfavicon*|nullloginMessage*stringlength <= 280hidePoweredBy*booleancurl -X POST 'https://example.com/api/v1/settings.updateBranding' \ -H 'Content-Type: application/json' \ -d '{}'{ "name": "string", "logoLight": "string", "logoDark": "string", "favicon": "string", "loginMessage": "string", "hidePoweredBy": true}Update appearance settings POST
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.
Update general settings POST
Changes the panel name, the panel domain (null removes it and goes back to IP:port) or the default node. Omitted fields keep their value. Setting a domain starts the DNS check and certificate; agents learn the new URL on their next connect. Needs `settings.manage`, which owners and admins hold. Available to MCP clients and the assistant.