Create a batch job
/lang2fhir/batchOpens an empty batch job. Items arrive on later upload calls and the set is sealed at finalize.
Supplying request_id makes the create idempotent on that token: a
retried submit whose response was lost returns the original job rather
than opening a second one. This dedupe is scoped to the calling
credential.
An instance may hold at most 4 active (pending or processing) jobs at
once; a create past that limit returns 409. The limit is instance-wide
— jobs are shared across the instance's credentials — so another
credential's jobs count against it.
Body parameters
request_idstringoptionalOptional client idempotency token. A retried create with the same token returns the original job instead of opening a second one.
Batch job created (or an idempotent replay of an existing job)
Response fields
job_idstringrequiredServer-assigned job identifier.
request_idstringoptionalThe idempotency token supplied at create, if any.
statusstringrequiredJob status. completed means every item has finished — some may have
failed, so check counts for the split. failed is a whole-job
failure (the job could not run at all), distinct from individual item
failures, which never fail the job.
pendingprocessingcompletedfailedfinalizedbooleanrequiredWhether the job's item set has been sealed.
total_itemsintegerrequiredThe sealed item count. It is 0 until the job is finalized, so an upload response always reports 0; poll the job after finalize for the real count.
errorobjectoptionalA whole-job failure. Present only on a failed job.
created_atstring (date-time)requiredupdated_atstring (date-time)requiredcompleted_atstring (date-time)optionalWhen the job finished. Absent until then.
expires_atstring (date-time)requiredWhen the job and its stored inputs and results are deleted. Set 7
days out, with the clock restarting when the job reaches completed
or failed. At expiry the job's request_id is freed for reuse.