Buildpipeline-components
GET/groups/{group_id}/pipeline-components/{component_id}
Read one component, its draft body and its published versions
get_group_pipeline_component
pipeline:read
A token needs thepipeline:readscope: View pipeline runs and definitionsGranted byread_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
- group_idGroupId (string · uuid)The group'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
- The ComponentInputPort schema
- namePortName (string)
- targetsarray of PortRef
- descriptionstring or nulloptional
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
- The ComponentOutputPort schema
- namePortName (string)
- sourcePortRef
- descriptionstring or nulloptional
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
- The ActorSummary schema
- emailstring
- idstring
- usernamestring
- avatar_urlstring or nulloptional
- idComponentId (string · uuid)
- nameComponentName (string)
- scopeScopeRef
- 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
- The ValidationViolation schema
- codestringStable machine-readable code (e.g.
cycle_detected,type_mismatch,required_input_not_wired). - messagestringHuman-readable description.
- targetValidationTarget
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.
- The ValidationWarning schema
- codestringStable machine code — the warning rule's own name, exactly as a violation's is.
- messagestring
- targetValidationTarget
- 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
deprecatedversion 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. Asunsetversion refuses to resolve at all, exact reference included. - published_atstring
published_byActorSummary
- The ActorSummary schema
- emailstring
- idstring
- usernamestring
- avatar_urlstring or nulloptional
- 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": "0c1240e3-09ba-4a7e-af79-258fe07f1b7f",
"id": "id-30cd",
"name": "payments-api",
"version": "version-7ee7"
}
],
"edges": [
{
"id": "id-9d2f",
"source_node_id": "6fe91100-2f33-46aa-84e4-b45e389cd716",
"target_node_id": "a651bd71-ac58-4f61-806a-e4c4120775e4"
}
],
"inputs": [
{
"name": "payments-api",
"targets": []
},
{
"name": "payments-api",
"targets": []
}
],
"nodes": [
{
"node": {
"capability_id": "3e5ba53f-5b96-4d01-bd26-ac59f2b9154d",
"id": "id-b3c8",
"name": "payments-api"
},
"stage_slot": "stage-slot-d036"
}
],
"outputs": [
{
"name": "payments-api",
"source": {
"node_id": "37e0bd3d-2848-43a3-85c1-d60b0acf9600",
"port": "port-3e6a"
}
},
{
"name": "payments-api",
"source": {
"node_id": "f01485cd-44c0-43c4-8fdb-2ae81deee876",
"port": "port-df2e"
}
}
],
"parameters": [
{
"name": "payments-api",
"param_type": "string"
}
],
"stage_slots": [
"stage-slots-ec93",
"stage-slots-6530"
]
},
"created_at": "2026-10-10T21:19:17Z",
"created_by": {
"email": "tomas@acme.example",
"id": "id-18e8",
"username": "tomas",
"avatar_url": "https://gitmoap.example/acme/6656f0ac"
},
"id": "da4747ac-4bd0-4b32-badb-78875e23dada",
"name": "payments-api",
"scope": {
"group": "4c1d8e2f-6a3b-4f90-b7c5-1e2d3c4b5a69"
},
"updated_at": "2026-10-11T19:00:13Z",
"version_count": 2,
"description": "Renders each region as density contours of its operations.",
"diagnostics": {
"valid": false,
"violations": [
{
"code": "code-4ef4",
"message": "Stream pipeline status into the run header",
"target": {
"kind": "pipeline"
}
}
],
"warnings": [
{
"code": "code-2d14",
"message": "Pin a page's payload to the build that rendered it",
"target": {
"kind": "pipeline"
}
},
{
"code": "code-b22a",
"message": "Draw the region map from operation density",
"target": {
"kind": "pipeline"
}
}
]
},
"latest_version": "latest-version-567c",
"versions": [
{
"capability_requirements": [],
"contract_digest": "contract-digest-1b13",
"depth": 17,
"expanded_node_count": 0,
"lifecycle_state": "active",
"published_at": "2026-10-12T10:08:08Z",
"published_by": {
"email": "mara@acme.example",
"id": "id-6de1",
"username": "mara"
},
"variable_requirements": [],
"version": "version-555a"
},
{
"capability_requirements": [],
"contract_digest": "contract-digest-434f",
"depth": 28,
"expanded_node_count": 6,
"lifecycle_state": "active",
"published_at": "2026-10-10T12:15:25Z",
"published_by": {
"email": "lin@acme.example",
"id": "id-6fab",
"username": "tomas"
},
"variable_requirements": [],
"version": "version-e9b9"
}
]
}
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
reasonorcode. - fieldstring or nulloptionalOn a
400that 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 oncodeotherwise. - required_scopestring or nulloptionalThe scope the access token was missing, on
INSUFFICIENT_SCOPE. - violationsanyoptionalPresent on the structured-validation errors (
PROVIDER_VALIDATION_FAILEDper-node,PIPELINE_VALIDATION_FAILEDDAG): 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-528b",
"message": "Draw the region map from operation density"
}
}
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
reasonorcode. - fieldstring or nulloptionalOn a
400that 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 oncodeotherwise. - required_scopestring or nulloptionalThe scope the access token was missing, on
INSUFFICIENT_SCOPE. - violationsanyoptionalPresent on the structured-validation errors (
PROVIDER_VALIDATION_FAILEDper-node,PIPELINE_VALIDATION_FAILEDDAG): 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-ab3b",
"message": "Inline scalar newtypes but keep their brand"
}
}
403Reporter is required to read componentsapplication/json
Error codes
- FORBIDDENYou are signed in but may not do this here;
reasonnames the permission or the rule that refused it - INSUFFICIENT_SCOPEThe access token lacks the scope this operation needs;
required_scopenames 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
reasonorcode. - fieldstring or nulloptionalOn a
400that 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 oncodeotherwise. - required_scopestring or nulloptionalThe scope the access token was missing, on
INSUFFICIENT_SCOPE. - violationsanyoptionalPresent on the structured-validation errors (
PROVIDER_VALIDATION_FAILEDper-node,PIPELINE_VALIDATION_FAILEDDAG): 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-19a3",
"message": "Stream pipeline status into the run header"
}
}
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
reasonorcode. - fieldstring or nulloptionalOn a
400that 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 oncodeotherwise. - required_scopestring or nulloptionalThe scope the access token was missing, on
INSUFFICIENT_SCOPE. - violationsanyoptionalPresent on the structured-validation errors (
PROVIDER_VALIDATION_FAILEDper-node,PIPELINE_VALIDATION_FAILEDDAG): 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-b20c",
"message": "Label every synthesized example"
}
}
CLI
gitmoap pipeline-components get-group-pipeline-component
- --group-ididThe group's id (id or group path)
- --component-ididThe component's id