Eligible Pipelines
List the pipelines whose Spec compares orders with a filed declaration reference table, newest first, to choose the pipeline_id the other customs routes take.
GET /v1/customs-declaration/pipelines returns the pipelines of the workspace that the customs comparison can run on, newest first. A pipeline qualifies through its Spec: the Spec has a validation stage whose ground-truth comparison is enabled and names a reference table. The id of a pipeline from this list is what pipeline_id names on the declarations and issues routes.
Each entry identifies the pipeline (id, name, status, created_at) and the stage that supplies the comparison: stage_id and stage_name of the validation stage, and reference_data_id and reference_name of the reference table holding the filed declarations. reference_name is null when the table is no longer found. The route takes no parameters and returns { "data": [...] }.
status is the pipeline's own status string. When the other routes are called without pipeline_id, they choose the newest pipeline in this list whose status is completed, and the newest one when none has completed, so reading this list first is how a client sees which pipeline an omitted pipeline_id will select.
/v1/customs-declaration/pipelinesResponse fields (data[])
cURL: List eligible pipelines
curl "https://api.talonic.com/v1/customs-declaration/pipelines" \
-H "Authorization: Bearer $TALONIC_API_KEY"Response: Eligible pipelines
{
"data": [
{
"id": "9c4e7a12-6d03-4b58-b1f7-3e8a0d5c2f46",
"name": "October consignments",
"status": "completed",
"created_at": "2026-10-19T07:42:11.000Z",
"stage_id": "4a1d8e60-2c97-4f35-a0b6-e7d3c9f15b82",
"stage_name": "Compare with filed declarations",
"reference_data_id": "d5b02c7e-18a4-4e69-93f1-6a0e4c8b7d25",
"reference_name": "Filed declarations"
}
]
}data list means no Spec in the workspace has a validation stage that compares with a reference table. Add one to the Spec the customs pipeline runs, and the pipeline appears here once it exists.