The AirplaneManager API is a way for third parties to obtain information about the flight departments that AirplaneManager manages. AirplaneManager provides a variety of endpoints (listed below) to obtain data, such as Charter Marketing (Empty Leg) endpoint and Schedule endpoint. After a third party agrees to our terms and signs up, they will be provided with a token per each API endpoint the third party requested. The third party must provide the token in the header of all REST requests (more documentation can be found in the "Docs" section). It is important to note that a third party will only see data that a flight department has opted-in to share! If you are trying to see data for a particular company, reach out to them and tell them to go to "Settings > Third Party Vendors" and enable your app/product.
The Schedule endpoint is a way for third parties to see upcoming (and recently past) flights for a flight department. This endpoint is intended for flight department internal applications that need access to the schedule. Charter Marketplaces / Brokers will be denied if they apply for this endpoint!
A third party may use the /flightdepartments endpoint to see which flight departments have opted in to share their data and then use the /legs endpoint to obtain all of the available legs on a per-flight department basis.
The Flight Logs endpoint is a way for third parties to see "current" flight log data on an aircraft, such as airframe hours and airframe landings. This endpoint is meant to be used for maintenance companies only!
Although this endpoint may be used by anyone, it is typically intended for maintenace-related third parties.
A third party may use the /aircraft endpoint to see what aircraft they are able to get data for and then use the /current endpoint to obtain actual flight log data on a per-aircraft basis.
The Charter Marketing endpoint is a way for third parties to see eligible charter aircraft, unavailability, and one ways (empty legs) for a charter flight department.
Charter companies opt-in to share particular aircraft / their availability. Charter companies also select one way legs and may provide an estimated price.
A third party may use the /aircraft endpoint to see what aircraft are eligible for charter, /unavailability to show dates/times aircraft are unavailable, and /oneways to obtain actual one way leg information.
The fuel endpoint is a way for third party fuel vendors to update their fuel prices in our system. A fuel vendor has the option of inserting blanket pricing, which is available to all of our customers, or specific prices per flight department based on the account identifier provided by the flight department.
The Service Provider endpoint is a way for third party service providers (typically handlers) to access detailed data about approved flights so they can prefill their own software systems. Flight departments will share flights on an individual basis.
The SMS endpoint is a way for third party SMS providers to see upcoming (and recently past) flights for a flight department. The feed can be used to prefill software products for risk assessments. SMS providers also have the ability to post back high level risk scores to display on the AirplaneManager GUI.
The booking endpoint is a way for third party booking (hotel, car, catering, airline) providers to see upcoming (and recently past) flights for a flight department. The feed can be used to prefill software products for future bookings. Booking providers also have the ability to post back high level data for hotel, car, catering, and airline booking confirmations on the AirplaneManager GUI.
