Skip to main content
get_history List paginated saved observations for one monitored subject: subject link for a placement (subjectId is the watch id), subject target for a destination (subjectId is the target id). Includes evidence references and retention limits.
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.

Response formats

format selects the row shape. detailed is the example above: every field. concise keeps, per row: id, state, reason, checked_at, job_id, evidence_key, result (state, reason, checkedAt, httpStatus, checkerVersion, evidence, redirects, occurrenceCount); 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.

Validation and omitted values

subject selects the timeline: link lists a placement’s observations and subjectId is its watch id; target lists a destination’s health observations and subjectId is its target id. The retired names get_link_history (watchId) and get_target_history (targetId) resolve here. Omit cursor for the first page. Keep continuation cursors opaque and use them only with the same listing and filters. History pages are ordered by checked_at, then identifier, ascending.

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.
  • history_compacted_before (string / null, optional).
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 · locate_link Follow the related workflow, inspect capability status, or return to the command index.