---
title: "Remove a member"
method: DELETE
path: "/spaces/{space_id}/members/{user_id}"
---

# Remove a member

`DELETE /spaces/{space_id}/members/{user_id}`

Removes a member from a space. The space owner cannot be removed,
and callers cannot remove themselves.
Requires user authentication (JWT). API keys cannot manage members.

## Path parameters

- `space_id` string, required
- `user_id` integer, required

## Response `200`

Member removed

- Member — A member of a Ghost space.
  - `user_id` integer, required — User ID of the member.
  - `name` string, required — Display name of the member.
  - `email` string, required — Email address of the member.
  - `role` 'owner' | 'admin' | 'developer' | 'viewer', required — A member's role within a space. The `owner` role belongs to the user who created the space; every space has exactly one owner, so `owner` is never accepted as an input when granting a role. On the `Space` schema, this is the caller's own role in the space, omitted for API-key authentication (API keys are space-scoped and carry no member identity).

## Other responses

- `default` — Error response

---

[API](https://skmtc.net/timescale/apis/ghost-api.md) · [All operations](https://skmtc.net/timescale/apis/ghost-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/timescale/ghost-api/versions/808022f897be/schema)