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.
string
Only runs for this pipeline.
string
queued, running, succeeded, failed, canceled, and so on.
string
Encoded range (for example 2025-03-01..2025-03-31) or separate from/to if your deployment exposes them.
integer
Page size.
string
Pagination cursor.

GET /api/runs/{id}

Full run record: status, timing, row counts, errors, and trigger metadata.
string
required
Run ID.
string
Terminal or in-progress state.
object
Aggregated counters (rows read/written, bytes, cost units).
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.
string
required
Run ID.

GET /api/runs/{id}/logs

Execution logs (plain text chunks, JSON lines, or URLs to object storage, depending on deployment).
string
required
Run ID.
string
Filter to a single node’s log stream.
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.
string
required
Run ID.

Status reference

Trigger a run

POST /api/pipelines/{id}/run

Run history (UI)

How runs appear in the product.