Get an import run's status
Poll an import’s progress. rows_created and rows_updated climb while it runs; status reaches succeeded or failed and stays there.
rows_skipped counts records the provider returned without the identifier rows are matched on — they cannot be stored without one.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Response
Successful Response
One import run's progress and outcome.
Whether this run asked the provider for everything.
Records returned without the source's identity field, and so dropped.
Where one import run has got to.
The terminal states are absorbing: a run never leaves them. There is no PENDING here — unlike a CSV upload, which sits parsed and uncommitted until the user says go, a source run is only ever created at the moment something decides to run it.
CANCELLING is a request, not an outcome. Stopping an import is a database status flip the workflow observes between pages, never a Temporal terminate: a terminate could land mid-page and leave rows half-written with nothing to settle the run, which is exactly the stuck state that blocks every future refresh of the table.
running, cancelling, cancelled, succeeded, failed What asked for a run.
initial, manual, scheduled Classified cause of the failure: unauthorized, rate_limited, server_unavailable, network_error, not_found, pagination_error, bad_request. NULL when the run did not fail.
Whether fixing this means reconnecting the integration. Only true for a credentials failure, so the prompt keeps its meaning.