Skip to main content
get_candidate_verification_batch Read batch progress, individual job observations and reserved, consumed and released check units. Unknown observations do not establish absence.
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: ordinal, candidate_id, local_reference, job_id, watch_id, state, error_code, observation, usage; 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

Inspect per-item state, observation and reservation totals even when the aggregate batch is completed or partial.

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): must equal 1
  • id (string, required): Resource identifier returned by the operation.
  • workspace_id (string, required): Workspace that owns this record.
  • project_id (string, required): Project that owns this record.
  • run_id (string, required): Identifier returned by the related operation.
  • state (string, required): Saved lifecycle or evidence state, as enumerated for this record. values: “pending”, “completed”, “partial”, “failed”
  • counts (object, required): additional fields rejected
  • items (array, required): Records in this bounded page. minItems: 1; maxItems: 50
  • reservation (object / null, required).
  • replayed (boolean, optional): True when the response reuses an earlier request with the same idempotency value.
  • recurring_monitoring_created (boolean, required): Whether this operation enrolled recurring monitoring. must equal false
  • created_at (string, required): UTC timestamp when the record was created.
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

monitor_discovery_candidate Follow the related workflow, inspect capability status, or return to the command index.