---
title: "Cancel an invitation"
method: DELETE
path: "/api/v1/manage/members/invites/{id}"
tags: ["Members"]
---

# Cancel an invitation

`DELETE /api/v1/manage/members/invites/{id}`

## Request

- Base URL: `https://fillo.so`
- URL: `https://fillo.so/api/v1/manage/members/invites/{id}`
- Auth: HTTP bearer

Cancel a pending invitation. The invite link stops working immediately, and inviting the address again starts fresh, which keeps this routine (Tier A). The key acts as the human who minted it, exactly as the other member routes do, and the id is scoped to the key's workspace first, so an invitation belonging to another workspace 404s indistinguishably from an unknown one. Scope: members:manage.

## Path parameters

- `id` string, required

## Response `200`

The invitation was cancelled.

- object
  - `id` string, required
  - `cancelled` true, required

## Other responses

- `400`: Invalid request (e.g. a body on a GET/DELETE, or a missing required query parameter).
- `401`: Missing, malformed, unknown, revoked, or expired key.
- `403`: The key is valid but lacks the required scope.
- `404`: No such resource in this project (returned instead of 403 for ids in other projects).
- `409`: The request was understood but refused in this state — an unmet precondition, or a confirm value that did not match. Nothing was changed.
- `429`: Per-key (120/min), per-workspace (240/min), or per-IP (300/min) rate limit exceeded. Retry after the Retry-After header.

---

[API](https://skmtc.dev/fillo/apis/fillo-management-api.md) · [All operations](https://skmtc.dev/fillo/apis/fillo-management-api/llms.txt) · [OpenAPI document](https://skmtc.dev/fillo/apis/fillo-management-api/revisions/867f943f04f5?raw)