---
title: "Cancel a sent invite"
method: DELETE
path: "/spaces/{space_id}/invites/{email}"
---

# Cancel a sent invite

`DELETE /spaces/{space_id}/invites/{email}`

Cancels the pending invite sent to the given email address for a space.
Requires user authentication (JWT). API keys cannot manage invites.

## Path parameters

- `space_id` string, required
- `email` string, required

## Response `200`

Invite cancelled

- Invite — An invite sent for a space.
  - `email` string, required — Email address the invite was sent to.
  - `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).
  - `status` 'pending' | 'declined', required — Status of a sent invite. `pending` means it's still awaiting a response; `declined` means the invitee declined it. A declined invite still occupies the email's slot for the space (one pending-or-declined invite per email), so it must be cancelled before that email can be re-invited.
  - `created_at` string, date-time, required — When the invite was created.

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