Set a member's roles
Replaces the roles of an existing member of your account. Roles on the user’s other accounts are unchanged.
Only an account_admin of {account_id} may call it. It updates existing members only;
a new member joins by accepting an email invitation, and a non-member returns 403.
Grantable roles are developer, account_admin, and billing_admin.
An omitted body, an empty body, or {} sets the roles to ["developer"]. Repeating the
request is safe. Prefer PUT /users/{user_id}/accounts/{account_id}/roles, which requires
an explicit role list.
Authorizations
A Reactor API key (rk_...), sent as Authorization: Bearer rk_.... Keep it on a server.
Path Parameters
The user's ID. Use the id from GET /me for your own user.
The account's ID. Use the account_id from GET /me.
Body
The member's new role set in this account. Defaults to ["developer"].
A role you can grant within an account.
developer, account_admin, billing_admin Response
The membership was updated. account_id and roles describe the selected membership.
An account the user belongs to. When the response is scoped to one membership, this is
that membership's account. New clients should read accounts instead.
The user's roles in account_id. New clients should read accounts instead.
When the user was created, as an RFC 3339 timestamp.
"2026-01-15T10:30:00Z"
The memberships you may see: all of them for your own user, or only the shared one when an account admin reads another member. Omitted on membership-update responses.