---
title: "Change a member's role"
method: PATCH
path: "/api/v1/manage/members/{id}"
tags: ["Members"]
---

# Change a member's role

`PATCH /api/v1/manage/members/{id}`

## Request

- Base URL: `https://fillo.so`
- URL: `https://fillo.so/api/v1/manage/members/{id}`
- Auth: HTTP bearer

Change a member's workspace role. Their access changes immediately across every project, which makes this outward-facing (Tier B). An `fsk_` key has no session, so it acts as the human who minted it: their live role is the anti-escalation ceiling, a key whose creator was removed or demoted is refused with 403, and the workspace's last owner can never be demoted. Scope: members:manage.

## Path parameters

- `id` string, required

## Request body

- object
  - `role` 'owner' | 'admin' | 'member', required

## Response `200`

The member's new role.

- object
  - `id` string, required
  - `email` string, required
  - `role` 'owner' | 'admin' | 'member', required

## Other responses

- `400`: Invalid request (e.g. a body on a GET/DELETE, or a missing required query parameter).
- `401`: Missing, malformed, unknown, revoked, or expired key.
- `403`: The key is valid but lacks the required scope.
- `404`: No such resource in this project (returned instead of 403 for ids in other projects).
- `409`: The request was understood but refused in this state — an unmet precondition, or a confirm value that did not match. Nothing was changed.
- `413`: The request body exceeded the 16 KiB management cap.
- `429`: Per-key (120/min), per-workspace (240/min), or per-IP (300/min) rate limit exceeded. Retry after the Retry-After header.

---

[API](https://skmtc.dev/fillo/apis/fillo-management-api.md) · [All operations](https://skmtc.dev/fillo/apis/fillo-management-api/llms.txt) · [OpenAPI document](https://skmtc.dev/fillo/apis/fillo-management-api/revisions/867f943f04f5?raw)