Post v1runs
Start a new run: a new tree root, or a run that continues an existing tree when parent_run_id is set. The run begins executing immediately (status running, started_at stamped); record its outcome with CompleteRun.
Retries are safe with an idempotency-key header: repeating the request with the same key
returns the original run (in whatever state it has reached) instead of starting a second one,
and reusing a key with a different request fails with idempotency_conflict. Without a key,
every call starts a fresh run.
Authorizations
Hiloop API key sent as an HTTP Bearer token.
Headers
Optional idempotency key for this mutation. The server records the result from execution start. For at least 72 hours, reuse by the same organization and route replays the original status and body. A matching request still in flight or reuse for different input returns 409 idempotency_conflict. Keys are scoped by organization and route and contain 1-255 characters.
1 - 255Body
The project the new run belongs to.
Optional parent run to continue the tree from. Empty starts a new tree root.
An optional human-readable label.
Optional registered workload name to run as. When set, the run is attributed to that workload (the caller must hold launch rights on it and the name must be registered); when empty, the run executes as the caller's own identity. The executing identity is always declared here, never inferred from the command.
Response
OK
The newly started run, with its lineage fields resolved.