Skip to main content
GET
Retrieve task run logs
Use this endpoint to stream structured log entries produced during automation. Entries are returned in ascending chronological order. New logs become available moments after they are persisted by the runner.

Request

Path parameters

  • runId — UUID of the run whose logs you want to inspect.

Example

Responses

  • 200 OK — Returns { "runId": UUID, "logEntries": LogEntry[] }.
  • 400 Bad Request — Invalid run ID.
  • 401 Unauthorized — Missing or malformed API key.
  • 404 Not Found — The run is not visible to the authenticated organization.

Log entry schema

Each item in logEntries contains the following fields:
  • id (UUID) — Unique identifier for the log row.
  • timestamp (string | null) — ISO 8601 timestamp when the event was recorded.
  • level (“info” | “warning” | “error”) — Normalized severity.
  • message (string) — Human-readable summary of the event. Empty strings may appear when the underlying step emits no message.
  • nodeId (string | null) — Identifier of the builder node that produced the log, if available.
  • nodeName (string | null) — Human-readable name of the node, derived from the task definition.
  • inputs (object, optional) — Input values for this step. Only present when the step recorded inputs.
  • outputs (object, optional) — Output values from this step. Only present when the step produced outputs.
Combine this endpoint with task-run.log webhook deliveries to monitor runs in near real time.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

runId
string<uuid>
required

UUID of the run to inspect.

Response

Log entries returned.

runId
string<uuid>
required
logEntries
object[]
required