# Remove someone from the account

Team

DELETE `/v1/members/{user_id}`

Takes the person off the account at once. Keys stay: they are the account's. The answer lists the API keys and webhook endpoints the person created that still work, to review and revoke. The owner can't be removed. Free.

**Auth:** the dashboard session cookie.

## Example

cURL:

```shell
curl -X DELETE 'https://socialtap.dev/v1/members/<user_id>' \
  -H "x-api-key: $SOCIALTAP_API_KEY"
```

## 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). | — |

## Response

### 200

Remove someone from the account

| Field | Type | Description |
| --- | --- | --- |
| `data` | `object` |  |
| `data.api_keys` | `object[]` | The API keys they created or last rotated, directly or through a key of theirs, that aren't revoked. They keep working until revoked: DELETE /v1/api_keys/{id}. |
| `data.api_keys[].created_at` | `string` (date-time) | When the key was created, RFC 3339 UTC. |
| `data.api_keys[].created_by_key` | `string` or `null` | The API key (key_…) that last created this key, gave it the admin scope or rotated it: revoking that key also revokes this one if this one has admin. Null when none did, or a person has rotated it in the dashboard since. |
| `data.api_keys[].created_by_user` | `string` or `null` | The person (GET /v1/members user_id) who created this key in the dashboard, or whose key created it. They may have left the account since. Null when no person did (an operator, or a key from before this was recorded). |
| `data.api_keys[].dashboard` | `boolean` | true for the account's built-in dashboard key: the dashboard's playground runs as it (so its requests are logged, counted and billed like any key's). Nobody holds its secret, so it works only from the signed-in dashboard. Only its spend_limit can be changed (to cap what the playground spends live); renaming, rescoping, restricting, rotating or revoking it is forbidden (details.reason dashboard_key). It is made on first use and revoked with the account. |
| `data.api_keys[].expires_at` | `string` (date-time) or `null` | When the key stops working, RFC 3339 UTC; null when it never expires. |
| `data.api_keys[].id` | `string` | Key ID (key_…): manage the key with it. It is not the secret. |
| `data.api_keys[].ip_allowlist` | `string[]` | IP addresses or CIDR ranges (IPv4 or IPv6) the key works from; \[\] = any. |
| `data.api_keys[].last_used_at` | `string` (date-time) or `null` | About when the key was last used (updated at most hourly); null when never. |
| `data.api_keys[].name` | `string` | Your label for the key. |
| `data.api_keys[].object` | `string` | Always api_key.<br>One of `api_key` |
| `data.api_keys[].prefix` | `string` | The secret's first characters, to recognize it. |
| `data.api_keys[].previous_secret_expires_at` | `string` (date-time) or `null` | Until then the secret this key had before its last rotation works too (rotate_secret), RFC 3339 UTC; null when none does. |
| `data.api_keys[].revoked_at` | `string` (date-time) or `null` | When the key was revoked; null while it is not. |
| `data.api_keys[].scopes` | `string[]` | What the key may call: endpoints (data endpoints), jobs (create, read and cancel jobs; includes jobs:read), jobs:read (read jobs and their results), account:read (account, usage, ledger, keys), admin (account settings and key management; includes account:read).<br>One of `endpoints`, `jobs`, `jobs:read`, `account:read`, `admin` |
| `data.api_keys[].spend_limit` | `object` or `null` | The key's spend limit and what it used this interval; null when the key has none. |
| `data.api_keys[].status` | `string` | pending: created by an agent signup and waiting for the owner's email confirmation (it can only read GET /v1/account). expired: past expires_at.<br>One of `active`, `pending`, `expired`, `revoked` |
| `data.deleted` | `boolean` | Always true. |
| `data.id` | `string` |  |
| `data.object` | `string` | The deleted object's type (webhook_endpoint). |
| `data.unattributed_api_keys` | `integer` | How many other working keys on the account no person is recorded for (older than the record): they could be this person's too, so review them. |
| `data.webhook_endpoints` | `object[]` | The live webhook endpoints they created or last pointed somewhere. They keep receiving events until deleted: DELETE /v1/webhook_endpoints/{id}. |
| `data.webhook_endpoints[].created_at` | `string` (date-time) |  |
| `data.webhook_endpoints[].created_by_user` | `string` or `null` | The person (GET /v1/members user_id) who created this endpoint in the dashboard, or whose API key created it. They may have left the account since. Null when no person did, or it is from before this was recorded. |
| `data.webhook_endpoints[].description` | `string` or `null` |  |
| `data.webhook_endpoints[].disabled_reason` | `string` or `null` | Why it is disabled: gone (it answered 410), failing (deliveries failed for 5 days), user. Null while enabled.<br>One of `gone`, `failing`, `user` |
| `data.webhook_endpoints[].events` | `string[]` | Event types it receives: types, prefix wildcards (job.\*) or \* for all. |
| `data.webhook_endpoints[].id` | `string` | we_… |
| `data.webhook_endpoints[].object` | `string` | Always webhook_endpoint.<br>One of `webhook_endpoint` |
| `data.webhook_endpoints[].previous_secret_expires_at` | `string` (date-time) or `null` | Until then the previous secret signs too; null when none. |
| `data.webhook_endpoints[].secret?` | `string` or `null` | The signing secret (whsec_…): only in the create and rotate_secret answers. Store it. |
| `data.webhook_endpoints[].status` | `string` | One of `enabled`, `disabled` |
| `data.webhook_endpoints[].updated_at` | `string` (date-time) |  |
| `data.webhook_endpoints[].url` | `string` | https URL deliveries are POSTed to. A key an agent collected from an approval reads only its host: https://host/. |
| `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.remove`

---

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