The Integration API (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.
/api/integration or /api/v1/integration) is the machine-to-machine interface for external ERP systems to push data into Dragon Guard. All endpoints authenticate via the X-Api-Key header (not Bearer JWT). The API key is provisioned per tenant by a Supreme admin and can be rotated at any time. Capabilities vary by tenant integrationMode.
All Integration API endpoints accept both
/api/integration/... and /api/v1/integration/... path prefixes — both are equivalent. The X-Api-Key header is required; Bearer JWT is not accepted on these routes.GET /api/v1/integration/capabilities
Returns the capabilities of the API key’s tenant. Use this endpoint to discover which integration operations are enabled before calling them. Authentication:X-Api-Key: <api-key> (required).
Tenant company code.
Configured integration mode (e.g.,
Standard, GrupoMasNative, BusinessCentralNative).Resolved provider name.
Whether API access is active for this tenant.
Map of capability flags indicating which operations are supported.
GET /api/v1/integration/company
Returns extended company/tenant information for the calling API key. Authentication:X-Api-Key: <api-key> (required).
Tenant company ID.
Company code.
Company display name.
Integration mode.
Resolved provider name.
API access flag.
External ERP system code.
Maximum registered handheld devices.
Same capability flags as
/capabilities.POST /api/v1/integration/items/validate
Dry-runs a single item upsert payload against Dragon Guard validation rules without persisting anything. Returns409 Conflict for ERP-owned tenants where item sync is not supported.
Authentication: X-Api-Key: <api-key> (required).
Item number / SKU.
Item description.
Primary unit of measure.
Base unit of measure.
Item type (e.g.,
Inventory, Service).Active flag. Defaults to
true.Primary barcode.
Category or group code.
Brand name.
Enable lot tracking.
Enable serial tracking.
Enable expiration tracking.
Whether the payload is valid.
Tenant company code.
Request correlation ID.
List of field-level validation errors if any.
POST /api/v1/integration/items
Upserts a single item. Creates the item ifitemNo does not exist, or updates it if it does. Returns the created or updated item entity.
Authentication: X-Api-Key: <api-key> (required).
Accepts the same body as POST /api/v1/integration/items/validate.
Whether the upsert succeeded.
Tenant company code.
Human-readable result message.
Request correlation ID for tracing.
Upserted item entity.
Validation errors if
success is false.POST /api/v1/integration/items/bulk/validate
Dry-runs a bulk item upsert batch without persisting. Returns per-item validation results and error details. Returns409 Conflict for ERP-owned tenants.
Authentication: X-Api-Key: <api-key> (required).
Caller-assigned reference number for the batch.
Optional free-text notes for the batch.
Array of item objects (same schema as single-item validate).
Whether the entire batch passes validation.
Batch summary:
batchReferenceNo, totalItems, createdCount, updatedCount, errorCount.Per-item results with
index, itemNo, action (CREATED/UPDATED), and success.Field-level error list referencing items by index (e.g.,
items[2].itemNo).POST /api/v1/integration/items/bulk
Upserts a batch of items in a single request. Items are created or updated based on matchingitemNo. Returns a batch summary and per-item action results.
Authentication: X-Api-Key: <api-key> (required).
Accepts the same body as POST /api/v1/integration/items/bulk/validate.
Whether the batch completed without errors.
Tenant company code.
Request correlation ID.
Batch summary with counts.
Per-item results (
index, itemNo, action, success).Any errors encountered during processing.
POST /api/v1/integration/stock/opening/validate
Dry-runs an opening stock payload without applying any changes. Returns409 Conflict for ERP-owned tenants where opening stock sync is not supported.
Authentication: X-Api-Key: <api-key> (required).
Caller-assigned reference for this opening stock batch. Used for idempotency.
Posting date for the opening stock movements.
Array of opening stock lines, each with
itemNo, binCode, locationCode, quantity, and uom.Whether the payload is valid.
Field-level errors if any.
POST /api/v1/integration/stock/opening
Applies an opening stock batch, creating inventory movements and updatingCurrentStock. Idempotent when the same referenceNo is used.
Authentication: X-Api-Key: <api-key> (required).
Accepts the same body as POST /api/v1/integration/stock/opening/validate.
Whether the opening stock was applied.
Tenant company code.
Request correlation ID.
Created or existing document record.
Errors if
success is false.POST /api/v1/integration/receipts/validate
Dry-runs a receipt creation payload without persisting. Returns409 Conflict for ERP-owned tenants where receipt import is not supported.
Authentication: X-Api-Key: <api-key> (required).
ERP document number.
Vendor code.
Vendor name.
Destination warehouse location code.
Expected receipt date.
Receipt lines with
itemNo, quantityExpected, and uom.Whether the payload is valid.
Field-level errors if any.
POST /api/v1/integration/receipts
Creates a new receiving header document via the integration API. Returns the created document reference. Authentication:X-Api-Key: <api-key> (required).
Accepts the same body as POST /api/v1/integration/receipts/validate.
Whether the receipt was created.
Tenant company code.
Request correlation ID.
Created document reference with
id, internalDocumentNo, externalDocumentNo, and status.Errors if
success is false.GET /api/v1/integration/receipts/
Returns the current status of a receipt document in Dragon Guard identified by its external document number. Authentication:X-Api-Key: <api-key> (required).
ERP document number used when the receipt was created.
Tenant company code.
External document number.
Internal WMS receipt number.
Current receipt status.
Resolved document status label.
Processing status label.
List of posted receipt document numbers derived from this receipt.
| Status | Meaning |
|---|---|
| 404 | Receipt not found for the given external document number. |
GET /api/v1/integration/receipts//movements
Returns the inventory movements created when a receipt was posted, identified by its external document number. Authentication:X-Api-Key: <api-key> (required).
ERP document number.
Tenant company code.
External document number.
Internal WMS receipt number.
Current receipt status.
Inventory movements created by posting this receipt.
| Status | Meaning |
|---|---|
| 404 | Receipt not found for the given external document number. |
POST /api/v1/integration/shipments/validate
Dry-runs a shipment creation payload without persisting. Returns409 Conflict for ERP-owned tenants.
Authentication: X-Api-Key: <api-key> (required).
ERP document number.
Customer code.
Customer name.
Source warehouse location code.
Planned shipment date.
Shipment lines with
itemNo, orderedQty, and uom.Whether the payload is valid.
Field-level errors if any.
POST /api/v1/integration/shipments
Creates a new shipment header document via the integration API. Authentication:X-Api-Key: <api-key> (required).
Accepts the same body as POST /api/v1/integration/shipments/validate.
Whether the shipment was created.
Tenant company code.
Request correlation ID.
Created document reference with
id, internalDocumentNo, externalDocumentNo, and status.Errors if
success is false.GET /api/v1/integration/shipments/
Returns the current status of a shipment document in Dragon Guard identified by its external document number. Authentication:X-Api-Key: <api-key> (required).
ERP document number used when the shipment was created.
Tenant company code.
External document number.
Internal WMS shipment number.
Current shipment status.
Resolved document status label.
Processing status label.
List of posted shipment document numbers.
| Status | Meaning |
|---|---|
| 404 | Shipment not found for the given external document number. |
GET /api/v1/integration/shipments//movements
Returns the inventory movements created when a shipment was posted, identified by its external document number. Authentication:X-Api-Key: <api-key> (required).
ERP document number.
Tenant company code.
External document number.
Internal WMS shipment number.
Current shipment status.
Inventory movements created by posting this shipment.
| Status | Meaning |
|---|---|
| 404 | Shipment not found for the given external document number. |