The RFID Operations API provides pre-flight validation for RFID-gated warehouse operations. Before committing a receipt, shipment, or transfer action, handheld devices call these endpoints to verify that the scanned EPC set is correct against the document’s expected set, enforcing the tenant’s configured RFID policy.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/CodexaCP/DG_BACK/llms.txt
Use this file to discover all available pages before exploring further.
POST /api/rfid/validate-operation
Performs a pre-flight validation of a single RFID scan against a warehouse operation. Checks whether the EPC resolves to a known tag, whether it belongs to the expected document, and whether any mismatch should block the operation based on the tenant’s RFID policy. Authentication:Authorization: Bearer <token> (required).
Raw EPC string from the hardware reader.
Pre-normalized EPC. Used instead of
rawEpc if provided.WMS module context (e.g.,
RECEIVING, SHIPMENT, INVENTORY_COUNT, TRANSFER).Specific operation type within the module (e.g.,
SCAN_IN, SCAN_OUT).Document type being processed (e.g.,
RECEIPT, SHIPMENT).Document number to validate the EPC against.
Current warehouse location code.
Current bin code.
Whether the validation call itself completed without errors.
Whether the EPC was found in the tag registry.
Whether the EPC passes the document validation rules.
Whether the RFID policy requires blocking the operation on this result. When
true, the handheld must not allow the user to proceed without manual override.Module as echoed from the request.
Human-readable validation outcome message.
Resolved
RfidTagDto if the EPC was found in the registry.Active policy settings applied during validation.
| Status | Meaning |
|---|---|
| 400 | Invalid request payload or business rule violation. |
POST /api/rfid/validate-batch
Validates up to 100 EPCs in a single request. Each item in the batch is validated independently using the same operation context. Returns an aggregated summary plus per-EPC results. Authentication:Authorization: Bearer <token> (required).
Array of validation request objects (same schema as
POST /api/rfid/validate-operation). Minimum 1 item, maximum 100 items.Total number of EPCs in the batch.
Number of EPCs that passed validation.
Number of EPCs that failed validation.
Number of EPCs where
shouldBlock is true.Convenience flag —
true if at least one EPC is blocking.Per-EPC validation results.
| Status | Meaning |
|---|---|
| 400 | Empty items array, or batch size exceeds 100. |