Get an import run
Fetch the status and progress counters of an import run. Runs move through queued → running → completed or failed. Rows are processed in chunks; processed_rows, created_count, updated_count, skipped_count, and error_count update as chunks complete, so you can poll this endpoint for live progress.
Authorizations
Workspace API key, e.g. Authorization: Bearer tented_.... Create keys in Workspace Settings → API Keys.
Path Parameters
Import run ID from the execute response.
Response
Import run status and counters.
An import run: status, chunked-processing progress, and per-outcome row counts.
Import run ID.
The import session the run was created from.
Run state. queued → running → completed or failed.
queued, running, completed, failed Who started the run. tented-api for runs started via this API.
How rows matching existing contacts were handled.
update, skip Whether imported values only filled empty fields on matched contacts.
Static list IDs imported contacts were added to.
Total data rows in the source file, or null before preprocessing has counted them.
Number of processing chunks the file was split into (rows are processed in chunks of up to 1,000).
Chunks processed successfully so far.
Chunks that failed.
Data rows processed so far — compare against total_rows for progress.
Highest row number processed so far.
Rows that created a new contact.
Rows that updated an existing contact.
Rows skipped (e.g. duplicates under duplicate_strategy: "skip", or rows with no usable identity).
Rows that failed with an error.
When processing started, or null while queued.
When the run completed, or null.
When the run failed, or null.
Failure reason when status is failed.
Custom fields created during this import's setup.
Creation time.
Last update.
File name associated with the import session.