LUCENEX / Documentation
API & integration reference
Route inventory, authentication and integration contracts to validate.
Reviewed 9 November 2026 · WMS 8020cd0API contract
The current implementation exposes ASP.NET controller endpoints. Successful application responses generally use { isSuccess, code, errorMessage, data }; list responses wrap rows and totals in data. HTTP authentication/authorization failures may instead return 401 or 403.
Authenticate with POST /login. Send the returned access token as Authorization: Bearer <token>. List requests use pageIndex, pageSize and searchObjects. This is a source-derived reference, not a versioned external API guarantee.
Integration work
ERP/accounting synchronization, partner APIs and automated hardware interfaces must be scoped and tested separately. Before integrating, agree ownership of stock data, identifiers, retry/idempotency behavior, error handling, field mappings and reconciliation. Do not let an integration bypass workflow confirmation rules.
Controller route inventory
The following inventory is generated from the documented source revision. Route existence is not evidence that every method, permission or payload has been validated. Use the source controller and view models for exact request contracts.
191 source-derived routes