/v1/definitions/{key}/import/jobsImport rows as a job
Starts the same import as post_definitions_key_import but as a JOB: it writes the run and answers 202 running with nothing landed yet — the rows land on the reads of the job. Reach for it over the plain import when the file is large enough that somebody is watching, or when a retry has to be safe — send the same idempotencyKey and a second call answers the SAME job instead of landing the file twice. Same body: rows already keyed by column, columns to ensure by label, identity to merge onto records that already exist, unknownChoice (add | blank | reject), duplicates (first | last | all). Still at most 5000 rows, refused whole with too_many_rows above it. Then read get_definitions_key_import_jobs_jobId straight away and again while it moves — each read lands chunks — until state is completed or failed; the whole job is one batch, so post_definitions_key_imports_runId_undo rolls all of it back.
Access class: def:read.
Send request
Use the documented inputs to call this endpoint directly.
Parameters
Values are applied to the request and the example on the right.
Request body
application/jsonrequiredResponses
the action's answer
{
"data": {
"actorUserId": 1.5,
"blankedCells": [
"string"
],
"created": 1.5,
"done": 1.5,
"error": "string",
"errors": [
"string"
],
"failed": 1.5,
"fileName": "string",
"finishedAt": "2026-01-01T00:00:00Z",
"id": "",
"imported": 1.5,
"optionsAdded": [
"string"
],
"startedAt": "2026-01-01T00:00:00Z",
"state": "string",
"total": 1.5,
"updated": 1.5
}
}a refusal: {"error": "<what a person needs to read>"}. 401 no credential, 402 the plan does not include this, 403 the seat does not, 404 the thing does not exist or is not yours to see.
{
"error": "string"
}