Bulk API

Bulk endpoints apply the same operation to N DLUs (or N authority candidates) in one call. Default contract is partial success: the response reports per-id outcomes, and a single failure does not abort the rest. Use for curator sweeps where individual rollback is acceptable.

Method	Path	Summary	Key params	Response
POST	/authority/{kind}/bulk-promote	Batch-promote per-DLU mentions to authority records	kind (path:string) body: AuthorityBulkPromoteRequest	BulkResult
POST	/dlus/bulk-confirm-entities	Flip pending-review entities to confirmed across N DLUs	body: BulkConfirmEntitiesRequest	BulkResult
POST	/dlus/bulk-delete	Soft-delete N DLUs	body: BulkDeleteRequest	BulkResult
POST	/dlus/bulk-fuse	Merge variant surface forms into one canonical across N DLUs	body: BulkFuseRequest	BulkResult
POST	/dlus/bulk-update	Apply the same patch to N DLUs	body: BulkUpdateRequest	BulkResult

Examples

Bulk confirm entities across many DLUs

curl -X POST -H "X-API-Key: $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"ids": ["dlu-1","dlu-2"], "entity_ids": ["p:42"]}' \
  "$ARCHAIC/dlus/bulk-confirm-entities"

See also

• /docs/concepts/document-logical-units/

Anchored writes

The no-anchor-no-entry rule applies to every write that asserts an entity, event, or relationship: each row must carry at least one (page, line) mention with a confidence score, or the engine drops it at write time. Bulk endpoints surface dropped rows in their per-id response so callers can inspect.