GET/user/repositories/pipeline-runs

List the pipeline runs in the repositories the caller belongs to

list_my_repository_pipeline_runs

pipeline:read
A token needs the pipeline:read scope: View pipeline runs and definitionsGranted by read_api, read_repository, write_api, write_repository.Every operation this scope unlocks
Filtered across resources
x-gitmoap-isolation: {"kind":"cross_resource_filtered"}
Paginated
Pass the next_token a page returns to get the next one.

Returns recent runs in every repository you are a member of, whoever or whatever started them, most recently started first: the view of what CI is doing across your work. It looks back days days (30 by default, at most 90). Filter by status, pipeline_id or search (pipeline name); pages hold up to 100 runs (20 by default). A service account belongs to no repositories this way and always gets an empty list.

Parameters

Query

statusPipelineStatusrunningsucceededsucceeded_with_warningsfailedtimed_outcancelledoptionalFilter by run status
pipeline_idPipelineId (string · uuid)optionalFilter by pipeline definition
searchstringoptionalSubstring match over the pipeline name
daysinteger · int64optionalTrailing window in days (1-90, default 30)
limitinteger · int32optionalPage size (1-100, default 20)
next_tokenstringoptionalOpaque pagination cursor

Responses

200Pipeline runs pageapplication/json

itemsarray of PipelineRunSummary
- The PipelineRunSummary schema
- pipeline_namestring
- pipeline_run_idPipelineRunId (string · uuid)
- repo_idRepositoryId (string · uuid)
- started_atstring
- statusPipelineStatusrunningsucceededsucceeded_with_warningsfailedtimed_outcancelledPer-PipelineRun status.
- triggerTriggerContext
  - The TriggerContext schema
  - repo_idRepositoryId (string · uuid)
  - repo_pathstring
  - before_shastring or nulloptionalThe commit the ref pointed at before the push — what a paths filter compares against. On a run started by hand, the commit its starter named to compare from, if any.
  - branchstring or nulloptional
  - buildMrBuildTargetmerge_resultsourceor nulloptionalWhich commit a merge-request-triggered run built.
  - commit_shastring or nulloptional
  - depthinteger · int32optional0–∞How many pushes made by pipeline runs led to this run, one after another; 0 when no pipeline's push started it.
  - every_stepbooleanoptionalEvery step runs, whatever its path filter says — asked for by whoever started the run.
  - extraobjectoptionalAdditional fields supplied by whatever started the run, passed along without being interpreted.
  - kindTriggerKindpushmerge_requesttagschedulemanualoptionalWhat started this run.
  - mr_idMergeRequestId (integer · int64) or nulloptional
  - paramsobjectoptionalThe values a person supplied when starting the run, keyed by the parameter names the pipeline's manual trigger declares.
  - ref_namestring or nulloptionalThe full ref (e.g. refs/tags/v1.2.0). Set for runs a tag started, which branch cannot describe.
  - root_group_idGroupId (string · uuid) or nulloptionalThe organisation this run belongs to — the root group of the repository it was triggered for. Recorded when the run starts and never recalculated, so a repository moved to a different organisation part-way through a run keeps the artifacts, logs and cache it has already produced. Absent on runs that started before runs recorded this.
  - schedule_stemstring or nulloptionalWhich scheduled trigger fired, when kind is schedule.
  - source_shastring or nulloptionalThe source-branch commit this run tested: a merge request's source head for a merge-request run, whichever commit it built, and the commit itself for a push or manual run. Set by the platform; absent on a run whose graph the caller supplied, which never counts toward a merge request's pipelines.
  - target_branchstring or nulloptionalThe merge request's target branch.
  - target_shastring or nulloptionalThe target branch's tip this merge-request run was tested against. Once the target branch moves on, the merge check reports a merge-result run as out of date.
  - triggered_byActorSummaryoptionalWho started the run, set by the platform from the authenticated caller; a value supplied in a request is ignored.
  - trustTriggerTrusttrusteduntrustedoptionalWhether the code being built is trusted with the repository's connections and secrets. Set by the platform when the run starts, whatever a request says.
  - trust_reasonTrustReason or nulloptionalWhy the run has the trust it has: who wrote the code, a person's merge or approval, or the organization's AI configuration. Absent on runs that started before this was recorded.
- finished_atstring or nulloptional
- pipeline_idPipelineId (string · uuid) or nulloptionalThe pipeline definition this run was started from. Absent when that definition has since been deleted; pipeline_name still names what ran.
- re_run_ofPipelineRunId (string · uuid) or nulloptional
- stagesarray of StageRollupoptionalPer-stage counts of how many steps are in each status, in execution order — enough to draw the run's shape in a list. Empty for older runs recorded before these counts existed.
  - The StageRollup schema
  - barrier_passedbooleanWhether every step in the stage has finished.
  - countsNodeStatusCounts
  - stage_idStageId (string)
  - stage_indexinteger · int320–∞
  - tolerated_failuresinteger · int32optional0–∞How many of the stage's failed or timed-out steps were allowed to fail, so they degrade the run rather than fail it. Left out when zero.
next_tokenstring or nulloptional

200 exampleSynthesized example

400Invalid query parameterapplication/json

Error codes

BAD_REQUESTThe request is malformed: a parameter or a body field is not a well-formed value of its type

errorErrorBody
- The ErrorBody schema
- codestringThe coarse category, tied to the status: NOT_FOUND, CONFLICT, INSUFFICIENT_SCOPE. Every error has one; the API reference's error catalogue lists them all.
- messagestringWhat went wrong, for a person. Written to be read, not parsed: match on reason or code.
- fieldstring or nulloptionalOn a 400 that refused one field's value, the field, as its JSON path: email, items[0].name. Put the message under that input. Absent on every other error.
- reasonstring or nulloptionalThe specific code, when the error has one: LAST_ORGANIZATION_OWNER, BRANCH_PROTECTED. The message starts with it too. Match on this when it is present, and on code otherwise.
- required_scopestring or nulloptionalThe scope the access token was missing, on INSUFFICIENT_SCOPE.
- violationsanyoptionalPresent on the structured-validation errors (PROVIDER_VALIDATION_FAILED per-node, PIPELINE_VALIDATION_FAILED DAG): a JSON array of the offending elements, so a caller can fix every one in a single round-trip. Absent (omitted) on every other error.

400 exampleSynthesized example

401application/json

Error codes

UNAUTHORIZEDNo credential was sent, or the one sent is invalid, expired or revoked

errorErrorBody
- The ErrorBody schema
- codestringThe coarse category, tied to the status: NOT_FOUND, CONFLICT, INSUFFICIENT_SCOPE. Every error has one; the API reference's error catalogue lists them all.
- messagestringWhat went wrong, for a person. Written to be read, not parsed: match on reason or code.
- fieldstring or nulloptionalOn a 400 that refused one field's value, the field, as its JSON path: email, items[0].name. Put the message under that input. Absent on every other error.
- reasonstring or nulloptionalThe specific code, when the error has one: LAST_ORGANIZATION_OWNER, BRANCH_PROTECTED. The message starts with it too. Match on this when it is present, and on code otherwise.
- required_scopestring or nulloptionalThe scope the access token was missing, on INSUFFICIENT_SCOPE.
- violationsanyoptionalPresent on the structured-validation errors (PROVIDER_VALIDATION_FAILED per-node, PIPELINE_VALIDATION_FAILED DAG): a JSON array of the offending elements, so a caller can fix every one in a single round-trip. Absent (omitted) on every other error.

401 exampleSynthesized example

403Forbidden — the caller's access level or token scope is insufficientapplication/json

Error codes

FORBIDDENYou are signed in but may not do this here; reason names the permission or the rule that refused it
INSUFFICIENT_SCOPEThe access token lacks the scope this operation needs; required_scope names it
PERMISSION_REQUIREDYou need a permission you do not hold here; the message names it

errorErrorBody
- The ErrorBody schema
- codestringThe coarse category, tied to the status: NOT_FOUND, CONFLICT, INSUFFICIENT_SCOPE. Every error has one; the API reference's error catalogue lists them all.
- messagestringWhat went wrong, for a person. Written to be read, not parsed: match on reason or code.
- fieldstring or nulloptionalOn a 400 that refused one field's value, the field, as its JSON path: email, items[0].name. Put the message under that input. Absent on every other error.
- reasonstring or nulloptionalThe specific code, when the error has one: LAST_ORGANIZATION_OWNER, BRANCH_PROTECTED. The message starts with it too. Match on this when it is present, and on code otherwise.
- required_scopestring or nulloptionalThe scope the access token was missing, on INSUFFICIENT_SCOPE.
- violationsanyoptionalPresent on the structured-validation errors (PROVIDER_VALIDATION_FAILED per-node, PIPELINE_VALIDATION_FAILED DAG): a JSON array of the offending elements, so a caller can fix every one in a single round-trip. Absent (omitted) on every other error.

403 exampleSynthesized example

CLI

gitmoap pipeline-runs list-my-repository

--daysnumberoptionalTrailing window in days (1-90, default 30)
--limitnumberoptionalPage size (1-100, default 20)
--next-tokenstringoptionalOpaque pagination cursor
--pipeline-ididoptionalFilter by pipeline definition
--searchstringoptionalSubstring match over the pipeline name
--statusrunning | succeeded | succeeded_with_warnings | failed | timed_out | cancelledoptionalFilter by run status

Used in these guides

Pipelines

Request

curl "https://api.gitmoap.com/user/repositories/pipeline-runs" \
  -H "Authorization: Bearer $GITMOAP_TOKEN"

gitmoap pipeline-runs list-my-repository

import { createApiClient } from "@gitmoap/backend-types";

const client = createApiClient({
  baseUrl: "https://api.gitmoap.com",
  headers: { Authorization: `Bearer ${process.env.GITMOAP_TOKEN}` },
});

const { data, error } = await client.GET("/user/repositories/pipeline-runs");

GET /user/repositories/pipeline-runs HTTP/1.1
Host: api.gitmoap.com
Authorization: Bearer $GITMOAP_TOKEN

⌘↵

Send to see the sandbox's answer. Nothing leaves your browser.