Skip to Content
SeyloDocs
API referenceSetup

Create the owner account

POST
/api/v1/setup.createOwner

Uses up the setup token, creates the owner with email and password and signs them in (HttpOnly cookie). CONFLICT when an owner already exists.

Needs no sign-in. Not available to MCP clients or the assistant.

Request Body

application/json
  1. body
token*string

The t= value of the installer's setup link.

Length1 <= length <= 200
email*string
Formatemail
Lengthlength <= 254
name?string
Lengthlength <= 80
password*string

At least 10 characters.

Length10 <= length <= 1024

Response Body

Success.

application/json
  1. response
viewer*
Example Request
curl -X POST 'https://example.com/api/v1/setup.createOwner' \  -H 'Content-Type: application/json' \  -d '{  "token": "string",  "email": "[email protected]",  "password": "stringstri"}'
Example Response
{  "viewer": {    "id": "string",    "email": "[email protected]",    "name": "string",    "role": "owner"  }}

Upload a logo or favicon POST

Replaces one branding image. The file travels as a base64 data URL (PNG, SVG, WebP, JPEG or ICO, at most 512 KiB). SVGs are served with a sandboxing Content-Security-Policy. Needs `settings.manage`, which owners and admins hold. Not available to MCP clients or the assistant.

Finish first-run setup POST

Marks the setup wizard as done, so the web app stops offering it. Steps left out can be done later in settings. Needs `setup.finish`, which owners and admins hold. Not available to MCP clients or the assistant.