---
title: "Revoke an invitation"
description: "Revokes a pending invitation whose roles all belong to products the caller administers.\n\n- **Scope:** `account:members:write`\n- **Credentials:** an API key, a client-credentials token or a person's access token\n- **Effect:** deletes; idempotent, safe to retry\n- **Limits:** request body up to 32 KB, response up to 256 KB\n- **CLI:** `arbol account invitations delete` · **MCP tool:** `account_invitations_delete`"
---

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

Path: Account API › Invitations

`DELETE /v1/account/invitations/{invitationId}`

Revokes a pending invitation whose roles all belong to products the caller administers.

- **Scope:** `account:members:write`
- **Credentials:** an API key, a client-credentials token or a person's access token
- **Effect:** deletes; idempotent, safe to retry
- **Limits:** request body up to 32 KB, response up to 256 KB
- **CLI:** `arbol account invitations delete` · **MCP tool:** `account_invitations_delete`

## Authentication

Requires one of the following:

- `arbolHuman`, oauth2, scopes: `account:members:write`
- `arbolMachine`, oauth2, scopes: `account:members:write`
- `arbolApiKey`, http, header `Authorization`

## Path parameters

- `invitationId` (`account.invitations.delete.path.invitationId`; string, required) — The invitation's id, as invitations.list answers it.
  - minLength 1; maxLength 256

## Code samples

### cURL

```bash
curl "https://api.getarbol.com/v1/account/invitations/<invitationId>" \
  --request DELETE \
  --header "Authorization: Bearer $ARBOL_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{}'
```

### TypeScript

```typescript
import { createClient } from "@arbol-ai/sdk";

const arbol = createClient({
  baseUrl: "https://api.getarbol.com",
  token: process.env.ARBOL_API_KEY!,
});

const { data } = await arbol.account.invitations.delete({
  invitationId: "<invitationId>",
});
```

### Rust

```rust
use arbol_sdk::{types, Client, Credential};

let arbol = Client::new(Credential::ApiKey(std::env::var("ARBOL_API_KEY")?))?;

let data = arbol
    .account()
    .invitations()
    .delete(&types::AccountInvitationsDeleteInput {
        invitation_id: "<invitationId>".into(),
    })
    .await?;
```

### CLI

```bash
arbol account invitations delete '<invitationId>'
```

### MCP

```json
{
  "name": "account_invitations_delete",
  "arguments": {
    "invitationId": "<invitationId>"
  }
}
```

## Responses

### 200

Successful operation.

#### Example

```json
{
  "success": true,
  "data": {
    "id": "string",
    "deleted": true
  },
  "error": null,
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`account.invitations.delete.response.200.success`; boolean, required)
  - one of `true`
- `data` (`account.invitations.delete.response.200.data`; object, required)
  - `id` (`account.invitations.delete.response.200.data.id`; string, required) — The id of the deleted resource.
  - `deleted` (`account.invitations.delete.response.200.data.deleted`; boolean, required)
- `error` (`account.invitations.delete.response.200.error`; unknown, required)
- `metadata` (`account.invitations.delete.response.200.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`account.invitations.delete.response.200.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 400

`INVALID_INPUT`: The request does not match the published schema.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "INVALID_INPUT",
    "message": "string",
    "retryable": false,
    "data": {
      "issues": [
        {
          "path": "string",
          "message": "string"
        }
      ]
    }
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`account.invitations.delete.response.400.success`; boolean, required)
  - one of `false`
- `data` (`account.invitations.delete.response.400.data`; unknown, required)
- `error` (`account.invitations.delete.response.400.error`; object, required) — The request does not match the published schema.
  - `code` (`account.invitations.delete.response.400.error.code`; string, required) — The failure code, stable across releases.
    - one of `"INVALID_INPUT"`
  - `message` (`account.invitations.delete.response.400.error.message`; string, required) — What went wrong, for people; it never contains input values.
  - `retryable` (`account.invitations.delete.response.400.error.retryable`; boolean, required) — Whether repeating the same request may succeed.
    - one of `false`
  - `data` (`account.invitations.delete.response.400.error.data`; object, required)
    - `issues` (`account.invitations.delete.response.400.error.data.issues`; array<object>, optional)
      - `path` (`account.invitations.delete.response.400.error.data.issues.path`; string, required) — RFC 6901 JSON Pointer to the refused field; empty for the whole input.
        - maxLength 256
      - `message` (`account.invitations.delete.response.400.error.data.issues.message`; string, required)
        - maxLength 256
- `metadata` (`account.invitations.delete.response.400.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`account.invitations.delete.response.400.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 401

`UNAUTHORIZED`: A valid access token is required.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "UNAUTHORIZED",
    "message": "string",
    "retryable": false,
    "data": {}
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`account.invitations.delete.response.401.success`; boolean, required)
  - one of `false`
- `data` (`account.invitations.delete.response.401.data`; unknown, required)
- `error` (`account.invitations.delete.response.401.error`; object, required) — A valid access token is required.
  - `code` (`account.invitations.delete.response.401.error.code`; string, required) — The failure code, stable across releases.
    - one of `"UNAUTHORIZED"`
  - `message` (`account.invitations.delete.response.401.error.message`; string, required) — What went wrong, for people; it never contains input values.
  - `retryable` (`account.invitations.delete.response.401.error.retryable`; boolean, required) — Whether repeating the same request may succeed.
    - one of `false`
  - `data` (`account.invitations.delete.response.401.error.data`; object, required) — No fields.
- `metadata` (`account.invitations.delete.response.401.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`account.invitations.delete.response.401.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 403

- `FORBIDDEN`: The token does not authorize this operation.
- `MEMBER_PROTECTED`: This person holds access that only Arbol changes.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "FORBIDDEN",
    "message": "string",
    "retryable": false,
    "data": {}
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`account.invitations.delete.response.403.success`; boolean, required)
  - one of `false`
- `data` (`account.invitations.delete.response.403.data`; unknown, required)
- `error` (`account.invitations.delete.response.403.error`; one of, required)
  - one of: `ForbiddenFailure`, `AccountMemberProtectedFailure`
  - discriminator: `code`
- `metadata` (`account.invitations.delete.response.403.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`account.invitations.delete.response.403.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 404

`INVITATION_NOT_FOUND`: This invitation does not exist.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "INVITATION_NOT_FOUND",
    "message": "string",
    "retryable": false,
    "data": {}
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`account.invitations.delete.response.404.success`; boolean, required)
  - one of `false`
- `data` (`account.invitations.delete.response.404.data`; unknown, required)
- `error` (`account.invitations.delete.response.404.error`; object, required) — This invitation does not exist.
  - `code` (`account.invitations.delete.response.404.error.code`; string, required) — The failure code, stable across releases.
    - one of `"INVITATION_NOT_FOUND"`
  - `message` (`account.invitations.delete.response.404.error.message`; string, required) — What went wrong, for people; it never contains input values.
  - `retryable` (`account.invitations.delete.response.404.error.retryable`; boolean, required) — Whether repeating the same request may succeed.
    - one of `false`
  - `data` (`account.invitations.delete.response.404.error.data`; object, required) — No fields.
- `metadata` (`account.invitations.delete.response.404.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`account.invitations.delete.response.404.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 409

`IDENTITY_REJECTED`: The identity service refused the change.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "IDENTITY_REJECTED",
    "message": "string",
    "retryable": false,
    "data": {}
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`account.invitations.delete.response.409.success`; boolean, required)
  - one of `false`
- `data` (`account.invitations.delete.response.409.data`; unknown, required)
- `error` (`account.invitations.delete.response.409.error`; object, required) — The identity service refused the change.
  - `code` (`account.invitations.delete.response.409.error.code`; string, required) — The failure code, stable across releases.
    - one of `"IDENTITY_REJECTED"`
  - `message` (`account.invitations.delete.response.409.error.message`; string, required) — What went wrong, for people; it never contains input values.
  - `retryable` (`account.invitations.delete.response.409.error.retryable`; boolean, required) — Whether repeating the same request may succeed.
    - one of `false`
  - `data` (`account.invitations.delete.response.409.error.data`; object, required) — No fields.
- `metadata` (`account.invitations.delete.response.409.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`account.invitations.delete.response.409.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 429

`RATE_LIMITED`: The request rate limit was exceeded. Try again later.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "RATE_LIMITED",
    "message": "string",
    "retryable": true,
    "data": {}
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`account.invitations.delete.response.429.success`; boolean, required)
  - one of `false`
- `data` (`account.invitations.delete.response.429.data`; unknown, required)
- `error` (`account.invitations.delete.response.429.error`; object, required) — The request rate limit was exceeded. Try again later.
  - `code` (`account.invitations.delete.response.429.error.code`; string, required) — The failure code, stable across releases.
    - one of `"RATE_LIMITED"`
  - `message` (`account.invitations.delete.response.429.error.message`; string, required) — What went wrong, for people; it never contains input values.
  - `retryable` (`account.invitations.delete.response.429.error.retryable`; boolean, required) — Whether repeating the same request may succeed.
    - one of `true`
  - `data` (`account.invitations.delete.response.429.error.data`; object, required) — No fields.
- `metadata` (`account.invitations.delete.response.429.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`account.invitations.delete.response.429.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 500

`INTERNAL_ERROR`: The service could not complete the operation.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "INTERNAL_ERROR",
    "message": "string",
    "retryable": false,
    "data": {}
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`account.invitations.delete.response.500.success`; boolean, required)
  - one of `false`
- `data` (`account.invitations.delete.response.500.data`; unknown, required)
- `error` (`account.invitations.delete.response.500.error`; object, required) — The service could not complete the operation.
  - `code` (`account.invitations.delete.response.500.error.code`; string, required) — The failure code, stable across releases.
    - one of `"INTERNAL_ERROR"`
  - `message` (`account.invitations.delete.response.500.error.message`; string, required) — What went wrong, for people; it never contains input values.
  - `retryable` (`account.invitations.delete.response.500.error.retryable`; boolean, required) — Whether repeating the same request may succeed.
    - one of `false`
  - `data` (`account.invitations.delete.response.500.error.data`; object, required) — No fields.
- `metadata` (`account.invitations.delete.response.500.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`account.invitations.delete.response.500.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 502

`OUTCOME_UNKNOWN`: The operation may have been applied; check its result before repeating it.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "OUTCOME_UNKNOWN",
    "message": "string",
    "retryable": false,
    "data": {}
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`account.invitations.delete.response.502.success`; boolean, required)
  - one of `false`
- `data` (`account.invitations.delete.response.502.data`; unknown, required)
- `error` (`account.invitations.delete.response.502.error`; object, required) — The operation may have been applied; check its result before repeating it.
  - `code` (`account.invitations.delete.response.502.error.code`; string, required) — The failure code, stable across releases.
    - one of `"OUTCOME_UNKNOWN"`
  - `message` (`account.invitations.delete.response.502.error.message`; string, required) — What went wrong, for people; it never contains input values.
  - `retryable` (`account.invitations.delete.response.502.error.retryable`; boolean, required) — Whether repeating the same request may succeed.
    - one of `false`
  - `data` (`account.invitations.delete.response.502.error.data`; object, required) — No fields.
- `metadata` (`account.invitations.delete.response.502.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`account.invitations.delete.response.502.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 503

- `UPSTREAM_UNAVAILABLE`: The upstream service could not complete the request.
- `ACCOUNT_NOT_CONFIGURED`: Account administration is not configured yet.
- `IDENTITY_UNAVAILABLE`: The identity service did not answer.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "UPSTREAM_UNAVAILABLE",
    "message": "string",
    "retryable": true,
    "data": {}
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`account.invitations.delete.response.503.success`; boolean, required)
  - one of `false`
- `data` (`account.invitations.delete.response.503.data`; unknown, required)
- `error` (`account.invitations.delete.response.503.error`; one of, required)
  - one of: `UpstreamUnavailableFailure`, `AccountAccountNotConfiguredFailure`, `AccountIdentityUnavailableFailure`
  - discriminator: `code`
- `metadata` (`account.invitations.delete.response.503.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`account.invitations.delete.response.503.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 504

`UPSTREAM_TIMEOUT`: The upstream service did not respond before its deadline.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "UPSTREAM_TIMEOUT",
    "message": "string",
    "retryable": true,
    "data": {}
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`account.invitations.delete.response.504.success`; boolean, required)
  - one of `false`
- `data` (`account.invitations.delete.response.504.data`; unknown, required)
- `error` (`account.invitations.delete.response.504.error`; object, required) — The upstream service did not respond before its deadline.
  - `code` (`account.invitations.delete.response.504.error.code`; string, required) — The failure code, stable across releases.
    - one of `"UPSTREAM_TIMEOUT"`
  - `message` (`account.invitations.delete.response.504.error.message`; string, required) — What went wrong, for people; it never contains input values.
  - `retryable` (`account.invitations.delete.response.504.error.retryable`; boolean, required) — Whether repeating the same request may succeed.
    - one of `true`
  - `data` (`account.invitations.delete.response.504.error.data`; object, required) — No fields.
- `metadata` (`account.invitations.delete.response.504.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`account.invitations.delete.response.504.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.


Source: https://docs.getarbol.com/api/account/invitations/delete/index.md