Skip to main content
POST
Create service user

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

Request body for POST /service-users. Intentionally minimal: only the two fields that uniquely identify a new service user. Role grants are a separate resource managed through /role-assignments, which keeps each grant independently addressable and avoids silent drift when grants are added or revoked through another code path.

name
string
required

The display name of the service user.

Minimum string length: 1
Example:

"paladin-prod"

owner_id
string<uuid>
required

The ID of the owner (team of record) that owns the service user. Must reference an existing owner in the caller's organization.

Example:

"7c86c85d-0651-43e2-a748-d69d658418e8"

Response

The created service user.

User Object

Description

The User object is used to represent a user.

Usage Example

Fetch from the LIST Sessions endpoint.

user_id
string<uuid>
required

The ID of the user.

Example:

"h0z968412-2451-4bbd-42h4-057l715d917m"

email
string
required

The email of the user.

Example:

"john.doe@company.dev"

full_name
string
required

The full name of the user.

Example:

"John Doe"

first_name
string
required

The first name of the user.

Example:

"John"

last_name
string
required

The last name of the user.

Example:

"Doe"

position
string
required

The user's position.

Example:

"Senior Engineer"

manager_id
string<uuid> | null

The ID of the user's manager. Null if the user has no manager.

Example:

"29827fb8-f2dd-4e80-9576-28e31e9934ac"

hr_idp_status
enum<string>

User status pulled from an HR/IDP provider.

Available options:
ACTIVE,
SUSPENDED,
DEPROVISIONED,
DELETED,
NOT_FOUND
Example:

"ACTIVE"