Skip to main content
PATCH

Authorizations

Authorization
string
header
required

Runpod API key authentication. Generate an API key in the Runpod console and send it in the Authorization header as Bearer <api_key>. Keys are scoped to the permissions granted when created; requests may return 403 when a valid key lacks access to the requested resource or action.

Console sessions (Clerk JWTs) act for the signed-in user. To act for a team instead, also send X-Team-Id: <team_id>; it applies only when the user owns or belongs to that team, otherwise the request runs against the user's own account. API keys created inside a team already act for that team and do not need the header.

Path Parameters

id
string
required

User identifier

Body

application/json

Changes to a member. Send role, groups, or both; an omitted field is left as it is.

role
object

An organization role to assign, by ID.

groups
object[]

The member's groups after the change: the whole set, by ID. An empty list removes the member from every group.

Response

OK

A member of the caller's organization. id is the member's user ID.

id
string
required

User ID.

Example:

"user_id_abc_123"

email
string | null
required

The member's email address. Null for an account that has none.

Example:

"member@example.com"

role
object
required

An organization role, by ID and display name.

groups
object[]
required

The groups the member belongs to, by name.

Last modified on November 3, 2026