Version 2022.04 of the Criteo API is live as of April 21, 2022. This is a stable version of the API and will be supported until April 21, 2023. Our corresponding client libraries (Python, Java, and PHP) and Postman have been updated with the new version.

The Criteo API will undergo scheduled maintenance on February 21st at 11:00 a.m. GMT. This interruption should last approximately twenty minutes. To check the status of the Criteo API's endpoints, you can always check status.criteo.com.

Version 2022.01 of the Criteo API is live as of January 20, 2022. This is a stable version of the API and will be supported until January 20, 2023. Our corresponding client libraries (Python, Java, and PHP) have been updated with the new version.

The following endpoints will be deprecated on January 18th, 2022 in accordance with the Criteo API versioning policy. By updating to the current stable version, you can ensure your services will not be disrupted for 12 months.

To provide our developer community with a reliable and stable API experience, we are announcing the enforcement of our rate limit policy.

Version 2021.10 of the Criteo API is live as of October 19, 2021. This is a stable version of that will be supported until October 19, 2022. The new stable version carries over all functionality from 2021.07 but does not include any new endpoints or functionality.

Version 2021.07 of the Criteo API is live as of July 27th, 2021. This version will be supported until July 27th, 2022.

Our client libraries for the Criteo API are now available. This transition SDK will help you migrate from MAPI to Criteo API and include endpoints in the latest stable version 2021-04, as well as /legacy endpoints.

If you have recently migrated to the Criteo API from MAPI, you may need to check your authentication. To avoid a disruption in service, make sure you are authenticating following the process that was shared in the onboarding guide here.

If you have implemented your calls to Criteo authentication endpoint /oauth2/token without the header Content-Type: application/x-www-form-urlencoded, this header will be mandatory beginning on May 11th.