Skip to main content
POST
Move a document to a different batch
Re-files the document into a batch you can edit, then re-extracts. Always billable, attributed to the mover. Same-schema moves keep cell overrides; a different schema clears them. 409 if the document is still processing. 400 if the destination is a schema-builder test batch. 409 if the destination is canceled.

Authorizations

Authorization
string
header
required

Organisation API key from Settings → API / /api/keys/. The secret is shown once. Send Authorization: Bearer sk-abacus-…. One active key per organisation. Ingest (/api/v2/ingest/*) refuses API keys — that surface is Auth0-only with ingest:read / ingest:write scopes.

Path Parameters

att_id
integer
required

Body

application/json

Body for POST /attachments/<att_id>/move-batch/.

target_batch_id: the batch to move the document into. Must be a batch the caller can edit (403 otherwise) that isn't a schema-test or cancelled batch (400/409). Moving to the document's current batch is an accepted no-op.

target_batch_id
integer
required

Response

Response for the move-batch POST — mirrors batch_moves.MoveResult.

code
string
required
moved
boolean
required
source_batch_id
integer | null
required
target_batch_id
integer | null
required
cleared_overrides
boolean
required
purged_lynx_document_id
string | null
required