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

# Revoke invitation

> Revoke an open invitation so its token can no longer be used.

`revoke_invitation`

Revoke an open invitation so its token can no longer be used.

<Note>Hosted MCP registration verified. These schemas describe the development contract; confirm supported inputs with tools/list. Generic CLI/HTTP calls require a matching development server. Configure LINKTRAIL\_API\_URL; production does not expose these command routes.</Note>

| Access           | Behavior                                                   |
| ---------------- | ---------------------------------------------------------- |
| `projects:write` | Writes or admits work; can change or remove existing state |

Reading saved data does not start a verification job. Mutations can change saved records or access; the effects below apply.

## Example request

Connect through [MCP](/guides/connect-mcp), [CLI](/guides/connect-cli), or [HTTP](/guides/connect-http). Replace example identifiers with records from your workspace.

<CodeGroup>
  ```json MCP theme={null}
  {
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "revoke_invitation",
      "arguments": {
        "invitationId": "invitation_example"
      }
    }
  }
  ```

  ```bash CLI theme={null}
  linktrail call revoke_invitation --args '{"invitationId":"invitation_example"}'
  ```

  ```bash HTTP theme={null}
  curl "$LINKTRAIL_API_URL/v1/commands/revoke_invitation" \
    -H "Authorization: Bearer $LINKTRAIL_API_KEY" \
    -H 'Content-Type: application/json' \
    --data '{"invitationId":"invitation_example"}'
  ```
</CodeGroup>

## Returned result

Illustrative data validated against the documented response schema. IDs and dates are examples, not a live account capture. MCP returns this data in `structuredContent` and in a text content block; generic HTTP and CLI return the JSON result directly.

```json theme={null}
{
  "id": "invitation_example",
  "state": "revoked"
}
```

## Input fields

Omit optional fields when you do not want to supply them. Null is accepted only where listed. Unknown input properties are rejected.

| Field          | Type   | Presence | Meaning and constraints                                                                             |
| -------------- | ------ | -------- | --------------------------------------------------------------------------------------------------- |
| `invitationId` | string | Required | Identifier of the invitation returned by its create or list operation. minLength: 1; maxLength: 200 |

### Validation and omitted values

Revoking a pending invitation prevents later acceptance; replay preserves the revoked state.

## Output fields

Fields inside optional or nullable parents apply only when that parent exists. [Common schema conventions](/reference/schemas) explain evidence states, empty lists and extensions.

| Field   | Type   | Presence | Meaning and constraints                                                                |
| ------- | ------ | -------- | -------------------------------------------------------------------------------------- |
| `id`    | string | Required | Resource identifier returned by the operation.                                         |
| `state` | string | Required | Saved lifecycle or evidence state, as enumerated for this record. must equal "revoked" |

[Download input schema](/schemas/revoke_invitation.input.json) · [Download output schema](/schemas/revoke_invitation.output.json)

## Errors and retries

The command is annotated idempotent. Reuse an accepted idempotency key when the input provides one; changing the payload under a reused key can conflict.

See [error recovery](/reference/errors) for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.

## HTTP resource routes

These existing resource routes share the operation’s domain behavior. Their parameter placement, status and response envelope can differ from generic invocation. See [HTTP route details](/reference/http/routes).

| Method and route                        | Success | Details                                       |
| --------------------------------------- | ------- | --------------------------------------------- |
| `DELETE /v1/invitations/{invitationId}` | 200     | Remaining arguments go in a JSON object body. |

## Continue

[list\_invitations](/reference/commands/list_invitations)

Follow the [related workflow](/guides/connect-http), inspect [capability status](/capability-status), or return to the [command index](/reference/index).