Skip to main content
GET
Get blueprint run status
Returns a customer-safe status projection: lifecycle status, a coarse progress step, timestamps, and a structured terminal error when failed. Never returns inputs, outputs, file URLs, or run content.
runId accepts either the opaque run_... id or the UUID run_key from the trigger response.

Status values

Poll every 2–5 seconds. progress_step is a coarser lifecycle hint that may gain Blueprint-defined milestones later — treat it as an open string set.

Terminal errors

When status is failed, error is present: Today every failure uses execution_failed. More specific Blueprint-defined codes will be added later without changing this shape — branch on codes you know and fall back to a generic retry path otherwise. See Triggering Blueprint runs and Get Blueprint run results.

Authorizations

Authorization
string
header
required

Your Rubie API key as a bearer token.

Path Parameters

runId
string
required

Opaque run_... id from the trigger response (UUID run_key also accepted).

Response

Status projection

id
string
required
Example:

"run_MQ"

run_key
string<uuid>
required
status
enum<string>
required
Available options:
queued,
running,
completed,
failed,
cancelled
progress_step
enum<string>
required

Coarse lifecycle step. Today it closely tracks status; finer Blueprint-defined milestones will be added later, so treat this as an open string set rather than a fixed enum.

Available options:
queued,
authenticating,
running,
awaiting_review,
completed,
failed,
cancelled,
unknown
created_at
string<date-time>
required
blueprint_id
string
required
Example:

"bp_MQ"

started_at
string<date-time> | null
ended_at
string<date-time> | null
error
object | null

Present only when status is failed. Today the API returns a single generic code; richer Blueprint-defined codes will be added later without changing this shape, so treat code as an open string set.