Checks

Checks are run records created by schedules or manual runs. Their status and execution data evolve until finalization; the terminal result is then immutable. API keys have read-only access through v1.checks:read.

Find checks

List filters support:

• schedule_id or a case-insensitive schedule_name
• engine
• worker_id
• status
• started_from: manual or scheduled
• created_at_since: an inclusive ISO 8601 timestamp with an explicit offset or Z; values without one, and date-only values, are rejected with 400

A check's detail also carries planned_run_at, the cron occurrence a scheduled check was dispatched for (null for manual runs), while created_at is the moment the check was created and started_at the moment a worker claimed it.

Count checks without pagination

POST /v1/checks/summary takes project_id and a required top-level created_at_since timestamp:

{  "project_id": "65f0c7a9a7d6b4e2c1234567",  "created_at_since": "2026-10-01T00:00:00Z"}

It returns data.created_at_since, data.total, and data.by_status, counting all project checks created at or after that timestamp. It has no pagination or list filters beyond this lower bound. Missing or blank statuses count as unknown; zero-count status buckets are omitted. A summary timeout returns 503.

Statuses are queued, leased, running, success, timeout, failed_infra, failed_configuration, failed_download, failed_restore, failed_probe, failed_quota, and failed_other. See Check results for their meanings.

Read logs and evidence

Use the log endpoint for structured sections or download the merged log as plain text. A log response can report incomplete: true; treat it as a partial view and inspect incomplete_reason.

Audit proof downloads support:

• json for the canonical check document
• ots for the binary OpenTimestamps proof, when available

The backup file a check used

A finished check can record the selected file in result.artifact:

After a failed download, size_bytes and sha256 are null and complete is false. A restore failure can still carry complete artifact metadata. The field can be absent when no file was selected, the worker could not report it, or the check predates artifact reporting.

payload.source_endpoint snapshots the source connection at dispatch. It supplies the address even after the source is edited or deleted. Both it and result.artifact, when present, are covered by the canonical JSON audit hash and its OpenTimestamps proof. The artifact checksum and the JSON proof digest are different values.

Endpoint reference

• List checks
• Summarize check statuses
• Get check details
• Read check log sections
• Download a check log
• Download audit evidence