To protect the API back-end (ELIX360 platform) against severe traffic spikes and denial of service attacks (i.e. excessive number of requests in a limited period of time), each application is allowed to invoke the "PUBLISHED PRODUCT HIERARCHY" API a maximum of 10 calls every second.

If your application exceeds this limit, the API would return a 429 error, with this explicit response body:

To protect the API back-end (ELIX360 platform) against severe traffic spikes and denial of service attacks (i.e. excessive number of requests in a limited period of time), each application is allowed to invoke the "SKU GET" API a maximum of 10 calls every second.

If your application exceeds this limit, the API would return a 429 error, with this explicit response body:

Regarding "Units Of Measure", note that ELIXPEDIA only manage attributes in "Metric", and NOT in "Imperial".
Still, the ELIX "SKU GET" API is able to perform an automatic conversion when the API is invoked with parameter "imperial" .

Example

GET /global/product/v1/sku/P1869701?elixAttributes=A0452,A0077,A0799,A0083&imperial

All documentation about API is available here: https://confluence.e-loreal.com/display/APICOE/HIP+API+Section 

To access the API, your application must be first authorized on APIGEE: please send your authorization request to the API owner, by providing your application ID.

One authorized, your application must present a valid token for every API call. Here is the scope to specify to request for an access token for the "SKU UPDATE" API:

About ELIXPEDIA Events Volume

Note that ELIXPEDIA publishes all along the day A LOT OF EVENTS (average between 10K and 20K per day).

Most of these events are because of SKU modifications due to MASS UPDATES, generally coming from external systems (SAP-ECC, WISE, APO, MINDS, MIC, COMPASS...etc.).
Obviously, these mass updates are performed on a limited list of attributes (ex. palletization , transfer prices, customs code...etc.), which probably are not relevant for all applications.

UNIKA Codifications

UNIKA has its own codification for hierarchy level items, but also manage alternative codes for SAP-ECC and SAP-S4 systems: 

Note that the 3 codifications are fully equivalent (1:1 relationship), so your application could choose any of these codifications.

All documentation about API is available here: https://confluence.e-loreal.com/display/APICOE/HIP+API+Section 

To access the UNIKA "PRODUCT HIERARCHY" API, your application must be first authorized on APIGEE: please send your authorization request to the API owner, by providing your application ID.

One authorized, your application must present a valid token for every API call. Here is the scope to specify to request for an access token for the UNIKA "PRODUCT HIERARCHY" API:

"SIGNATURE" hierarchy

"METIER" hierarchy

The "Product Hierarchy" managed in UNIKA is the GROUP hierarchy (i.e. same hierarchy for all countries) and is compounded with several business objects (ex. signature, brand, axe...) represented below in blue:

Note that in SAP systems, only some of the UNIKA hierarchy levels are actually used.

To protect the API back-end (ELIX360 platform) from excessive requests, a quota has been defined on the "PUBLISHED HIERARCHY" API: each application is allowed to invoke the API a maximum of 10 000 calls per day.

If your application has reached the maximum quota allowed, the API would return a 429 error, with this explicit response body:

{ "error": { "code": "429", "reason": "Too Many Requests", "message": "Too many requests sent." }

Note that the quotas consumption count are all reset to 0 every night at 0:00AM (Paris time).