ℹ️ This article is about the Luminovo API, which connects your own systems (for example your ERP) to Luminovo. To connect Luminovo to a supplier's API for live prices and stock, see Activate direct API integrations to your suppliers.

Action required: switch your implementation of Luminovo public API until August 7th, 2025 to avoid interruptions to your operations.

Introduction

Until now, there have been two ways to access Luminovo's Rest API.

Legacy URL {tenant-name}.luminovo.com/api
New URL api.luminovo.com

To ensure maximum stability for existing API endpoints, we require all users to switch to the new API. This migration will help our engineering team focus on releasing new and more stable endpoints.

We expect those changes to take around 2-3 hours of development time on your side.

Required Changes:

Switch to the new authentication method
Update request URLs
Verify Accept headers for data model versioning

1. Switch to the new authentication method

The new authentication method still uses Bearer tokens but simplifies the process. It is documented in our API documentation under Authentication.

The new authentication method still uses Bearer tokens to do requests to Luminovo's API. Previously, client_id and client_secret were required. Now, you only need one secret token.

Examples of old vs new authentication

Old Authentication Method

curl --request POST \
  --url "https://{tenant}.luminovo.com/api/token" \
  --header 'content-type: application/json' \
  --data '{
    "client_id": "your-client-id",
    "client_secret": "your-client-secret"
  }'

With a sample response:

{
   "access_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c",
   "token_type": "bearer",
   "expires_in": 3600
 }

New Authentication Method

curl --request POST \
  --url "https://api.luminovo.com/token" \
  --header 'content-type: application/json' \
  --data '{
    "token": "cb7daea2-df5f-44de-99cc-213668e6c991"
  }'

The response only contains a string with the token:

eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c

Steps to migrate:

Create your new API token in Luminovo: go to Settings > Integrations > Luminovo API, click Create token in the Machine tokens section, and assign the roles that control what the token can access
Update your authentication code (see documentation)
Ensure you correctly extract the Bearer token from the response (to test this without writing code, see Luminovo API – API authentication and Postman example project)

2. Update request URLs

Simply change all endpoints from:

{tenant}.luminovo.com/api/{endpoint} to api.luminovo.com/{endpoint}

Compare your implementation with our API documentation to ensure you're using the latest parameters and data models. See our our public API documentation.

3. Verify Accept headers

Ensure your requests include the proper Accept header to specify the data model version: Accept: application/api.luminovo.[resource]-v1+json. For some endpoints, this header is not required.

This header ensures you receive responses in the expected format even as we evolve the API.

Testing and Timeline

The legacy API will remain accessible until August 7th, 2025
We recommend testing the new API in a non-production environment first
Begin with low-volume, non-critical endpoints before migrating critical functionality

Questions

If you have any questions to the technicalities of switching to the new public API, please reach out to [email protected]

Updating Your Luminovo API Connection: Quick Guide for IT Teams