Breaking Changes from October 1, 2023

We are introducing several breaking changes to our API and are asking all our customers to adjust their application respectively as soon as possible.

Summary of Changes

Changes concern responses from the API only. Requests are not affected.

• All instances of local and UTC date-times currently represented as a pair of sibling fields suffixed or prefixed with “Local” and “Utc” words respectively, and logically referring to the one and the same date-time (e.g., scheduledTimeLocal and scheduledTimeUtc) are now combined into a single object field with nested local and utc sub-properties (e.g., scheduledTime.local and scheduledTime.utc).
• Certain properties of location contract are now represented in more units of measurement and therefore also placed into a nested object (e.g., location.gsKt -> localtion.groundSpeed.kt)

Endpoints Affected and Required Adjustments in Detail

Flights and FIDS endpoints (all)

GET /flights/{searchBy}/{searchParam}*
GET /flights/airports/{codeType}/{code}/{fromLocal}/{toLocal}

• replace *.location.pressureAltFt with *.location.pressureAltitude.feet
• replace *.location.gsKt with *.location.groundSpeed.kt
• replace *.location.trackDeg with *.location.trueTrack.deg
• replace *.scheduledTimeLocal with *.scheduledTime.local
• replace *.scheduledTimeUtc with *.scheduledTime.utc
• replace *.actualTimeLocal with *.revisedTime.local
• replace *.actualTimeUtc with *.revisedTime.utc
• replace *.runwayTimeLocal with *.runwayTime.local
• replace *.runwayTimeUtc with *.runwayTime.utc

Airport local time endpoint

GET /airports/{codeType}/{code}/time/local

• replace *.localTime with *.time.local
• replace *.utcTime with *.time.utc

Airport delays endpoints (all)

GET /airports/{codeType}/{code}/delays/*

• replace *.fromLocal with *.from.local
• replace *.fromUtc with *.from.utc
• replace *.toLocal with *.to.local
• replace *.toUtc with *.to.utc

Deadline and Transition Period

Please complete the changes mentioned below before the provisioning date of October 1, 2023, otherwise your applications might get broken. Until then, the transition period will be in force when all affected endpoints remain fully backwards compatible.

If you are an active user and need more time to adapt these changes, please let us know no later than on September 24, 2023! Last minute requests to delay the changes may not be respected!

Please be advised, that this is an updated announcement, as breaking changes scheduled previously on July 1, 2023 didn’t go forward, but will be included into the upcoming batch on October 1.