API Release Schedule & Versioning Policy Update

📘

You may have noticed there was no API release in April this year. That's because we are updating our release schedule and versioning policy, which will take effect on July 21, 2026.

What's Changing With the New Policy

Starting with the July release, Criteo APIs will move to a bi-annual release cadence(January and July) with three versioning tiers:

• Experimental: Early-stage endpoints available for testing and feedback. Expect breaking changes.
• Release Candidate: Features approaching stability. Integrations built here will carry forward to stable without URL changes.
• Stable: Fully supported, production-ready releases on our standard support timeline.

What This Means For You

• Fewer forced migrations. When a feature graduates from Release Candidate to Stable, the URL stays the same, no integration changes needed.
• More predictability. You'll always know how far a feature is from Stable and what to expect at each stage.
• Earlier access. Release Candidates give you a reliable preview of the next Stable release, with a clear promotion timeline.
• A safe sandbox for the Experimental. Truly exploratory or in-testing endpoints now have a dedicated home, separate from your production integrations.

Timeline & Next Steps

The new versioning policy will officially take effect with the next July release 2026.07.
In the coming weeks we will publish:

• The full new versioning policy documentation, detailing the rules and timelines for each tier.
• A complete mapping of all current Preview and Stable endpoints in 2026.01to their equivalent tier in the new system.

We'll communicate clearly and consistently throughout the next two quarters to support any users who need to migrate.