# Change someone's role

Team

PATCH `/v1/members/{user_id}`

Makes someone an admin or a member (yourself included). The owner's role changes only by a handover. Free.

**Auth:** the dashboard session cookie.

## Example

cURL:

```shell
curl -X PATCH 'https://socialtap.dev/v1/members/<user_id>' \
  -H "x-api-key: $SOCIALTAP_API_KEY" \
  -H "content-type: application/json" \
  -d '{
  "role": "admin"
}'
```

## Authorizations

The dashboard's session cookie, not an API key.

## Path parameters

| Name | Type | Description | Example |
| --- | --- | --- | --- |
| `user_id` required | `string` | The person's ID (GET /v1/members). | — |

## Body

JSON. Fields marked nullable may be `null`; optional ones may be left out.

| Field | Type | Description |
| --- | --- | --- |
| `role` | `string` | Their new role. The owner's role never changes here: the owner hands the account over with POST /v1/account/transfer.<br>One of `admin`, `member` |

## Response

### 200

Change someone's role

| Field | Type | Description |
| --- | --- | --- |
| `data` | `object` |  |
| `data.email` | `string` | Their verified email address. |
| `data.is_you` | `boolean` | Whether this is the signed-in person. |
| `data.joined_at` | `string` (date-time) | When they joined the account, RFC 3339 UTC. |
| `data.object` | `string` | Always member.<br>One of `member` |
| `data.role` | `string` | owner: everything, including deleting the account and handing it to someone else (exactly one). admin: billing, keys, webhooks, settings and people, never the owner. member: reads the account and uses the playground with a key it is given; changes nothing.<br>One of `owner`, `admin`, `member` |
| `data.user_id` | `string` | The person's ID: change their role or remove them with it. |
| `meta` | `object` | The shared route meta (see the API reference introduction). |

### 400

400 Bad Request.

| Code | HTTP | Retry | Meaning | What to do |
| --- | --- | --- | --- | --- |
| `invalid_input` | 400 | No | A parameter is missing or malformed, or the link is not one this endpoint takes. | Fix the parameter named in param as the message says. For a link of the wrong kind, call an endpoint listed in details.endpoints, when there is one. |

### 401

401 Unauthorized.

| Code | HTTP | Retry | Meaning | What to do |
| --- | --- | --- | --- | --- |
| `unauthorized` | 401 | No | The x-api-key header is missing, or its key is unknown or revoked. On the dashboard's routes: the session cookie is missing or expired. | Send a valid API key in the x-api-key header. No key yet? A person gets one at details.signup_url; an AI agent follows details.agent_auth_url. |

### 403

403 Forbidden.

| Code | HTTP | Retry | Meaning | What to do |
| --- | --- | --- | --- | --- |
| `forbidden` | 403 | No | The API key is valid but may not make this request, and details.reason says why: the account is suspended, the key lacks the route's scope, waits for its owner to confirm it by email, has expired, or was used from an IP outside its allowlist, or a rotated key's previous secret was used for a call that needs the admin scope. A running job stops with it too when its account is suspended or the key that created it is revoked or expires. It is about the key, never the item: a private item is private_or_unavailable, also 403, so branch on the code. | Act on details.reason. suspended: contact [support](mailto:support@socialtap.dev). scope: use a key with details.required_scope. previous_secret: use the new secret. key_pending: have the owner open the emailed link. key_expired or key_revoked: create a new key. ip_not_allowed: call from an allowed IP. |

### 404

404 Not Found.

| Code | HTTP | Retry | Meaning | What to do |
| --- | --- | --- | --- | --- |
| `not_found` | 404 | No | The item does not exist or was deleted. On GET /v1/requests/{id}/response: the response was not kept (details.reason says why). | Check the link or ID. Do not retry. |

### 429

429 Too Many Requests.

| Code | HTTP | Retry | Meaning | What to do |
| --- | --- | --- | --- | --- |
| `rate_limited` | 429 | Yes, later | The account passed its runaway-protection ceiling: a high per-account limit that stops a broken client loop (plans have no rate limit). Requests without an API key (signup, the MCP server's tool listing and find_endpoint) are limited per IP address instead. It also stops an account whose failed requests in the last hour cost far more than its successful ones paid for: failures are free within a limit (the message says so), and successes raise it. | Wait the seconds in the retry-after header, then retry. If your steady traffic needs more, ask [support](mailto:support@socialtap.dev) to raise the ceiling; without an API key, send one. |

operationId `members.update`

---

[HTML version](https://socialtap.dev/docs/reference/team/members-update/) · [Docs index for AI agents](https://socialtap.dev/llms.txt) · [All docs in one file](https://socialtap.dev/llms-full.txt)