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

# Save owner digest

> Set your own website digest to off, daily or weekly at 03:00 UTC.

`save_owner_digest`

Set your own website digest to off, daily or weekly at 03:00 UTC. No recipient override; live delivery remains separately gated.

<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                                                   |
| --------------------- | ---------------------------------------------------------- |
| `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": "save_owner_digest",
      "arguments": {
        "projectId": "project_example",
        "revision": 0,
        "frequency": "off",
        "categories": [
          "placements",
          "destinations"
        ]
      }
    }
  }
  ```

  ```bash CLI theme={null}
  agentlinkops call save_owner_digest --args '{"projectId":"project_example","revision":0,"frequency":"off","categories":["placements","destinations"]}'
  ```

  ```bash HTTP theme={null}
  curl "$AGENTLINKOPS_API_URL/v1/commands/save_owner_digest" \
    -H "Authorization: Bearer $AGENTLINKOPS_API_KEY" \
    -H 'Content-Type: application/json' \
    --data '{"projectId":"project_example","revision":0,"frequency":"off","categories":["placements","destinations"]}'
  ```
</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}
{
  "projectId": "project_example",
  "revision": 1,
  "frequency": "off",
  "categories": [
    "placements",
    "destinations"
  ],
  "recipient": null,
  "hourUtc": 3,
  "weekdayUtc": 1,
  "nextAt": null,
  "delivery": "disabled"
}
```

## 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                                                                                       |
| ------------ | ------- | -------- | ------------------------------------------------------------------------------------------------------------- |
| `projectId`  | string  | Required | Identifier of the project returned by its create or list operation. minLength: 1; maxLength: 200              |
| `revision`   | integer | Required | Immutable set revision to read or compare. minimum: 0; maximum: 9007199254740991                              |
| `frequency`  | string  | Required | The frequency value; allowed values and bounds are specified in this schema. values: "off", "daily", "weekly" |
| `categories` | array   | Required | The categories value; allowed values and bounds are specified in this schema. minItems: 1; maxItems: 5        |

### Validation and omitted values

Requires a signed-in owner or administrator. Recipients come from the verified account address, never request arguments.

Delivery must be separately enabled. Accepted handoff is not confirmed delivery; unknown outcomes are retained and never blindly resent. Exact event links may expire with retained history.

## 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                                                                                                 |
| ------------ | ------------- | -------- | ----------------------------------------------------------------------------------------------------------------------- |
| `projectId`  | string        | Required | Identifier returned by the related operation. minLength: 1; maxLength: 200                                              |
| `revision`   | integer       | Required | Optimistic concurrency revision; supply it as expectedRevision on the next write. minimum: 0; maximum: 9007199254740991 |
| `frequency`  | string        | Required | values: "off", "daily", "weekly"                                                                                        |
| `categories` | array         | Required |                                                                                                                         |
| `recipient`  | string / null | Required |                                                                                                                         |
| `hourUtc`    | number        | Required | must equal 3                                                                                                            |
| `weekdayUtc` | number        | Required | must equal 1                                                                                                            |
| `nextAt`     | string / null | Required | UTC timestamp of the next scheduled summary; null while notifications are disabled.                                     |
| `delivery`   | string        | Required | values: "disabled", "ready"                                                                                             |

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

## Errors and retries

This command is not annotated idempotent. After a timeout, inspect existing state before repeating a write. Operation-specific errors include `OWNER_DIGEST_HUMAN_REQUIRED`, `OWNER_DIGEST_ACCESS_DENIED`, `OWNER_DIGEST_NOT_READY`, `OWNER_DIGEST_SCOPE_CLOSED`, `OWNER_DIGEST_CONFLICT`, `OWNER_DIGEST_RECIPIENT_REQUIRED`, `OWNER_DIGEST_SUPPRESSED`, `OWNER_DIGEST_EVENT_EXPIRED`, `INVALID_OWNER_DIGEST_INPUT`, `INVALID_CURSOR`.

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

[get\_owner\_digest](/reference/commands/get_owner_digest) · [list\_owner\_digest\_deliveries](/reference/commands/list_owner_digest_deliveries)

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