Get notification preferences

get_notification_preferences Read your personal workspace email subscription. Delivery availability is separate from saved preferences.

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

Access	Behavior
`events:read`	Reads saved data

This read does not start a verification job.

Example request

Connect through MCP, CLI, or HTTP. Replace example identifiers with records from your workspace.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_notification_preferences",
    "arguments": {}
  }
}

agentlinkops call get_notification_preferences --args '{}'

curl "$AGENTLINKOPS_API_URL/v1/commands/get_notification_preferences" \
  -H "Authorization: Bearer $AGENTLINKOPS_API_KEY" \
  -H 'Content-Type: application/json' \
  --data '{}'

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.

{
  "revision": 1,
  "email": "owner@example.com",
  "enabled": true,
  "frequency": "daily",
  "timezone": "UTC",
  "hour": 9,
  "weekday": 1,
  "categories": [
    "placements",
    "destinations"
  ],
  "projectIds": null,
  "suppressedReason": null,
  "nextAt": "2026-09-14T09:00:00.000Z",
  "deliveryAvailable": 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. This operation accepts an empty object.

Validation and omitted values

Preferences are personal to the calling member in this workspace. deliveryAvailable reports environment configuration, not whether preferences are saved.

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.

Field	Type	Presence	Meaning and constraints
`revision`	number	Required	Optimistic concurrency revision; supply it as expectedRevision on the next write.
`email`	string	Required
`enabled`	boolean	Required
`frequency`	string	Required	values: “immediate”, “daily”, “weekly”
`timezone`	string	Required
`hour`	number	Required
`weekday`	number	Required
`categories`	array	Required
`projectIds`	array / null	Required
`suppressedReason`	string / null	Required	Provider bounce, complaint or suppression reason that stopped delivery; null when the recipient is deliverable.
`nextAt`	string / null	Required	UTC timestamp of the next scheduled summary; null while notifications are disabled.
`deliveryAvailable`	boolean	Required	True only when this environment has email delivery configured; saved preferences never imply delivery.

Download input schema · Download output schema

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

save_notification_preferences · list_notification_deliveries Follow the related workflow, inspect capability status, or return to the command index.

Overview

MCP, CLI and API commands

CLI client

HTTP and events

Optional local workflows

Get notification preferences

Example request

Returned result

Input fields

Validation and omitted values

Output fields

Errors and retries

HTTP resource routes

Continue

​Example request

​Returned result

​Input fields

​Validation and omitted values

​Output fields

​Errors and retries

​HTTP resource routes

​Continue

Example request

Returned result

Input fields

Validation and omitted values

Output fields

Errors and retries

HTTP resource routes

Continue