All endpoints are now available with v3.0. Differences compared to the old endpoints (versions v1.0 to v2.0) include:
Responses to unsuccessful requests are now provided in the problem details format. Problem details are a standardized response for unsuccessful requests, providing information for computers to parse as well as for humans to understand.
For more information, see the response format documentation.
Successful results are no longer wrapped in Logic4Response or Logic4ResponseList objects. This simplifies processing the response.
All v3.0 endpoints (and higher versions) use the most compact JSON possible. The following is stripped from the response:
This saves up to 30% of bandwidth, resulting in faster responses.
Request body parsing for V3 endpoints more closely adheres to standards.
Notable changes include:
No longer allowed: "DateTime": "19-3-2026", "DateTime": "2026-3-19 9:28" (and many other variations)
Replacement: "DateTime": "2026-03-19", "DateTime": "2026-03-19T09:28:00"
No longer allowed: "Text": 12, "Text": true
Replacement: "Text": "12", "Text": "true"
No longer allowed: 'Property': 'value', Property: "value"
Replacement: "Property": "value"
Examples: // I am a comment, /* I am also a comment */
These must be removed before sending the request.
Some endpoints have been modified during their transition to v3. The existing endpoints are unchanged. Details of the new functionality can be found in the documentation for the new endpoints.
Notable changes include:
Endpoints which used to always return 'true' or a hardcoded string upon success now return an empty body instead. Some information which was already present in the request body is no longer returned in responses. More endpoints now return the ID of newly created entities.
Various requests which used to return HTTP 500 now return a HTTP 400 response instead.
The fields TakeRecords/SkipRecords are now required on more endpoints.
Some endpoints which provide delete functionality have been moved to using the HTTP method DELETE, and their arguments have been moved from the request body to the query string.
If any order row ID is invalid, the request is cancelled and a HTTP 400 response is returned.
These endpoints now correctly return only order rows or invoice rows respectively. /v3/Orders/GetOfferRows has been added to provide results which are no longer returned by GetOrderRows or GetInvoiceRows.
Some redundant endpoints do not have a v3.0 version as the same functionality is provided by different endpoints.
/v3/Pickbons/ProcessPickbons can be used instead.
/v3/Pickbons/GetOrderHeadPickbonRows can be used instead as this new version supports multiple pickbons in one request.
/v3/Shipments/AddShipmentForInvoiceOrOrder can be used instead as this new version contains identical functionaliy to optionally send emails.
The old endpoints with versions v1.0 to v2.0 are still supported, but for a limited time. We have not yet determined when these endpoints will be removed. We strongly recommend switching to v3.0 endpoints.