Process batch document update
Processes a batch update for multiple document families in a single request. Supports uploading binary files, applying labels, updating notes, and deleting documents. Use multipart/form-data for file uploads or application/json for metadata-only updates.
Task status in the response
Send the task’s status asstatusSlug on the task object. The task echoed back in the response carries it under the same name, matching the Task model everywhere else in the API, so a client can apply the returned task directly to its local copy.
Completing a task with a discarded save
When the batch moves the task to a status of typeDONE, the platform first checks the task’s documents. If the most recent saved changes for one of them were discarded server-side and never redone, the request is refused with 409 Conflict and no part of the batch is applied — the status change, the queued document uploads, the label changes and the deletes are all rolled back together.
The message names the affected documents by path (or by ID when a document has no path):
409 Conflict for a stale changeSequence on the task; the two cases share the CONFLICT code and are distinguished by the message.Authorizations
API key for authentication. Create one from the Kodexa platform UI under Settings > Access Tokens.
Body
A batch update request containing multiple document operations to be processed atomically.
Content object file uploads to add to document families.
Document families to delete.
IDs of document families to include in the batch.
Label additions and removals.
ID of the project containing the document families.
Optional task data to associate with the batch update.
Optional client-supplied work-session context. The UI captures startedAt when the user opens a task and sends it back on save so the server can record how long the user spent on this work for time-allocation analytics.
