Skip to main content
get_link_change_report Read retained placement changes in one recent UTC period for an authorized website. The bounded response names its frozen request boundary, row count, truncation and retention uncertainty; incomplete results do not prove a quiet period.
Name recorded in the 2026-10-27 deployment. This page describes current source; verify inputs and access in your connected catalog. Provider configuration and workspace access 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

Schema-validated example; IDs and dates are illustrative. 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

projectId is required and must be accessible to the current principal. from is an exact UTC timestamp with milliseconds, earlier than the request time and no more than 31 days old. The service fixes as_of and through_sequence for this response, examines at most the latest 10,000 workspace event sequence positions, returns at most 500 retained placement-acquired, recovered or lost events newest first, and never continues the older cursor feed. complete describes this bounded retained-event read. A retention floor, scan limit or truncation makes it false; shown counts are then a lower bound. Even a complete empty report does not prove that no unobserved link changed.

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
  • schema_version (number, required).
  • workspace_id (string, required): Workspace that owns this record.
  • project_id (string, required): Project that owns this record.
  • coverage_scope (string, required).
  • from (string, required).
  • as_of (string, required).
  • through_sequence (number, required).
  • count (number, required).
  • limit (number, required).
  • truncated (boolean, required).
  • complete (boolean, required).
  • retention_limited (boolean, required).
  • scan_limit (number, required).
  • scan_limited (boolean, required).
  • events (array, required).
Types, allowed values, limits and nested fields:
Download input schema · Download output schema

Errors and retries

Follow the error recovery before retrying this read. Preserve the selected workspace, project, filters and feed. Recovering a read does not require an idempotency key or another verification job. Operation-specific errors include INVALID_INPUT, PROJECT_NOT_FOUND, WORKSPACE_ACCESS_DENIED, INSUFFICIENT_SCOPE. 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

list_events · get_link_reports Follow the related workflow. See capability status for availability or the command index for another operation.