Skip to content
GitmoapAPIBeta
Buildpipelines
GET/repositories/{repo_id}/trigger-evaluations

Why a ref update did or did not start a pipeline run.

list_trigger_evaluations
  • 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
  • Single-resource

    x-gitmoap-isolation: {"kind":"single_or_self_scoped"}

  • Paginated
    Pass the next_token a page returns to get the next one.

Every evaluation is recorded, including the ones that did nothing: "I pushed and nothing happened" is the most common question a CI system is asked, and answering it with silence makes the user bisect their own configuration.

Parameters

Path
  • repo_idRepositoryId (string · uuid)Repository id
Query
  • ref_namestringoptionalExact ref (refs/heads/main)
  • kindTriggerKindpushmerge_requesttagschedulemanualoptionalpush | merge_request | tag | schedule
  • outcomeTriggerOutcomematchedno_trigger_matchnot_registered_at_refdraftauthority_deniedauthority_unresolvableauthority_revokedquota_exhaustedloop_guardsupersededprovider_validation_failedconnection_resolution_faileddefinition_invalidalready_triggeredmerge_conflictoptionalFilter to one outcome
  • commit_shastringoptionalEvery evaluation for one commit
  • pipeline_idPipelineId (string · uuid)optionalOnly one pipeline's evaluations
  • actionablebooleanoptionaltrue: only the refusals somebody can act on — a pipeline that should have started and could not
  • limitinteger · int32optionalMax 100, default 20
  • next_tokenstringoptionalOpaque pagination cursor

Responses

200Trigger evaluations, newest firstapplication/json
  • itemsarray of TriggerEvaluation
    • The TriggerEvaluation schema
    • commit_shastring
    • idTriggerEvaluationId (string · uuid)
    • kindTriggerKindpushmerge_requesttagschedulemanualWhat caused a run to start.
    • occurred_atstringWhen the evaluation happened, RFC 3339.
    • outcomeTriggerOutcomematchedno_trigger_matchnot_registered_at_refdraftauthority_deniedauthority_unresolvableauthority_revokedquota_exhaustedloop_guardsupersededprovider_validation_failedconnection_resolution_faileddefinition_invalidalready_triggeredmerge_conflictWhy a pipeline did or did not start for a ref update. matched means a run started. Otherwise: no_trigger_match (no trigger matched the event, ref or paths), not_registered_at_ref (no pipeline at that ref), draft (the pipeline is a draft), authority_denied (whoever pushed lacks Developer access), authority_unresolvable (whoever caused the event could not be identified), authority_revoked (the owner of a schedule lost Developer access), quota_exhausted, loop_guard (a pipeline's own push, without opt-in or too many in a row), superseded (replaced by a newer run), provider_validation_failed, connection_resolution_failed, definition_invalid, already_triggered (the same event was already handled) or merge_conflict (the merge result could not be built).
    • ref_namestring
    • repository_idRepositoryId (string · uuid)
    • actorActorSummary or nulloptionalWhose access the evaluation was checked against.
    • before_shastring or nulloptionalThe commit the ref pointed at before the update this evaluation was about — with commit_sha, the range a retry evaluates again. Absent for a ref that was created, and for evaluations recorded before the range was kept.
    • detailobjectoptionalWhatever makes the outcome actionable rather than merely named — the declared patterns, the quota gate that closed, the violation list.
    • pipeline_idPipelineId (string · uuid) or nulloptional
    • pipeline_run_idPipelineRunId (string · uuid) or nulloptional
    • stemstring or nulloptional
  • next_tokenstring or nulloptional
200 exampleSynthesized example
{
"items": [
{
"commit_sha": "9bc8bb898adf5717f7c8350686e425d4c4aab687",
"id": "913bd857-d90b-4de3-9e2d-6744a7718655",
"kind": "push",
"occurred_at": "2026-10-13T18:05:43Z",
"outcome": "matched",
"ref_name": "payments-api",
"repository_id": "5b0e7c2a-9d14-4e8b-a6f1-2c3d4e5f6a70"
}
],
"next_token": "next-token-16ab"
}
400Bad request — a path parameter is not a well-formed value of its typeapplication/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
{
"error": {
"code": "code-9639",
"message": "Draw the region map from operation density"
}
}
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
{
"error": {
"code": "code-0f1e",
"message": "Draw the region map from operation density"
}
}
403application/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
{
"error": {
"code": "code-9540",
"message": "Draw the region map from operation density"
}
}
404Repository absent, or Private and the caller is not a memberapplication/json
Error codes
  • NOT_FOUNDThe resource does not exist — or exists and you cannot see it: a private resource you have no access to answers exactly as an absent one does
  • 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.
404 exampleSynthesized example
{
"error": {
"code": "code-116f",
"message": "Inline scalar newtypes but keep their brand"
}
}

CLI

gitmoap pipelines list-trigger-evaluations

  • --repo-ididRepository id (id or owner/repo path)
  • --actionableflagoptional`true`: only the refusals somebody can act on — a pipeline that should have started and could not
  • --commit-shastringoptionalEvery evaluation for one commit
  • --kindpush | merge_request | tag | schedule | manualoptionalpush | merge_request | tag | schedule
  • --limitnumberoptionalMax 100, default 20
  • --next-tokenstringoptionalOpaque pagination cursor
  • --outcomematched | no_trigger_match | not_registered_at_ref | draft | authority_denied | authority_unresolvable | authority_revoked | quota_exhausted | loop_guard | superseded | provider_validation_failed | connection_resolution_failed | definition_invalid | already_triggered | merge_conflictoptionalFilter to one outcome
  • --pipeline-ididoptionalOnly one pipeline's evaluations
  • --ref-namestringoptionalExact ref (`refs/heads/main`)

Used in these guides