Signals & Catalog
The catalog API (/v1/delivery/catalog/*) exposes the four registries that drive the binding picker. Use it to populate dropdowns rather than hardcoding lists — it always reflects the running registry contents.
Core signal types
| Parameter | Type | Description |
|---|---|---|
| document.extracted | signal | Fired when a document completes extraction with structured fields. |
| document.extraction_failed | signal | Fired when extraction fails terminally. |
| run.dataspace.completed | signal | Fired when a dataspace job run completes. |
| run.structuring.completed | signal | Fired when a structuring run completes. |
| run.resolution.completed | signal | Fired when a resolution run (field normalization + transforms) completes. |
| run.extraction.completed | signal | Fired when a multi-document extraction (batch-inference) run completes. |
| result.approved | signal | Fired when a reviewer approves a record. |
| result.rejected | signal | Fired when a reviewer rejects a record. |
| result.flagged | signal | Fired when validation flags fire on a record. |
| delivery.item.completed | meta | Fired after a successful delivery. Meta-signal — the poller prevents re-binding loops. |
| delivery.item.failed | meta | Fired after a terminal delivery failure. |