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 […]
Breaking Changes from October 1, 2023 Read More »
Search airports by IP geolocation and Search airports by location endpoints now have query-string style counter-parts. If you’re on the most recent pricing plans, we recommend: using /airports/search/location?lat={lat}&lon={lon}&radiusKm={radiusKm}&limit={limit} instead of /airports/search/location/{lat}/{lon}/km/{radiusKm}/{limit} (documentation) using /airports/search/ip?q={ip}&radiusKm={radiusKm}&limit={limit} instead of /airports/search/ip/{ip}/km/{radiusKm}/{limit} (documentation) New endpoint added: Solar and day time at the airportGET /airports/{codeType}/{code}/time/solar/*It produces certain solar and daytime calculations
April ’23 Updates: New Endpoints and Performance and Usability Improvements Read More »
Our new endpoint allows geolocating nearby airports by IP address. We already have an endpoint returning nearest airports by making use of the coordinates (latitude and longitude) as an input. The new endpoint complements this set. It geolocates the coordinates internally by using the IP address as an input, and returns airports, closest to that
Geolocating Nearby Airports by IP Read More »
We now return ICAO and IATA airline codes as part of API responses from any flight endpoints, whether it is FIDS or flight status. Earlier, we only returned the name of the airline. The change will only apply to the flights, where the airline / operator could be correctly mapped. This is valid for the
Airline Codes for Flight Endpoints Read More »
We have significantly expanded the capabilities of our airport delays endpoint. This endpoint is designed to get a statistical insight of the “smoothness” of flight operations in this or that airport. Until recently, it only allowed you to trace this information in real-time only. We have now changed several things: [UPDATED] Airport delays endpoint now
Introducing Historical Airport and Global Delays Read More »
We have done something we were supposed to do a long time ago: we have published proper Terms of Use for our API. From now on these terms will be applicable to everyone using our API, including existing and new subscribers. We understand it might be quite a boring read, but nevertheless, we encourage you
Introduction of the Terms of Use Read More »
We’re introducing a new big feature: Flight Alert PUSH API. It facilitates the delivery of flight data in a fundamentally different manner. Instead of polling flight status or FIDS endpoint again and again in order to get data updates, you can now subscribe to a certain flight or airport and get notified automatically whenever an
Introduction of Flight Alert PUSH API Read More »
We have updated our “Flight delay statistics by flight number” endpoint. Earlier delay records of the same flight number were grouped by origins and destinations. This way you could separately see how much the flight is delayed in each airport it departs from or arrives at. From now on, groups are as well segregated by
Improved flight delay statistics, flight delay brackets and flight locations for FIDS Read More »
We are continuing to expand capabilities related to analyzing actual flight tracks with reliance on community-maintained ADS-B data provided by third-party. Attentive users could have already noticed that for some airports AeroDataBox API has started providing: Flight runway data, which we introduced as a response to requests of a few users to have some capabilities