The movements API provides read-only visibility into the inventory ledger. Operators and supervisors use it to audit what has moved, when, and by whom — directly from the handheld without needing to log into the back-office. Two independent resource groups are exposed: raw inventory movements (individual stock entries) and product journals (grouped batches of movements with header metadata). Neither resource accepts write operations from the handheld; all mutations occur through the receipts, shipments, or back-office posting workflows.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/CodexaCP/DG_APK/llms.txt
Use this file to discover all available pages before exploring further.
Inventory movement records (
GET /api/movements) are read-only from the handheld — there are no POST, PATCH, or DELETE operations on raw movements. Product journals support one write operation: PUT /api/movements/journals/{journalNo} saves line-level edits to an open journal before it is posted from the back-office.GET /api/movements
Returns a paginated list of inventory movement records filtered by any combination of search term, bin, location, movement type, reference number, item code, and date range. All filter parameters are optional; omitting all of them returns the full movement history in reverse chronological order (server default). Method & path:GET /api/movementsAuth required: Yes
Query parameters
1-based page number.
Number of records per page.
Free-text search term matched across multiple fields (movement number, item description, reference).
Filter to movements involving a specific bin code.
Filter to movements within a specific warehouse location.
Filter by movement type, e.g.
RECEIPT, SHIPMENT, TRANSFER, ADJUSTMENT.Filter by the source document reference number, e.g. a receipt number or shipment number.
Filter to movements for a specific ERP item code.
Start of date range, formatted
yyyy-MM-dd. Inclusive.End of date range, formatted
yyyy-MM-dd. Inclusive.Response — 200 OK
Returns aPagedResponse<MovementsPageDto>.
Current page number.
Records per page as requested.
Total matching records across all pages.
Total number of pages.
Whether a previous page exists.
Whether a next page exists.
Array of
MovementsPageDto objects.Example
GET /api/movements/journals
Returns a paginated list of product journal headers. Journals are logical groups of inventory movements created for planning, bulk transfers, or adjustments. Each header summarises the journal purpose and its line count; useGET /api/movements/journals/{journalNo} to fetch the full line detail.
Method & path: GET /api/movements/journalsAuth required: Yes
Query parameters
1-based page number.
Records per page.
Free-text search matched against journal number, description, and external document number.
Response — 200 OK
Returns aPagedResponse<ProductJournalHeaderDto>.
Current page number.
Records per page as requested.
Total matching records across all pages.
Total number of pages.
Whether a previous page exists.
Whether a next page exists.
Array of
ProductJournalHeaderDto objects.Example
GET /api/movements/journals/
Returns the full detail of a single product journal including all of its lines. Use this after the list endpoint to drill into a specific journal’s individual item movements. Method & path:GET /api/movements/journals/{journalNo}Auth required: Yes
Path parameters
The journal number, URL-encoded. Obtain from
GET /api/movements/journals.Response — 200 OK
Returns aProductJournalDetailDto, which extends ProductJournalHeaderDto with a lines array.
ProductJournalHeaderDto. The additional lines field:
Array of
ProductJournalLineDto objects.null (empty response) when the journalNo is not found.
Example
PUT /api/movements/journals/
Saves updated header metadata and line entries for an open product journal. The handheld uses this to record line-level quantities, source/target bins, and lot numbers before the journal is posted from the back-office. The full journal detail (header + all lines) is returned after the save. Method & path:PUT /api/movements/journals/{journalNo}Auth required: Yes
Path parameters
The journal number to update, URL-encoded. Obtain from
GET /api/movements/journals.Request body
Free-text description of the journal’s purpose.
Default movement type for the journal header, e.g.
ADJUSTMENT, TRANSFER.Planned or actual posting date for the journal.
External reference document number.
Intermediate transit location for in-transit transfer journals.
Full replacement set of journal lines. Each entry is a
ProductJournalLineDto.Response — 200 OK
Returns the updatedProductJournalDetailDto. The structure is identical to the response of GET /api/movements/journals/{journalNo} — see that endpoint for field descriptions.
Error conditions
| Status | Condition |
|---|---|
400 Bad Request | Journal number is missing or the request body is invalid. |
404 Not Found | No journal with the given journalNo exists. |
409 Conflict | The journal has already been posted and cannot be modified. |