FlightXML3 looks like a pretty good update from an API perspective, so great work!
I’m a bit concerned about the query limits with the new pricing model though. I’m working on a consumer facing application for flight tracking and even a less-than-moderately-sized user base could hit > 600 queries per minute. For example, AirlineFlightSchedules isn’t returning any additional metadata compared to v2 except for the fa_ident. Therefore if I want to show a user all of the flights between two airports and include code shares + actual departure/arrival times I still have to make additional FlightInfoStatus calls for each flight, which can lead to dozens of API calls per user. Even with my own caching layer in between I’m not likely to get many hits due to variability in origins, destinations, and time ranges selected by users. With the lack of rate limiting in v2 this is a non-issue; the introduction of limiting queries with v3 is a huge concern of mine.
Are there any plans to cater toward use cases like this, or are consumer facing applications not really a priority?
Also, do you have thoughts on including all of the FlightInfoStatus metadata in the AirlineFlightSchedules response? It would be really helpful if you could and would definitely alleviate some query limit burden.