We do not offer a separate “test server” or “sandbox” infrastructure for outside customers to use. We welcome use of our standard web interfaces for development of new apps.
The “change” notifications are substantially the same format, containing all of the same fields as other notifications. The only things that vary are the textual content of the long_desc/short_desc/summary fields. Those 3 fields are intended to simply be displayed to the user and not mechanically parsed, since the nature of the data is so variable, ever changing, and potentially subject to localization.
“UAL1754 flight information has changed”
“United #1754 flight information has changed Departure Gate is now 66”
“SWA861 flight information has changed”
“Southwest #861 flight information has changed Departure Time is now Sun 10-May-2015 02:40PM MDT Arrival Time is now Sun 10-May-2015 03:50PM MDT”
However, the above two examples are not intended to be comprehensive of all possible messages that might be received.
- We do not begin billing until you have accumulated more than $5 of usage, which equates to more than 500 separate requests. If you never accumulate more than $5 then you will not receive a bill for that initial usage, and this is usually enough to allow people to decide whether FlightXML will be suitable for their needs or not. In some cases, we may also provide users with a time-limited free API key if you have been discussing your needs with a FlightAware sales representative.