Skip to main content

Release schedule & support

What to build on today

  • JSON: target v2 (alpha)
  • NDC/XML: target v26.2

Major release frequency

Breeze releases a new major API version every April and October. Breaking changes are not introduced once an API version is released.

We support the previous major API for 12 months after a new release.

JSON API versions

Major releases skip between even numbers.

  • Scheduled majors are even: v2, v4, v6, v8
  • Odd numbers are reserved in the event a partner needs an out-of-cycle breaking change for their needs. The changes in that version will be incorporated into the next even-numbered release.
  • The route carries the major only: /json/v2/…, /json/v4/…. Minor and patch releases are backward compatible and do not change the route.
VersionRelease dateSupport throughNotes
v0,v1
v22026-102028-04Build here.
v42027-042028-10Planned
v62027-102029-04Planned

NDC/XML versions

IATA numbers its XML schemas by calendar year. IATA’s latest messaging schemas are available here Breeze plans to support the .2 and .4 releases of each year.

  • The .2 schema in October.
  • The .4 schema in April.

Same 12-month maintenance window as JSON. The version is selected by the route, /ndc/v26.2/…; note the v prefix is in the URL only — the XML payload's PayloadAttributes > VersionNumber is plain 26.2.

VersionRelease dateSupport throughNotes
v21.3-Not supported Listed for identification.
v24.1-2027-04Migration target for legacy 21.3-era integrations only.
v25.42025-102027-04Pre-policy. Current until 26.2 is published.
v26.22026-102028-04Build here.
v26.42027-042028-10Planned. IATA sets the number.
v27.22027-102029-04Planned. IATA sets the number.

The chart

Every version runs through the same three phases, six months apart:

  • 🟠 Alpha — 6 months. Endpoints are up, the schema can still change, nothing is supported. Build against it early if you want to be ready on release day.
  • 🔵 Current — 6 months. Released and supported. No breaking changes.
  • Maintenance — 12 months. Security and critical fixes only, then the route is switched off.

Two versions are supported at any moment — the current one and its predecessor in maintenance. That twelve-month overlap is your migration window.

Migrating off NDC/XML v21.3

Coming from our legacy Navitaire NDC 21.3 API? Start with Switch from Navitaire NDC 21.3.