> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blobhub.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Remove Member

Remove a member from a target.

## **DELETE** `/members/:id`

### Path Parameters

| Parameter | Type   | Required | Description                         |
| :-------- | :----- | :------- | :---------------------------------- |
| `id`      | string | Yes      | The unique ID of the member record. |

### Response

Returns `{"status": "success"}` — no body beyond the status.

### Errors

| Status | Error       | Cause                                                                          |
| :----- | :---------- | :----------------------------------------------------------------------------- |
| 403    | `forbidden` | Missing `admin` access to the member's target, or no human behind the request. |

Revoking access is a perimeter change in exactly the way granting it is, and is refused on the same terms: a
[service account](/general/service-accounts)'s own key gets `403` here whatever role it carries. Use an
[acting token](/rest-api/auth/impersonate) when automation has to revoke on a human's behalf.

<Note>
  Retiring a service account removes every membership it holds, without any call to this endpoint — see
  [Delete User](/rest-api/users/delete-user).
</Note>

### Example

<CodeGroup>
  ```bash Request theme={null}
  curl -X DELETE https://api.blobhub.io/v1/members/mem_001 \
    -H "X-API-Key: $ORG_API_KEY"
  ```

  ```json Response theme={null}
  {
    "status": "success"
  }
  ```
</CodeGroup>