Dragon Guard is a .NET 8 ASP.NET Core Web API that powers warehouse operations for handheld scanners and back-office systems. It handles the full WMS lifecycle — item catalog management, receiving, shipments, inventory movements, RFID tag tracking, and bidirectional ERP integration — across isolated multi-tenant companies.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.
Quickstart
Authenticate and make your first API call in minutes
API Reference
Complete endpoint documentation with request and response schemas
ERP Integration
Connect GrupoMAS Native or Business Central to Dragon Guard
RFID
Tag lifecycle, scan events, policies, and device profiles
What Dragon Guard does
Dragon Guard sits between your ERP system and warehouse floor, providing:- Handheld-optimized endpoints — lean JSON contracts designed for Android WMS apps with paginated product lookup, bin stock queries, and barcode/RFID fallback support
- Multi-tenant isolation — every company’s data, devices, and users are fully isolated; a single deployment can serve multiple warehouse tenants
- ERP connectors — native adapters for GrupoMAS and Microsoft Business Central; released-work polling and outbound acknowledgment queuing ensure reliable ERP synchronization
- RFID lifecycle — commission tags, resolve EPCs to item context, apply per-module operation policies, and record scan audit events
- Supreme admin surface — a
SUPERADMIN_SUPREMOtier manages plans, tenant onboarding, device authorization, and RFID configuration without touching operational data
Key sections
Authentication
JWT login, handheld delegated auth, and token claims
Core Modules
Items, stock, receiving, shipments, and movements
Supreme Admin
Tenant management, plans, and global oversight
Platform
Multitenancy model, audit logging, and pagination
Configuration
JWT, database, and integration settings
Outbound Queue
Durable retry and ERP posting acknowledgments
Get started in 3 steps
Configure the API
Set
Jwt:Key, Jwt:Issuer, Jwt:Audience, and your SQL Server connection string in appsettings.json. The API auto-migrates the database on startup.Obtain a JWT token
Call
POST /api/auth/login with your email and password. The response includes a token you pass as Authorization: Bearer <token> on every subsequent request.Handheld devices authenticate differently — see Handheld Login for the delegated GrupoMAS flow and device authorization model.