The RFID Events API is the scan-audit layer of Dragon Guard. Every time a handheld device reads an EPC, a scan event record is created viaDocumentation 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/events. The event stores resolution state, validation outcome, document context, and operator metadata. The API also exposes a handheld runtime context endpoint used by handhelds to load their RFID operational policy and device profile at startup.
POST /api/rfid/events
Records a new RFID scan event. Called by handheld devices after each EPC scan to log the result, trigger tag resolution, and enforce configured validation policies. Authentication:Authorization: Bearer <token> (required).
Raw EPC string as read from the RFID reader hardware.
Pre-normalized EPC. If omitted, the server normalizes
rawEpc.How the EPC was captured (e.g.,
HANDHELD, FIXED_READER, MANUAL_ENTRY).WMS module that triggered the scan (e.g.,
RECEIVING, SHIPMENT, INVENTORY_COUNT, TRANSFER).Type of scan event (e.g.,
SCAN_IN, SCAN_OUT, VALIDATION).Document type this scan is associated with (e.g.,
RECEIPT, SHIPMENT).Document number this scan is associated with.
Line number within the associated document.
Location code at time of scan.
Bin code at time of scan.
Quantity decoded from or associated with the tag.
Normalized device key of the scanning device.
Email of the operator performing the scan.
Correlation ID for grouping related events in a single session.
Session ID grouping all events in a single document scan session.
Timestamp of the physical scan. Defaults to server time if omitted.
Tag resolution outcome (e.g.,
RESOLVED, UNRESOLVED, AMBIGUOUS).Validation outcome (e.g.,
VALID, INVALID, WARN).Error message if validation or resolution failed.
Optional JSON string for additional metadata.
201 Created with the full RfidScanEventDto.
Error codes
| Status | Meaning |
|---|---|
| 400 | Invalid payload or business rule violation. |
GET /api/rfid/events
Returns a paginated, filterable list of RFID scan events for the authenticated company. Supports filtering by module, resolution/validation status, document, date range, and free-text search. Authentication:Authorization: Bearer <token> (required).
Filter by WMS module (e.g.,
RECEIVING, SHIPMENT).Filter by tag resolution status.
Filter by validation status.
Free-text search.
Filter by document type.
Filter by document number.
Filter by correlation ID.
Filter by session ID.
Start of scan date range.
End of scan date range.
When
true, returns only events with errors.Page number. Defaults to
1.Page size. Defaults to
20.Current page.
Total matching events.
GET /api/rfid/events/export
Exports RFID scan events matching the current filter as an Excel workbook. Accepts the same query parameters asGET /api/rfid/events.
Authentication: Authorization: Bearer <token> (required).
Returns application/vnd.openxmlformats-officedocument.spreadsheetml.sheet with a timestamped filename.
GET /api/rfid/handheld/context
Returns the combined RFID runtime context for the calling handheld — both the active policy (validation rules, block-on-mismatch settings, fallback behavior) and the effective device profile. Used at app startup to configure RFID behavior without separate round trips. The device ID is read from theX-Device-Id header or from the deviceId claim in the JWT.
Authentication: Authorization: Bearer <token> (required — must be a handheld JWT).
WMS module the handheld is loading (e.g.,
RECEIVING, SHIPMENT). Used to select module-specific policy overrides.Hardware device identifier. Falls back to the
deviceId claim in the JWT if not provided.Whether the context was resolved successfully.
Module for which context was resolved.
Resolved device identifier.
Whether the device is registered and authorized.
Whether an RFID device profile was found for this device.
Whether the device profile supports RFID scanning.
Whether the device profile supports barcode scanning.
Whether RFID is enabled for the requested module.
Whether RFID scanning is fully available for this device and module.
Whether the policy allows manual fallback when RFID fails.
Whether the policy allows barcode fallback.
Whether the device can proceed without RFID capability.
Hardware status code (
READY, NO_RFID_PROFILE, RFID_NOT_SUPPORTED, RFID_DISABLED_BY_POLICY, DEVICE_NOT_AUTHORIZED).How the device profile was resolved.
How the policy was resolved.
Effective RFID mode for this module.
Human-readable status message.
Full resolved RFID policy object.
Full effective device profile object.
| Status | Meaning |
|---|---|
| 400 | DeviceId is missing from both the header and the JWT claims. |