Platform

Request validation rules

Common request schemas are validated before side effects run. Field failures on /api/v1 use the shared 422 problem response; SCIM returns its SCIM error representation.

API docs

Browse docs

On this page

01 Account and agent registration

details

User fields

email is required, unique, at most 160 characters, and must contain @ with no spaces. name is optional on API registration: when omitted, register_via_api derives it from the email local part. When supplied, name is 2-120 characters. password is required, at least 12 characters, and at most 72 characters.

Operator UUID path parameters

Invalid UUID path parameters on operator routes fail as HTTP 400 via UUIDParams ("Invalid UUID path parameter"), not as a 422 extra.errors map.

Bootstrap fields

workspace_name and agent_name are required. Invalid bootstrap data returns 422 without creating a partial account or workspace.

02 Outbound destinations

details

Webhook subscriptions

name and an absolute HTTP(S) url are required; event_types must contain at least one entry. A signing secret is generated when omitted. Production delivery applies the outbound URL policy described in Production readiness.

03 Validation error example

example

{
  "type": "https://robotscenter.net/problems/unprocessable-entity",
  "title": "Unprocessable entity",
  "status": 422,
  "detail": "Validation failed",
  "request_id": "req-abc123",
  "extra": {
    "errors": {
      "password": ["should be at least 12 character(s)"]
    }
  }
}

Related docs