Skip to main content

Get CSV import status

Check progress and the result of a queued CSV import.

GET /projects/:projectid/databases/:dbid/tables/:tblid/import-csv/:importId

Authentication​

Send the project API key in the Authorization header, without a Bearer prefix. Requires databases.read for the database in the URL.

Request​

Set INTELLECTIBLE_IMPORT_ID to the importId returned by Import a CSV. Use the same project, database, and table path as the original request. No request body.

Example​

Use the environment variables from the database overview. Replace example IDs with your own.

curl --include --request GET \
--header "Authorization: ${INTELLECTIBLE_PROJECT_API_KEY}" \
"${INTELLECTIBLE_PUBLIC_API_URL}/projects/${INTELLECTIBLE_PROJECT_ID}/databases/${INTELLECTIBLE_DATABASE_ID}/tables/${INTELLECTIBLE_TABLE_ID}/import-csv/${INTELLECTIBLE_IMPORT_ID}"

Response​

200 OK

{
"importId": "import_id",
"status": "importing",
"message": "Importing CSV...",
"progress": 45,
"error": null,
"rowsCommitted": 10000,
"updatedAt": 1793318400000
}
FieldDescription
importIdImport identifier.
statusqueued, importing, complete, or failed.
messageHuman-readable progress message, or null.
progressProgress percentage when available, otherwise null.
errorError detail when available, otherwise null.
rowsCommittedNumber of rows reported committed so far, or null when unavailable.
updatedAtStatus timestamp in Unix milliseconds.

Poll with a delay between requests and stop on complete or failed. Use status, not the progress percentage, to decide whether the import succeeded. queued can also be reported during preparation or finalisation; it is not necessarily the first state only.

An HTTP 200 means the status was retrieved successfully, not that the import succeeded. A failed import may have already committed rows. Do not automatically submit it again: inspect the error, committed count, and destination data first.

See Errors and safe retries for shared failure handling.