Hello,
We’re seeing unreliable results when searching scheduled flights from airlines by airline IATA codes (which we try to always stick with)
Two examples to show this behaviour:
(Works via both ICAO & IATA) EasyJet flight scheduled at 2022-03-29T01:45:00Z - EZY8848/U28848
(Only works via ICAO) TUI flight scheduled at 2022-03-29T05:00:00Z - TOM7226/BY7226
Is there a legacy reason why BY cannot return any results? And does this exist for any other airline IATA code that we need to be careful with?
Edit: Also are there any plans to allow searching with a single fully formed flight ID, e.g. U28848? If a user searches that ID, we need to find where to split it to correctly call the schedule endpoint.
Many Thanks
This does appear to be a bug within our API. I am unable to provide a proper timeline at this time, but I can ensure that our team is looking into this to get a fix out in the near future. In the meantime, we recommend sticking with searching by ICAO to ensure consistent behavior within the API.
In regards to the second question, I don’t believe we have that on our roadmap at this time, but I will be sure to bring it up as a suggestion.
1 Like
Hi Fischer!
Seems you have a regression because the BY problem was solved (mentioned in your webinar & tested by us), but now it’s back to the old behaviour:
No results:
curl -X GET “https://aeroapi.flightaware.com/aeroapi/schedules/2022-06-03T00%3A00%3A00Z/2022-06-03T23%3A00%3A00Z?airline=BY&flight_number=588”
-H “Accept: application/json; charset=UTF-8”
-H “x-apikey: xxx” \
But this works:
curl -X GET “https://aeroapi.flightaware.com/aeroapi/schedules/2022-06-03T00%3A00%3A00Z/2022-06-03T23%3A00%3A00Z?airline=TOM&flight_number=588”
-H “Accept: application/json; charset=UTF-8”
-H “x-apikey: xxx” \
Can you investigate and let us know a timeline?
Thanks
