Read change events

list_events Read change events from one feed using an opaque cursor: feed links for placement changes, feed targets for destination-health changes. The two feeds keep separate cursors; a broken destination does not imply its source backlink disappeared. Apply a full page locally before saving next_cursor.

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": "list_events",
    "arguments": {
      "feed": "links",
      "limit": 50
    }
  }
}

agentlinkops call list_events --args '{"feed":"links","limit":50}'

curl "$AGENTLINKOPS_API_URL/v1/commands/list_events" \
  -H "Authorization: Bearer $AGENTLINKOPS_API_KEY" \
  -H 'Content-Type: application/json' \
  --data '{"feed":"links","limit":50}'

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.

{
  "workspace_id": "ws_example",
  "events": [],
  "next_cursor": "example_opaque_cursor",
  "has_more": false
}

Response formats

format selects the row shape. detailed is the example above: every field. concise keeps, per row: id, type, watch_id, target_id, created_at, cursor, data (before and after snapshots without occurrences, expectations and signatures; observation_id; evidence_key); every top-level field (cursors, counts, coverage, metadata) is kept in both. The observation state an unknown-versus-absent decision depends on is never dropped. MCP and code mode default to concise; the CLI and HTTP default to detailed; the response names the default it applied in defaults_applied.

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
`feed`	string	Required	Which change feed to read: links (placement changes) or targets (destination-health changes); each feed keeps its own cursor. values: “links”, “targets”
`cursor`	string	Optional	Opaque continuation returned by this same listing; omit for the first page.
`limit`	integer	Optional	Maximum rows in this page or bounded report; subject to the schema maximum. minimum: 1; maximum: 100; default: 50
`projectId`	string	Optional	Identifier of the project returned by its create or list operation. minLength: 1; maxLength: 200
`format`	string	Optional	Response shape: concise keeps the fields needed to decide and to call next (the evidence state always included); detailed returns every field. MCP and code mode default to concise; REST and the CLI to detailed. The response names the default it applied in defaults_applied. values: “concise”, “detailed”

Validation and omitted values

feed selects one of two independent feeds with separate cursors: links for placement changes, targets for destination-health changes. Never reuse a cursor across feeds. The retired names list_link_events and list_target_events resolve here with the feed implied. 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. Events are ordered by sequence ascending. Apply the entire returned page before persisting the next cursor. Each event feed has its own cursor history. Without a cursor, reads start at the beginning of retained source-event history. An expired supplied cursor returns snapshot recovery instructions. Without a cursor, reads start at the beginning of retained destination-event history. An expired supplied cursor returns destination snapshot recovery instructions.

Defaults when omitted

Field	Default
`limit`	`50`

Output fields

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

workspace_id (string, optional): Workspace that owns this record.
events (array, required).
next_cursor (string, required): Opaque checkpoint for this feed. Save it after processing the events, even when has_more is false. Continue paging only while has_more is true.
has_more (boolean, required): True when another page is available.

All fields and nested objects

Field	Type	Presence	Meaning and constraints
`workspace_id`	string	Optional	Workspace that owns this record.
`events`	array	Required
`events[].id`	string	Required	Resource identifier returned by the operation.
`events[].workspace_id`	string	Optional	Workspace that owns this record.
`events[].project_id`	string / null	Optional	Project that owns this record.
`events[].watch_id`	string	Optional	Identifier returned by the related operation.
`events[].target_id`	string	Optional	Identifier returned by the related operation.
`events[].type`	string	Optional
`events[].created_at`	string	Optional	UTC timestamp when the record was created.
`events[].cursor`	string	Optional
`events[].data`	object	Required
`events[].data.before`	any	Optional
`events[].data.after`	any	Optional
`events[].data.state`	string	Optional	Saved lifecycle or evidence state, as enumerated for this record.
`events[].data.reason`	string / null	Optional	Recorded explanation; null when no explanation applies.
`events[].data.observation_id`	string	Optional	Identifier returned by the related operation.
`next_cursor`	string	Required	Opaque checkpoint for this feed. Save it after processing the events, even when has_more is false. Continue paging only while has_more is true.
`has_more`	boolean	Required	True when another page is available.

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.

Method and route	Success	Details
`GET /v1/events`	200	Remaining read arguments go in query parameters.
`GET /v1/target-events`	200	Remaining read arguments go in query parameters.

Continue

export_link_watches · list_targets 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

Example request

Returned result

Response formats

Input fields

Validation and omitted values

Defaults when omitted

Output fields

Errors and retries

HTTP resource routes

Continue

​Example request

​Returned result

​Response formats

​Input fields

​Validation and omitted values

​Defaults when omitted

​Output fields

​Errors and retries

​HTTP resource routes

​Continue

Example request

Returned result

Response formats

Input fields

Validation and omitted values

Defaults when omitted

Output fields

Errors and retries

HTTP resource routes

Continue