Release schedule and support policy
What to build on today
Section titled “What to build on today”- JSON: target
v2 - NDC/XML: target
v26.2
Major release frequency
Section titled “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
Section titled “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.
| Version | Release date | Support through | Notes |
|---|---|---|---|
v0,v1 | Not released | Not supported | |
v2 | 2026-10 | 2028-04 | Build here. |
v4 | 2027-04 | 2028-10 | Planned |
v6 | 2027-10 | 2029-04 | Planned |
NDC/XML versions
Section titled “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
.2schema in October. - The
.4schema 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.
| Version | Release date | Support through | Notes |
|---|---|---|---|
v26.2 | 2026-10 | 2028-04 | Build here. |
v26.4 | 2027-04 | 2028-10 | Planned. IATA defines version number. |
v27.2 | 2027-10 | 2029-04 | Planned. IATA defines version number. |
Release lifecycle
Section titled “Release lifecycle”Each version moves through three phases:
- Alpha: 6 months. Endpoints are available, but the schema can still change and the version is not supported.
- Current: 6 months. Released and supported, with no breaking changes.
- Maintenance: 12 months. Security and critical fixes only. The route is switched off when maintenance ends.
You have 12 months to migrate after a version’s successor is released. With releases every six months, up to three versions of each API are supported at once: the current version and two in maintenance.
Each column covers six months. JSON and NDC/XML versions on the same row share a schedule. Support ends at the end of the maintenance bar; blank cells are outside that version’s lifecycle.
| API versions | Apr to Sep 2026 | Oct 2026 to Mar 2027 | Apr to Sep 2027 | Oct 2027 to Mar 2028 | Apr to Sep 2028 | Oct 2028 to Mar 2029 |
|---|---|---|---|---|---|---|
JSON v2NDC/XML v26.2 | Alpha | Current | Maintenance | |||
JSON v4NDC/XML v26.4 | Alpha | Current | Maintenance | |||
JSON v6NDC/XML v27.2 | Alpha | Current | Maintenance | |||
Migrating off NDC/XML v21.3
Section titled “Migrating off NDC/XML v21.3”Coming from our legacy Navitaire NDC 21.3 API? Start with Switch from Navitaire NDC 21.3.