Skip to content
GitmoapAPIBeta
Integrateprovider-connections
GET/repositories/{repo_id}/resolved-provider-connections

List the provider connections a repository's pipelines can use

resolve_repo_connections
  • provider_connection:read
    A token needs the provider_connection:read scope: View provider connectionsGranted by read_api, write_api.Every operation this scope unlocks
  • Audited · sensitive read

    x-gitmoap-audit: {"kind":"audited","arg":"sensitive_read"}

  • Filtered across resources

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

Combines the repository's own connections with those of every group above it. Where two of them define a connection for the same provider under the same name, the one nearest the repository wins. Each entry says whether it is inherited, and one inherited from a group you cannot see shows only its provider and name. Credential values are never returned, only references to where they are kept. Reporters and above, as members of the repository: a public repository does not make its connections readable.

Parameters

Path
  • repo_idRepositoryId (string · uuid)Repository id

Responses

200application/json
  • itemsarray of ResolvedConnection
    • The ResolvedConnection schema
    • auth_modeConnectionAuthModestatic_credentialsoidc_federationHow this connection authenticates.
    • created_atstring
    • created_byActorSummary
    • idConnectionId (string · uuid)
    • inheritedboolean
    • nameProviderConnectionName (string)
    • provider_idProviderId (string)
    • scope_idstring
    • scope_typeScopeTypegrouprepository
    • secret_refsobjectThe names of the stored credential fields, each with a reference to where it is stored. Never the values. Empty for an oidc_federation connection.
    • source_scope_idstring
    • source_scope_typeScopeTypegrouprepository
    • config_overridesobjectoptional
    • federation_targetOidcFederationTarget or nulloptionalThe cloud role the connection assumes. Present only when auth_mode is oidc_federation.
      • The OidcFederationTarget schema
      • cloudaws
      • role_arnRoleArn (string)The IAM role the pipeline assumes.
      • audiencestring or nulloptionalThe audience of the identity token. Defaults to sts.amazonaws.com.
      • regionAwsRegion (string) or nulloptionalThe AWS region for the provider's calls.
    • last_rotated_atstring or nulloptional
200 exampleSynthesized example
{
"items": [
{
"auth_mode": "static_credentials",
"created_at": "2026-10-10T03:47:24Z",
"created_by": {
"email": "tomas@acme.example",
"id": "id-ea5d",
"username": "tomas"
},
"id": "74e25cbb-9be0-406e-a7b7-94a70a45ebdc",
"inherited": false,
"name": "payments-api",
"provider_id": "5070f565-a219-4cdb-baf6-40476e18d7f3",
"scope_id": "ffee7b08-633c-433e-89b5-cd73ff0a7f09",
"scope_type": "group",
"secret_refs": {
"secret_refs": "secret-refs-bf20"
},
"source_scope_id": "c50840ab-02f5-484d-93e7-b1e253e385dc",
"source_scope_type": "group"
}
]
}
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-0b88",
"message": "Pin a page's payload to the build that rendered it"
}
}
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-d8ae",
"message": "Stream pipeline status into the run header"
}
}
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-edd9",
"message": "Stream pipeline status into the run header"
}
}
404application/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-d0e9",
"message": "Stream pipeline status into the run header"
}
}

CLI

gitmoap provider-connections resolve-repo-connections

  • --repo-ididRepository id (id or owner/repo path)

Used in these guides