Landax API is an OData-based interface that allows other systems to access data from Landax. Examples on usages are

  • Custom forms for data registrations (eg. Non-conformances)
  • Login integrations
  • Syncronization of data from customers, users etc.

When communicating through the API, you have full control over which data you access in the source system and target system. By writing and maintaining the syncronization application, you can secure that no data is lost.


To connect to the API, you need a Landax instance with an URL that normally are at the format «*», for instance The API are found at /api/v{$version}, for instance At the time this document is written, the last locked version is 20. To find the last locked version, go to /api/latest in your web browser. In the very top of the document, it says what the last locked version is. Do not use /api/latest for integration! It is possible, but latest are always changing, and integrations will break over time.

An overview of the data models and methods in the API is available from a web browser, by visiting the API main page.


All versions except the latest version is locked for changes. If you want to use functionality that is not to be found in the latest locked version of the API, contact us. We recommend always using the latest locked version. The current status of the API versions can be seen by visiting the API from a web browser. The last unlocked version (latest) should not be used for integrations.


The API has two protocols. One of them is found at /api/v25 and is defined by an OpenAPI specification, which is found on /api/v25/openapi.json or /api/v25/openapi.yaml. The API is following some general patterns inspired by the OData protocol, but diverts from it on multiple occations.

The API also supports the OData protocol, and it is found at /odata/v25. The OData metadata schema is found at /api/v25/$metadata, but most OData clients will be happy with a pointer to /odata/v25. This OData protocol is useful for PowerBI and other clients made for the OData protocol.

  • No labels