Skip to main content
export_link_watches Export monitored placements with pagination for local CRM recovery.
Available in the deployed MCP and HTTP bundle. Confirm access and inputs with your connected catalog. Workspace scopes and enabled providers still apply.
This read does not start a verification job.

Example request

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

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.

Input fields

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

Validation and omitted values

Omit cursor for the first page. Keep continuation cursors opaque and use them only with the same listing and filters. Omitting projectId reads the accessible workspace scope rather than selecting a different project. Pages are ordered by creation time, then identifier, ascending. Omitted q, state and status apply no corresponding filter. This export uses full watch records; paused watches export next_check_at as null. Follow every page for the selected dataset. When retained index observations exist and this credential has discovery:read, each watch also carries source-qualified index metadata and evidence references. These are separate from its backlink state; no provider call runs during export.

Defaults when omitted

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
  • items (array, required): Records in this bounded page.
  • next_cursor (string / null, required): Opaque continuation for the same listing; null means no further page.
  • has_more (boolean, optional): True when another page is available.
  • schema_version (number, required).
  • workspace_id (string, required): Workspace that owns this record.
  • exported_at (string, required).
  • format (string, required).
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

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.

Continue

get_evidence · get_index_observation Follow the related workflow, inspect capability status, or return to the command index.