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

# Test notification email

> Explicitly queue a test to your saved verified recipient.

`test_notification_email`

Explicitly queue a test to your saved verified recipient. Requires enabled delivery and preferences; limited to one per hour.

<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                                                   |
| ------------------------------------ | ---------------------------------------------------------- |
| `events:read`, `notifications:write` | Writes or admits work; can change or remove existing state |

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": "test_notification_email",
      "arguments": {
        "expectedRevision": 1
      }
    }
  }
  ```

  ```bash CLI theme={null}
  agentlinkops call test_notification_email --args '{"expectedRevision":1}'
  ```

  ```bash HTTP theme={null}
  curl "$AGENTLINKOPS_API_URL/v1/commands/test_notification_email" \
    -H "Authorization: Bearer $AGENTLINKOPS_API_KEY" \
    -H 'Content-Type: application/json' \
    --data '{"expectedRevision":1}'
  ```
</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": "ntest_example",
  "state": "pending"
}
```

## 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                                                                                       |
| ------------------ | ------- | -------- | ------------------------------------------------------------------------------------------------------------- |
| `expectedRevision` | integer | Required | Revision last read by the caller; mismatches reject concurrent updates. minimum: 1; maximum: 9007199254740991 |

### Validation and omitted values

Queues one test to the saved, enabled recipient at the supplied revision; limited to one per hour. Requires configured email delivery and preferences that are enabled and not suppressed.

## 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 "pending" |

[Download input schema](/schemas/test_notification_email.input.json) · [Download output schema](/schemas/test_notification_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)

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