Breaking Changes from July 1, 2023

We are introducing a couple of minor breaking changes in our API and are asking all our customers to modify their application respectively. Please complete the changes below before July 1, 2023, otherwise your applications might get broken. Until then, endpoints remain fully backwards compatible. If you are an active user and need more time to adapt the changes, please let us know.

Endpoints Affected: Flight status; FIDS

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

Documentation: https://doc.aerodatabox.com/#tag/Flight-API/operation/GetFlight
Documentation: https://doc.aerodatabox.com/#tag/Flight-API/operation/GetAirportFlights

Summary:

  • All pairs of times represented in local and UTC timezones are now in combined into nested objects.
  • Certain properties of location contract are now represented in more units of measurement.

Adjustments Required:

In endpoint response:

  • 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

Leave a Comment