Skip to content
GitmoapAPIBeta
Buildpipeline-components
GET/repositories/{repo_id}/pipeline-components/{component_id}

Read one component, its draft body and its published versions

get_repo_pipeline_component
  • 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

Returns the component with its draft body, advisory diagnostics for that draft, and every version it has published, newest first. A component can be read from the scope that owns it and from any scope beneath it; anywhere else it is not found. Anyone who can read the pipelines here may call it.

Parameters

Path
  • repo_idRepositoryId (string · uuid)The repository's id
  • component_idComponentId (string · uuid)The component's id

Responses

200The component, its draft body and every version it has published, newest firstapplication/json
  • bodyComponentBodyThe draft: what the next published version will contain.
    • The ComponentBody schema
    • component_instancesarray of NestedComponentInstanceoptionalOther components this component uses. Always empty in a published version, where they have already been expanded into steps.
      • The NestedComponentInstance schema
      • component_idComponentId (string · uuid)
      • idNodeId (string)
      • namestring
      • versionComponentVersionRef (string)
      • component_refstring or nulloptional
      • paramsobjectoptional
      • stage_mapobjectoptionalBinds every slot the referenced component declares to a slot of the containing body.
    • edgesarray of EdgeoptionalConnections between the component's own steps; both ends must be steps of this component.
      • The Edge schema
      • idEdgeId (string)
      • source_node_idNodeId (string)
      • target_node_idNodeId (string)
      • source_portPortName (string) or nulloptionalAbsent on a dependency-only edge.
      • target_portPortName (string) or nulloptionalAbsent on a dependency-only edge.
    • inputsarray of ComponentInputPortoptional
    • nodesarray of ComponentNodeoptional
      • The ComponentNode schema
      • nodeNode
      • stage_slotStageSlot (string)Which of the component's stage slots this step is placed in.
      • param_slotsComponentNodeParamsoptionalStep fields whose values come from the component's parameters rather than from the step.
    • outputsarray of ComponentOutputPortoptional
    • parametersarray of ComponentParameteroptional
      • The ComponentParameter schema
      • nameComponentParamName (string)
      • param_typeComponentParamTypestringnumberbooleanobjectarrayThe JSON shape a parameter's value must have.
      • allowed_valuesarray of object or nulloptionalThe only values this parameter accepts. Absent means any value of its type. On a published parameter, adding this list or removing a value from it is a major version change; adding a value is a minor one.
      • defaultobjectoptional
      • descriptionstring or nulloptional
      • requiredbooleanoptionalWhether a pipeline using the component must supply a value. A required parameter cannot have a default.
    • stage_slotsarray of StageSlot (string)optionalThe positions the component's steps occupy, in order. A pipeline using the component maps each slot to one of its own stages.
  • created_atstring
  • created_byActorSummary
  • idComponentId (string · uuid)
  • nameComponentName (string)
  • updated_atstring
  • version_countinteger · int640–∞
  • descriptionstring or nulloptional
  • diagnosticsValidationSummary or nulloptionalProblems found in the draft. A draft is saved even when it is invalid.
    • The ValidationSummary schema
    • validboolean
    • violationsarray of ValidationViolation
    • warningsarray of ValidationWarningoptionalThings worth knowing that do not make the definition invalid, such as a deprecated component version. A violation stops a published definition from being saved; a warning never does. Left out when there are none.
  • latest_versionComponentVersion (string) or nulloptional
  • versionsarray of ComponentVersionSummaryoptionalPublished versions, newest first. Present on a single-component read.
    • The ComponentVersionSummary schema
    • capability_requirementsarray of CapabilityId (string)The provider capabilities the version's steps use.
    • contract_digeststringA SHA-256 fingerprint, in hex, of what a pipeline using the version must satisfy: its parameters, its ports and the variables it reads. It changes only when that contract does.
    • depthinteger · int320–∞How many levels of components the version spans: 1 when it uses no other component.
    • expanded_node_countinteger · int320–∞How many steps the version expands into.
    • lifecycle_stateComponentLifecycleStateactivedeprecatedsunsetWhere a published version sits in its retirement. A deprecated version still resolves for an exact reference and still runs, but no floating reference selects it — which is what makes deprecating the safe way to retire one. A sunset version refuses to resolve at all, exact reference included.
    • published_atstring
    • published_byActorSummary
    • variable_requirementsarray of EnvironmentVariableName (string)The variables the version's steps read from the pipeline that uses it. Each must be declared on the environment those steps run in, or on a group or repository above the pipeline, or a run is refused when it starts.
    • versionComponentVersion (string)
    • changelogstring or nulloptional
200 exampleSynthesized example
{
"body": {
"component_instances": [
{
"component_id": "cb41c461-67ef-476f-a113-c0851b92a9ef",
"id": "id-7101",
"name": "payments-api",
"version": "version-0c0e"
}
],
"edges": [
{
"id": "id-2830",
"source_node_id": "9f48d05f-f226-4ebf-b450-4b7dd1120ce0",
"target_node_id": "853a62d4-1ddc-40c8-8941-3cf17f3cddf9"
}
],
"inputs": [
{
"name": "payments-api",
"targets": []
},
{
"name": "payments-api",
"targets": []
}
],
"nodes": [
{
"node": {
"capability_id": "3b02f11b-a763-4b45-8058-b2e5cdf1d0ef",
"id": "id-5b9a",
"name": "payments-api"
},
"stage_slot": "stage-slot-d89f"
}
],
"outputs": [
{
"name": "payments-api",
"source": {
"node_id": "8b7c4a42-e991-4486-a1c5-3a70a8d8e7df",
"port": "port-bf1b"
}
},
{
"name": "payments-api",
"source": {
"node_id": "d9ae79a1-520a-4a2e-a248-04defe845aad",
"port": "port-3f6c"
}
}
],
"parameters": [
{
"name": "payments-api",
"param_type": "string"
}
],
"stage_slots": [
"stage-slots-5179"
]
},
"created_at": "2026-10-11T18:13:00Z",
"created_by": {
"email": "mara@acme.example",
"id": "id-fd8e",
"username": "tomas",
"avatar_url": "https://gitmoap.example/acme/efc93bd8"
},
"id": "08782530-6619-45b5-b83c-a438328df0f5",
"name": "payments-api",
"scope": {
"group": "4c1d8e2f-6a3b-4f90-b7c5-1e2d3c4b5a69"
},
"updated_at": "2026-10-11T08:10:02Z",
"version_count": 4,
"description": "Renders each region as density contours of its operations.",
"diagnostics": {
"valid": false,
"violations": [
{
"code": "code-5a1e",
"message": "Stream pipeline status into the run header",
"target": {
"kind": "pipeline"
}
}
],
"warnings": [
{
"code": "code-9fbc",
"message": "Label every synthesized example",
"target": {
"kind": "pipeline"
}
}
]
},
"latest_version": "latest-version-2fb7",
"versions": [
{
"capability_requirements": [],
"contract_digest": "contract-digest-4406",
"depth": 89,
"expanded_node_count": 4,
"lifecycle_state": "active",
"published_at": "2026-10-17T07:25:59Z",
"published_by": {
"email": "mara@acme.example",
"id": "id-be6d",
"username": "lin"
},
"variable_requirements": [],
"version": "version-a158"
}
]
}
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-d9d7",
"message": "Label every synthesized example"
}
}
401Unauthenticated — no credential, or an invalid oneapplication/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-9b9d",
"message": "Draw the region map from operation density"
}
}
403Reporter is required to read componentsapplication/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-c74f",
"message": "Inline scalar newtypes but keep their brand"
}
}
404No such component here — a component belongs to a scope, and only that scope and the scopes beneath it can see itapplication/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-f2c9",
"message": "Inline scalar newtypes but keep their brand"
}
}

CLI

gitmoap pipeline-components get-repo-pipeline-component

  • --repo-ididThe repository's id (id or owner/repo path)
  • --component-ididThe component's id

Used in these guides