talonic_list_specs
List the workspace's Specs — the configured pipelines an agent can run with talonic_run_spec. Each row carries the Spec id, name, the schema_id it materializes onto (a different id from the Spec's own), the published version and materialized_version (null when never published), field_count, node_count and timestamps.
When to use
- You need a
spec_idto run the customer's pipeline. - The user refers to 'our invoice pipeline' and you must find it.
- You want to see which Specs are published (
versionnon-null) before running.
When not to use
- You want ad-hoc extraction schemas — use
talonic_list_schemas. - You want to discover fields — use
talonic_list_fields/talonic_find_data.
Parameters
| Parameter | Type | Description |
|---|---|---|
| search | string | Case-insensitive contains match on the Spec name. |
| limit | number | Page size (default 20, max 100). |
| cursor | string | Opaque cursor from `pagination.next_cursor`. |
| order | string | `asc` or `desc`, sorted by `updated_at` (default desc). |
Response shape
Fields
| Parameter | Type | Description |
|---|---|---|
| data[].id | string | Spec UUID. |
| data[].name | string | Spec name. |
| data[].schema_id | string | The schema this Spec materializes onto — a different id from the Spec's own. |
| data[].version | number|null | Published version number, or null if never published. |
| data[].materialized_version | number|null | Version currently materialized onto the schema, or null. |
| data[].field_count | number | Number of fields in the Spec. |
| data[].node_count | number | Number of nodes in the authored rail. |
| pagination.next_cursor | string|null | Cursor for the next page, or null when there isn't one. |
Frequently asked questions
Why does a Spec have both an id and a schema_id?+
The Spec is the authoring document; running it materializes onto a schema, which has its own id. `talonic_run_spec` takes the Spec id.