Batch scan multiple panes
QR Scanning
Batch scan panes
Batch scan_in, start, or complete for multiple panes — application rollback, no MongoDB replica set required.
POST
Batch scan multiple panes
How batch scan works
- Same actions as single-pane scan (subset):
scan_in,start, andcompleteonly. Behavior for each pane matches Scan a pane for those actions (station, status,startedAt, optional material backfill from the order,PaneLogrows, WebSocket events after success). - Processing order: Panes are updated in the order they appear in
paneNumbers. Only numbers that exist in the database are included; duplicates and unknown IDs are skipped. If no pane numbers resolve to documents, the API returns 400. - All-or-nothing (application rollback): The endpoint does not use MongoDB multi-document transactions. If validation fails partway through (e.g. one pane is already
completed,merged_into, or wrong station forcomplete), the server restores earlier panes from a snapshot and deletesPaneLogdocuments created in that request. That works on standalone MongoDB as well as replica sets.
scan_out, qc_pass, qc_fail, and laminate are not supported here. Use Scan a pane for each pane when you need handoff, QC, or laminate merge. merged_into panes are rejected in batch operations.Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
application/json
Array of pane numbers to scan (e.g. ["PNE-0001", "PNE-0002"])
Minimum array length:
1Minimum string length:
1Station ObjectId where the scan is performed
Minimum string length:
1Action to perform on all panes
Available options:
scan_in, start, complete