Table Execution
Run Enrichment
Initiate a table run, optionally for a selected range of rows and/or columns.
POST
Run Table
Overview
This endpoint starts or reruns table execution after rows and columns are ready. It can run the whole table, rerun failures, or scope execution to specific rows or columns.Example request
Key parameters
table_id(required): target table identifier.mode(optional): run mode. Allowed values:new(default),all,failed.rows(optional): row IDs to scope the run.columns(optional): column IDs to scope the run.
mode:
new: run cells that do not already have valuesall: rerun every eligible cell in scopefailed: rerun only failed cells
rows when you want to rerun only a subset of table rows.
Use columns when you want to run only specific columns instead of the full schema.
When you add new columns to an existing table, the usual pattern is mode: "new" with the new column IDs in columns.
Success signal
A successful response returns run metadata (id, status, num_requested_cells). Use GET /v1/tables/{table_id} to track run_status and in-progress counters.
Common errors
401 Unauthorized
Check that your header is Authorization: Bearer ${EXTRUCT_API_TOKEN}.
404 Not Found
The table ID is invalid or unavailable in your workspace.
422 Unprocessable Entity
Most often caused by invalid mode, malformed JSON, or invalid row/column IDs.
Related endpoints
Related guides
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Body
application/json
Response
Successful Response
Run Table