The pipelines API provides read-only access to CI/CD run history that the platform ingests automatically from your connected source control providers. When a pipeline run completes in GitHub Actions or GitLab CI, a webhook payload is delivered to the platform and stored as a structured run record. You can query this history to surface build trends, correlate deploys with incidents, or feed data into reporting dashboards — no manual data entry required. All requests require a Bearer token in theDocumentation Index
Fetch the complete documentation index at: https://docs.scrubbe.com/llms.txt
Use this file to discover all available pages before exploring further.
Authorization header.
Pipeline runs are created exclusively through GitHub and GitLab webhook ingestion. The API does not expose endpoints for creating, updating, or deleting run records.
List pipeline runs
GET https://your-api-domain.com/api/v1/pipelines
Returns a paginated list of all ingested pipeline run records, ordered by start time descending (most recent first).
Query parameters
Page number for pagination.
Number of records to return per page.
Filter by run status. Accepted values:
success, failure, cancelled, in_progress.Filter by source provider. Accepted values:
github, gitlab.Filter runs to a specific repository, in
owner/repo format.Filter runs triggered from a specific branch.
Response fields
Array of pipeline run summary objects.
Pagination metadata.
Get a pipeline run
GET https://your-api-domain.com/api/v1/pipelines/:id
Returns the full detail record for a single pipeline run, including individual job or stage results if available in the webhook payload.
Path parameters
The unique identifier of the pipeline run record.
Response fields
Unique run record identifier.
Source provider:
github or gitlab.Repository in
owner/repo format.Branch the pipeline ran against.
Full SHA of the triggering commit.
The commit message associated with the triggering commit.
Username or actor that triggered the pipeline.
Final run status:
success, failure, cancelled, or in_progress.ISO 8601 timestamp when the run began.
ISO 8601 timestamp when the run completed.
null if still in progress.Total run duration in seconds.
Individual job or stage results, if provided by the webhook payload.
The original webhook payload received from the provider, stored for auditability.