Skip to main content
GET
Get pipeline logs
Requires a ServiceKey. See Service Keys.
Returns the concatenated tail of stdout/stderr for each pod backing the pipeline worker. The response is shaped as data.pods[], with one entry per replica - single-replica pipelines return a one-element array.
The logs field on each pod is a single string, not a list of structured log entries. Newlines separate lines. Filter, parse, or tail it client-side.
If the pod is still being scheduled, has just crashed, or has been replaced, the logs field may contain a runtime tail error such as unable to upgrade connection: container not found. The envelope-level error field is still false in this case - the API call itself succeeded, but there was nothing to tail. Retry after the pipeline reaches RUNNING via status.
Useful when:
  • A POST succeeded but status is FAILED.
  • destination-health reports unhealthy and you need the underlying connection error.
  • Records are not arriving at the destination and you want to see normalization or transform errors.

Authorizations

Authorization
string
header
required

Pipeline REST endpoints require a ServiceKey. Regular GoldRush API keys are rejected with 403. See Service Keys.

Path Parameters

pipeline_id
string
required

The pipeline identifier, prefixed with pipe_.

Response

Recent pipeline logs.

data
object
error
boolean
error_message
string | null
error_code
string | null