Skip to main content
A run is one execution of a pipeline graph. Use these endpoints to audit outcomes, drill into per-node metrics, stream logs, and cancel work. Base URL: https://api.planasonix.com
Auth: Authorization: Bearer plus your API key or JWT.

GET /api/runs

List runs across pipelines with filters.
pipelineId
string
Only runs for this pipeline.
status
string
queued, running, succeeded, failed, canceled, and so on.
dateRange
string
Encoded range (for example 2025-03-01..2025-03-31) or separate from/to if your deployment exposes them.
limit
integer
Page size.
cursor
string
Pagination cursor.

GET /api/runs/{id}

Full run record: status, timing, row counts, errors, and trigger metadata.
id
string
required
Run ID.
status
string
Terminal or in-progress state.
metrics
object
Aggregated counters (rows read/written, bytes, cost units).
error
object
Present when status is failed; includes message and optional stack reference.

GET /api/runs/{id}/nodes

Per-node execution: start/finish times, state, retries, and row counts.
id
string
required
Run ID.

GET /api/runs/{id}/logs

Execution logs (plain text chunks, JSON lines, or URLs to object storage, depending on deployment).
id
string
required
Run ID.
nodeId
string
Filter to a single node’s log stream.
since
string
ISO timestamp or log cursor for incremental fetch.

DELETE /api/runs/{id}

Request cancellation of a running or queued run. Completed runs return 409 or 400 depending on policy.
id
string
required
Run ID.

Status reference

StatusMeaning
queuedScheduled or manual run waiting for capacity
runningActively executing
succeededAll nodes completed without fatal errors
failedOne or more nodes failed or policy aborted the run
canceledUser or system canceled the run

Trigger a run

POST /api/pipelines/{id}/run

Run history (UI)

How runs appear in the product.