Want the latest version of AeroAPI?
Important update: You have reached documentation for AeroAPI version 3, which will reach end-of-life October 2023. If you are currently using this version, please make plans to migrate to version 4 in the near future.
We recently introduced AeroAPI v4, FlightAware's next-generation RESTful API for accessing comprehensive flight data. Offering a more advanced and easier to use platform!
- RESTful/JSON - following latest standards and open API 3.1 specifications
- Enhanced flight information and deeper data content
- Comprehensive interactive online developer documentation
- Foresight predictions now available
- Custom Flight Alerting
Version 3.0 Beta
Pricing
Previous versions of AeroAPI used a usage-based pricing model that billed users a small amount for every request made, with the price determined by the pricing class of the specific function accessed, and a discount based upon the total number of requests made per month. Many users found this pricing model difficult to estimate how much their monthly bills would be in advance, especially when designing a new application or when application usage might grow over time.
To make pricing easier to estimate, Version 3.0 uses a monthly "tiered subscription" model that allows you to simply choose the features that most closely correspond to the functionality needed by your application. This simplifies budgeting and allows you to know that your monthly costs will be the flat subscription price that you had originally selected. (Maximum usage caps per month and request rate limits do apply to most of the tiers. Auto-upgrade to the next tier upon reaching your monthly usage limit can optionally be enabled.)
Additionally, to make it easier for new application developers to begin accessing Version 3.0, a free tier is available with a limited number of queries every month.
The query count is determined by the number of times a AeroAPI method is invoked by your application at its default number of results; each invocation will count as a single query. Many AeroAPI methods return lists and limit the number of results to 15 records by default, but also have a "howMany" argument that allow you to request a larger number of results. If you specify a value for "howMany" that is greater than 15 (and have already invoked "SetMaximumResultSize" to opt-in to a larger maximum limit), then you may be returned up to the quantity specified by howMany, if possible. You will be billed for a query count equivalent to the actual number of results returned divided by 15, rounded up. For example, if you call SetMaximumResultSize with a max_size of 100, then call FlightInfo with howMany of 45, but it only returns 35 records, you will be charged the equivalent of calling FlightInfo a total of 3 times, or 1+int(35/15).
- Additional 500 queries
- Geospatial queries within 250nm of your location
