Update a member's role and/or activation status.

PATCH

/v1/organizations/members/{user_id}

curl --request PATCH \
  --url https://api.adversarial.com/api/v1/organizations/members/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0 \
  --header 'Content-Type: application/json' \
  --data '{ "active": true, "roles": [ "example" ] }'

• Production
• Staging
• Local

Parameters

Path Parameters

user_id

required

string format: uuid

The UUID of the member to update

Request Body^required

Media typeapplication/json

object

active

Set to true to reactivate a deactivated user. Absent means “don’t change activation status”. false is rejected — use DELETE to deactivate.

boolean | null

roles

Names of the roles to assign (e.g. [“admin”], [“editor”, “viewer”]). Absent means “don’t change roles”.

Array<string> | null

Example^generated

{
  "active": true,
  "roles": [
    "example"
  ]
}

Responses

200

Member updated

Media typeapplication/json

object

email

required

string

first_name

required

string

icon

Relative path to the user’s avatar endpoint, e.g. "users/{id}/avatar?v={hash}". None when the user has no avatar.

string | null

id

required

string format: uuid

last_name

required

string

deactivated_date

string | null format: date-time

joined_date

required

string format: date-time

kind

required

Kind of principal an OrganizationMember represents. Always HUMAN on the /v1/users endpoint today; included on the wire so consumers have a single discriminator regardless of which endpoint surfaced the row.

Wire format is SCREAMING_SNAKE_CASE so the values read as constants (HUMAN, SERVICE_ACCOUNT).

string

Allowed values: HUMAN INTEGRATION SERVICE_ACCOUNT

last_login

string | null format: date-time

roles

required

Array<string>

Example

{
  "kind": "HUMAN"
}

400

Invalid request

403

Forbidden - insufficient permissions

404

User not found in organization