The Receiving API manages inbound warehouse receipts. It covers creating and retrieving receipt headers with their lines, updating receipts, posting receipts to finalize stock movements, and exporting/importing receipt records via config packages. For GrupoMAS tenants, the header list is sourced live from the ERP.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.
GET /api/ReceivingHeaders
Returns a paginated list of receiving headers for the authenticated company. For GrupoMAS tenants, the list is fetched live from MAS (released receipts). For local tenants,OPERATOR role users see only RELEASED and RECEIVING status documents.
Authentication: Authorization: Bearer <token> (required).
1-based page. Defaults to
1.Page size. Defaults to
20.Search by receipt number, vendor name, external document number, or status.
Filter by status (e.g.,
OPEN, RELEASED, RECEIVING, CLOSED).Current page.
Page size.
Total records.
Total pages.
POST /api/ReceivingHeaders
Creates a new receiving header document. Lines are required in the request body. Authentication:Authorization: Bearer <token> (required).
Linked purchase order number. Auto-generated if omitted.
ERP or external reference number.
Vendor code.
Vendor display name.
Destination warehouse location code.
Reference number.
Free-text remarks.
Initial status. Defaults to
OPEN.Expected receipt date. Defaults to now.
Receipt lines. Each line must include
itemId, quantityExpected (> 0), and uOM.New receiving header ID.
Auto-generated receipt document number (e.g.,
RCP-0000001).| Status | Meaning |
|---|---|
| 400 | Missing lines, invalid item, zero/negative expected quantity, or missing UOM. |
GET /api/ReceivingHeaders/
Returns full detail for a single receiving header including all lines with posted and remaining quantities. Authentication:Authorization: Bearer <token> (required).
Receiving header ID.
Header ID.
Receipt number.
Current status.
Resolved document status label.
Processing status label.
Whether a handheld operator has active scans on this receipt.
Email of the operator currently working this receipt, if any.
Receipt lines with
itemCode, itemDescription, quantityExpected, quantityReceived, remainingQuantity, postedQuantityReceived, binCode, locationCode, and uOM.| Status | Meaning |
|---|---|
| 404 | Receiving header not found. |
PUT /api/ReceivingHeaders/
Updates a receiving header and replaces its lines. Only allowed for headers inOPEN or RELEASED status.
Authentication: Authorization: Bearer <token> (required).
Receiving header ID to update.
Updated PO number.
Updated vendor code.
Updated vendor name.
Updated destination location code.
Updated reference number.
Updated remarks.
Updated status (
OPEN or RELEASED).Updated receipt date.
Replacement lines array.
| Status | Meaning |
|---|---|
| 400 | Invalid status transition, missing lines, or handheld activity prevents re-opening. |
| 404 | Receiving header not found. |
| 409 | Header is locked by a concurrent operation. |
POST /api/ReceivingHeaders//post
Posts a receiving header, finalizing the receipt and creating inventory movements for all received lines. Updates stock quantities and queues an outbound acknowledgment to the connected ERP if configured. Authentication:Authorization: Bearer <token> with role ADMIN, SUPERVISOR, or OPERATOR (required).
Receiving header ID to post.
Always
Recibo registrado correctamente. on success.Auto-generated posted receipt number (e.g.,
PR-000001).ID of the created outbound acknowledgment record.
Initial delivery status of the acknowledgment.
| Status | Meaning |
|---|---|
| 400 | Receipt has no lines, is already fully posted, bin is missing, or quantity exceeds expected. |
| 403 | Caller lacks required role. |
| 404 | Receiving header not found. |
| 409 | Header is locked by a concurrent operation. |
GET /api/ReceivingHeaders/export-config
Exports receiving headers for the tenant as an Excel config package (.xlsx).
Authentication: Authorization: Bearer <token> (required).
Returns application/vnd.openxmlformats-officedocument.spreadsheetml.sheet.
POST /api/ReceivingHeaders/preview-config
Previews a receipts config package import without persisting changes. Authentication:Authorization: Bearer <token> (required).
Multipart form upload. Must be a valid Dragon Guard
RECEIPTS config package .xlsx.Whether the package passes validation.
Number of new receipts that would be created.
Number of existing receipts that would be updated.
Row-level errors.
Preview of first 50 rows.
POST /api/ReceivingHeaders/apply-config
Imports receiving headers from a Dragon Guard config package Excel file. Authentication:Authorization: Bearer <token> (required).
Multipart form upload. Must be a valid Dragon Guard
RECEIPTS config package .xlsx.Number of new receipts created.
Number of existing receipts updated.
Any errors encountered.