Skip to content
EdgeKit

Change a member’s role

POST
/v1/org/update-member-role
curl --request POST \
  --url https://your-tenant-host/v1/org/update-member-role \
  --header 'Content-Type: application/json' \
  --header 'x-edgekit-site-id: site_example' \
  --cookie ek.session_token=<ek.session_token> \
  --data '{ "memberId": "01926f3a-8b4f-7c55-b066-6f7a8b9c0d1e", "role": "admin", "organizationId": "01926f3a-8b4e-7b33-a944-5e6f7a8b9c0d" }'

admin or member. owner is not assignable here: ownership transfer has its own rules, and offering it through a promotion route would let an admin hand the organization away. Safe to retry.

Authorizations

Section titled “Authorizations”

Parameters

Section titled “Parameters”

Header Parameters

Section titled “Header Parameters”
x-edgekit-site-id
required

The site this request is for, within this tenant. Every official EdgeKit SDK sets it from the client you configured; set it yourself only when calling this API directly.

string
>= 1 characters <= 128 characters

Example 

site_example

The site this request is for, within this tenant. Every official EdgeKit SDK sets it from the client you configured; set it yourself only when calling this API directly.

Request Bodyrequired

Section titled “Request Bodyrequired”
Media typeapplication/json
object
memberId
required
string format: uuid
>= 1 characters <= 128 characters

Example 

01926f3a-8b4f-7c55-b066-6f7a8b9c0d1e
role
required
string
Allowed values: admin member

Example 

member
organizationId
string format: uuid
>= 1 characters <= 128 characters

Example 

01926f3a-8b4e-7b33-a944-5e6f7a8b9c0d

Responses

Section titled “Responses”

200

Section titled “200”

The updated membership.

Media typeapplication/json
object
id
required
string format: uuid
organizationId
required
string format: uuid
userId
required
string format: uuid
role
required

Open: accept a member not listed. Known: owner, admin, member.

string | null
createdAt
required
string | null format: date-time
user
required
object
id
required
string format: uuid
email
required
string
name
required
string | null

Example 

{
  "id": "01926f3a-8b4f-7c55-b066-6f7a8b9c0d1e",
  "organizationId": "01926f3a-8b4e-7b33-a944-5e6f7a8b9c0d",
  "userId": "01926f3a-8b4c-7d2e-9f10-2a3b4c5d6e7f",
  "role": "owner",
  "createdAt": "2026-07-31T09:00:00.000Z",
  "user": {
    "id": "01926f3a-8b4c-7d2e-9f10-2a3b4c5d6e7f",
    "email": "ada@example.com",
    "name": "Ada Lovelace"
  }
}

400

Section titled “400”

Invalid request.

Media typeapplication/json
object
error
required
object
code
required
string
message
required
string
details

Example 

{
  "error": {
    "code": "unauthorized",
    "message": "Invalid or missing API key."
  }
}

401

Section titled “401”

Missing or invalid credential.

Media typeapplication/json
object
error
required
object
code
required
string
message
required
string
details

Example 

{
  "error": {
    "code": "unauthorized",
    "message": "Invalid or missing API key."
  }
}

403

Section titled “403”

Not allowed.

Media typeapplication/json
object
error
required
object
code
required
string
message
required
string
details

Example 

{
  "error": {
    "code": "unauthorized",
    "message": "Invalid or missing API key."
  }
}

404

Section titled “404”

Resource not found.

Media typeapplication/json
object
error
required
object
code
required
string
message
required
string
details

Example 

{
  "error": {
    "code": "unauthorized",
    "message": "Invalid or missing API key."
  }
}

422

Section titled “422”

Request validation failed.

Media typeapplication/json
object
error
required
object
code
required
string
message
required
string
details

Example 

{
  "error": {
    "code": "unauthorized",
    "message": "Invalid or missing API key."
  }
}

500

Section titled “500”

Unexpected error.

Media typeapplication/json
object
error
required
object
code
required
string
message
required
string
details

Example 

{
  "error": {
    "code": "unauthorized",
    "message": "Invalid or missing API key."
  }
}