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

# Send invitation email

> Explicitly queue an existing invitation to its intended recipient using the one-time invitation token.

`send_invitation_email`

Explicitly queue an existing invitation to its intended recipient using the one-time invitation token. The encrypted outbox retries safely; replay never sends a second invitation.

<Note>Available in the deployed MCP and HTTP bundle. Confirm access and inputs with your connected catalog. Workspace scopes and enabled providers still apply.</Note>

| Access                                  | Behavior              |
| --------------------------------------- | --------------------- |
| `projects:write`, `notifications:write` | Writes or admits work |

This operation changes saved state. Review its inputs and retry behavior before calling.

## 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": "send_invitation_email",
      "arguments": {
        "invitationId": "invitation_example",
        "token": "lti_0000000000000000000000000000000000000000000000000000000000000000"
      }
    }
  }
  ```

  ```bash CLI theme={null}
  agentlinkops call send_invitation_email --args '{"invitationId":"invitation_example","token":"lti_0000000000000000000000000000000000000000000000000000000000000000"}'
  ```

  ```bash HTTP theme={null}
  curl "$AGENTLINKOPS_API_URL/v1/commands/send_invitation_email" \
    -H "Authorization: Bearer $AGENTLINKOPS_API_KEY" \
    -H 'Content-Type: application/json' \
    --data '{"invitationId":"invitation_example","token":"lti_0000000000000000000000000000000000000000000000000000000000000000"}'
  ```
</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": "pending",
  "replayed": false
}
```

## 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        |
| `token`        | string | Required | The token value; allowed values and bounds are specified in this schema. pattern: "^lti\_\[a-f0-9]\{64}\$" |

### Validation and omitted values

Supply the one-time token returned by invite\_member; the server stores only its hash. The email is queued in an encrypted outbox and sent by the notification schedule; replaying for the same invitation returns the existing outbox row and never sends twice.

Requires configured email delivery. Without it the command returns EMAIL\_NOT\_CONFIGURED and the token can still be shared directly.

## 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.                 |
| `replayed` | boolean | Required | True when the response reuses an earlier request with the same idempotency value. |

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

## Errors and retries

This command is not annotated idempotent. After a timeout, inspect existing state before repeating a write.

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

This operation has no separate resource alias. Use its generic command route in a matching environment.

## Continue

[list\_notification\_deliveries](/reference/commands/list_notification_deliveries) · [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).