Congrats on the V3 Beta! Love the new pricing model (I think). A few questions…
You’ve got old copy talking about V2 and V1 in the V3 FAQ - flightaware.com/commercial/flightxml/v3/faq.rvt - specifically the bit talking about “What are the plans for FlightXML 1 now that FlightXML 2 is available?”
It’d be dandy if IATA codes (as useless as they are) were available (as a field that’s returned; I know they’re not unique, so wouldn’t work as a parameter) via AirportInfo; many folks expect those over the ICAO codes.
Are faFlightID’s consistent between V2 and V3? If I get a push notification from V2, can I query V3 with faFlightID for details?
Is each call to the API or push notification (once they’re available) going to count as a single query insofar as your new pricing model is concerned? In other words, are there cases where a single API call could get charged for multiple queries (including include_ex_data with a call to FlightInfoStatus, or requesting 150 results from AirportBoards, etc.)?
What’s current best thinking for timeline on push notifications? Are we weeks, months, or years away? (Never mind - I see Q3 2017 is the target launch).
How are queries that exceed the per-minute rate limit handled? Do you queue them up on your end and return info as time allows? Return a 429 header? Return data and have sales get in touch with a recommended upgrade to the next plan?