Skip to Content
SeyloDocs
API referencePeople

Disable a person

POST
/api/v1/users.disable

Blocks sign-in for an account and ends its sessions and API keys right away. Grants and history stay; users.enable undoes it.

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

Authorization

cookieseylo_session<token>

Request Body

application/json
  1. body
userId*string

Panel-issued id.

Match^[a-z0-9]{16}$

Response Body

Success.

application/json
  1. response
id*string

Panel-issued id.

Match^[a-z0-9]{16}$
email*string
Formatemail
Lengthlength <= 254
name*string
role*||

owner and admin may do everything; members only what their grants allow.

status*string|string
twoFactor*boolean
passkeyCount*integer
Range0 <= value
githubLogin*string|null
grantCount*integer
Range0 <= value
lastLoginAt*|null
createdAt*string
Formatdate-time
Example Request
curl -X POST 'https://example.com/api/v1/users.disable' \  -H 'Content-Type: application/json' \  -d '{  "userId": "string"}'
Example Response
{  "id": "string",  "email": "[email protected]",  "name": "string",  "role": "owner",  "status": "active",  "twoFactor": true,  "passkeyCount": 0,  "githubLogin": "string",  "grantCount": 0,  "lastLoginAt": "2019-08-24T14:15:22Z",  "createdAt": "2019-08-24T14:15:22Z"}

Set a service's alert rules POST

Makes a service follow the default alert rules (useDefaults true) or use its own (useDefaults false with rules). Rules for non-service events are refused. Needs `services.alerts` on the service (a grant on its project covers it). Available to MCP clients and the assistant.

Enable a person POST

Lets a disabled account sign in again. Its API keys stay revoked. Needs `users.manage`, which owners and admins hold. Not available to MCP clients or the assistant.