Processing Configs
Discover the named processing configurations available to your workspace with GET /v1/configs, including credit cost and pipeline steps for each one.
Processing configurations are the named pipelines the POST /v1/process endpoint runs documents through. The GET /v1/configs endpoint lists every configuration available to your organization so you can discover the config_id values to submit against, and GET /v1/configs/:id reads a single configuration to inspect its settings.
Each configuration reports its credit_cost and the pipeline steps it executes (for example extract, structure, reconcile), so you can predict spend and understand what a run will produce before submitting documents.
GET
/v1/configsGET
/v1/configs/:idPath parameters
id*stringThe configuration id.
curl
Response
Config fields
config_idstringThe identifier you pass to POST /v1/process.
namestringHuman-readable configuration name.
descriptionstringWhat the configuration does.
credit_costintegerCredits charged per run through this configuration.
stepsstring[]Pipeline steps the configuration executes (e.g. extract, structure, reconcile).
Response
{
"data": [
{
"config_id": "cfg_bridgeway_invoice_v1",
"name": "Bridgeway Invoices",
"description": "Extract, structure, and reconcile inbound invoices.",
"credit_cost": 12,
"steps": ["extract", "structure", "reconcile"]
}
]
}Errors
Error responses
401unauthorizedMissing or invalid API key.
404not_foundGET /v1/configs/:id only: no configuration with this id exists.