Last API documentation version: 1.2.4

Most recent API features:

• A new end-point /quota enables to display the quota usage for your application.
• The API response header now contains information about your quota usage.
• A new optional parameter "eventID" can be added in the API request header, in order to lineage the API call with the ELIXPEDIA event in HIP monitoring tool 

The recommended way to trigger calls to the "PUBLISHED HIERARCHY" API is to subscribe to events published by UNIKA.

Indeed, UNIKA publishes an event every time a product hierarchy is modified (generally, less than one hundred per day).

TOPICS

A topic is a message queue that contains events. All UNIKA events are published to Confluent in topic "global.product.hierarchy.v1"

Séverin MAS - GLOBAL IT - Master Data Team   [email protected] / Chat in Teams

To protect the API back-end (ELIX360 platform) from excessive requests, a quota has been defined on the "SKU GET" API: each application is allowed to invoke the API a maximum of 100 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": "Daily quota of requests has been reached", "message": "Too many requests sent." }

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

Last API documentation version: 1.2

Most recent API features:

• New optional query string parameters "instance" and "catalog" can be added to the API request, in order to skip the built-in routing logic which determine the target ELIXPEDIA instance and catalog. 

Last API documentation version: 1.2.4

Most recent API features:

• A new end-point /quota enables to display the quota usage for your application.
• The API response header now contains information about your quota usage.
• A new optional parameter "eventID" can be added in the API request header, in order to lineage the API call with the ELIXPEDIA event in HIP monitoring tool 

Here are some examples of update requests that some applications are authorized to post:

Once the update request has been sent to ELIXPEDIA, the "SKU UPDATE" API would return one of these codes:

200: Data updated successfully

This means that the data is now up to date in the ELIXPEDIA instance. You can then expect that the data change to be notified to other applications in the forthcoming seconds.