Generates a Bearer Token
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
📌 Authentication – Credentials and Token
Authentication is performed via an HTTP request using the credentials provided by the Neomode team, based on the configured environment (homologation or production).
🔐 Access Credentials
| Field | Type | Description |
|---|---|---|
clientId | string | Identifier of the authorized store or retailer. |
clientSecret | string | Secret key associated with clientId, used for authentication. |
scope | string | Access scope. Use the default value "Lori", unless otherwise specified. |
Take care of your Credentials
Credentials are provided exclusively by the Neomode team by the Neomode Vault
Do not share or expose this data publicly!
⏳ Token Duration
The authentication response will include the expires_in field, which represents the token's validity in seconds.
After this period, the token expires and must be renewed using the same initial credentials.
Requests with an expired token will return a 401 Unauthorized error.
We recommend that your system implement an automatic renewal mechanism before expiration.
📥 Example of using the Token in the header
After obtaining the authentication token, include it in the Authorization header of all protected requests:
Example HTTP header
A--header 'Content-Type: application/json' \
--header 'Authorization: ••••••'