Order Execution

Beyond Tires Logistic

Interface for order execution processes with Michelin warehouse logistic partners (shipment & receiving orders, item master, order status...)

Version: 1.0.0

Last Edited: July 30th, 2025

Authentication: Order Execution

Region: Worldwide

Authentication details

Shipment Tracking APIs are authenticated with the OAuth Security Scheme. To access this API, you would require valid Credentials.

-OAuth2 client credential authorization is a method used to grant access to resources in a secure manner. It involves a client application obtaining an access token directly from the authorization server using its own credentials, such as a client ID and client secret.

-By using client credentials, the authorization server can authenticate the client and issue an access token, which the client can then use to make authorized API requests. This ensures that only trusted applications can access protected resources, enhancing security and control.

Create your access token here - Generate Access token

Read the below Guidelines to learn more about Shipment Tracking API.

Guidelines on how to use this API

We suggest starting with the "Trial" Plan to explore the API calls and understand their structure before moving on to real-time data integration.

Technical details

For more information about interface contract, message format, mandatory data, body response, response codes, etc... please refer to the "Specification" tab

Security

LEX employs OAuth 2.0 for secure authentication, ensuring that all data exchanges between Michelin applications and 3PL partners are protected and compliant with industry standards. A bearer token is expected for POST and GET calls.

Call modes

GET MODE

No request body needed
Parameters:
- fetchSize: Number of elements to return (max=100, default=50)
- minTimestamp: The min timestamp of the events shipment (Accepted format is timestamp or ISO_OFFSET_DATE_TIME)
Returns body response in JSON format, containing up to 100 business messages

POST MODE

Request body is needed, matching interface contract
No parameters
Body request format: JSON
Only 1 business message at a time can be sent in 1 call

push mode

Alternative to GET mode, LEX is able to push data when available to an URL given by 3PL partner
3PL partner URL will be called on POST mode
Authentication will be chosen according 3PL partner's constraints:
- OAuth2 authentication
- Cipher payload
LEX standard message will be sent in JSON format, containing up to 100 business messages (same as GET mode)
No parameters

References

The initial deployment of LEX Order Execution in 2020 involved inbound and outbound flows managed by an internal Michelin ERP installed in Asia, interfaced with a major 3PL partner, managing Ausralian warehouses.

Currently, we continue to collaborate with this major 3PL partner ($18 Billion Gross Revenue Pro Forma in 2024), in order to outsource management of Malaysia and Australia warehouses.