Aviation Edge API for Developers

Our database is divided between static and dynamic data. Static data is that what does not frequently change but due to the massive size of our database, there are constant updates. Think about airport and airline information. The dynamic data is that what changes more frequently or uses our software to turn it into useful tools. Think about flight tracking and airport timetables.

It’s a REST API so depending on the development language you use, you can find the suitable method to develop it. A way to try the API is by getting your free API key and then testing it on our testing page.

 

You can find the examples of each endpoint below. The layout of the GET requests are as follows:
For an entire dataset, when available:
https://aviation-edge.com/v2/public/[ENDPOINT]?key=[API KEY]
For specific string value information:
https://aviation-edge.com/v2/public/[ENDPOINT]?key=[API KEY]&[STRING]=[VALUE]

For further information:
The Software Development Kit (SDK) on our Github.
REST/JSON in Android, follow this tutorial.

  • Flight Tracker API
  • SCHEDULES api
  • Airline Routes API
  • NearBy API
  • Autocomplete API
  • HISTORICAL SCHEDULES API
  • FUTURE SCHEDULES API
  • Satellite TrackER apı

Future Schedules

Request

For the departure schedule of a certain airport on a certain future date.
GET http://aviation-edge.com/v2/public/flightsFuture?key=[API_KEY]&type=departure&iataCode=AGP&date=YYYY-MM-DD

For the arrival schedule of a certain airport on a certain future date.
GET http://aviation-edge.com/v2/public/flightsFuture?key=[API_KEY]&type=arrival&iataCode=AGP&date=YYYY-MM-DD

For the flights that are scheduled to arrive at a certain airport on a certain date (out of a departure schedule).
GET http://aviation-edge.com/v2/public/flightsFuture?key=[API_KEY]&type=departure&iataCode=AGP&arr_iataCode=ORY&date=YYYY-MM-DD

For the flights that are scheduled to depart from a certain airport on a certain date (out of an arrival schedule).
GET https://aviation-edge.com/v2/public/flightsFuture?key=[API_KEY]&type=arrival&iataCode=AGP&dep_iataCode=ory&date=YYYY-MM-DD

 

You can combine any type of the filters below to make specific calls. The below strings are all possible to use:

&iata_code=
&type=
&date=

&dep_iataCode=
&dep_icaoCode=
&arr_iataCode=
&arr_icaoCode=
&airline_iata=
&airline=icao=
&flight_num=

(obligatory) Departure or arrival airport IATA code depending on the "&type=" value
(obligatory) Either "departure" or "arrival" as both within the same query is not possible
(obligatory) Future date in YYYY-MM-DD format

filter of departure airport if "arrival" for "&type=" was chosen, based on the airport IATA code
filter of departure airport if "arrival" for "&type=" was chosen, based on the airport ICAO code
filter of arrival airport if "departure" for "&type=" was chosen, based on the airport IATA code
filter of arrival airport if "departure" for "&type=" was chosen, based on the airport ICAO code
option to filter airline based on airline IATA code
option to filter airline based on airline ICAO code
option to filter a specific flight based on its flight number
 


Response

[
{"weekday": "4",
"departure":
{"iataCode": "lax",
"icaoCode": "klax",
"terminal": "4",
"gate": "A",
"scheduledTime": "12:00"},
"arrival":
{"iataCode": "jfk",
"icaoCode": "kjfk",
"terminal": "8",
"gate": "B",
"scheduledTime": "20:35"
},
"aircraft":
{"modelCode": "a321",
"modelText": "airbus a321-231"
},
"airline":
{"name": "american airlines",
"iataCode": "aa",
"icaoCode": "aal"},
"flight":
{"number": "274",
"iataNumber": "aa274",
"icaoNumber": "aal274"}
},



          (Example for a codeshared flight)

[
{"weekday": "4",
"departure":
{"iataCode": "sea",
"icaoCode": "ksea",
"terminal": "B", "gate": "21",
"scheduledTime": "14:07"
},
"arrival":
{"iataCode": "jfk",
"icaoCode": "kjfk",
"terminal": "7",
"gate": "1",
"scheduledTime": "22:29"
},
"aircraft":
{"modelCode": "a21n",
"modelText": "airbus a321-253n"},
"airline":
{"name": "Qatar Airways",
"iataCode": "qr",
"icaoCode": "qr"
},
"flight":
{"number": "2996",
"iataNumber": "qr2996",
"icaoNumber": "qr2996"
},
"codeshared":
{"airline":
{"name": "alaska airlines",
"iataCode": "as",
"icaoCode": "asa"},
"flight":
{"number": "426",
"iataNumber": "as426",
"icaoNumber": "asa426"}}
},
  • Airports
  • Airlines
  • Airplanes
  • Cities
  • Countries
  • Taxes
  • Aircraft Types

Airplane Database

Request

For the entire database of airplanes. 
GET https://aviation-edge.com/v2/public/airplaneDatabase?key=[API_KEY]

For information about a specific airplane, you can search based on registration number. 
GET https://aviation-edge.com/v2/public/airplaneDatabase?key=[API_KEY]&numberRegistration=HB-JVE

For the airplanes based on the hex ICAO code. 
GET https://aviation-edge.com/v2/public/airplaneDatabase?key=[API_KEY]&hexIcaoAirplane=4B19EA

For information about airplanes of a specific airline, you can search based on airline IATA code. 
GET https://aviation-edge.com/v2/public/airplaneDatabase?key=[API_KEY]&codeIataAirline=0B

 

Response



"airplaneId": "55", 
"numberRegistration": "HB-JVE", 
"productionLine": "Fokker 28/70/100", 
"airplaneIataType": "F28 MK0100", 
"planeModel": "F-100", 
"modelCode": "F100", 
"hexIcaoAirplane": "4B19EA", 
"codeIataPlaneShort": "100", 
"codeIataPlaneLong": "F100", 
"constructionNumber": "11459", 
"numberTestRgistration": "PH-EZD", 
"rolloutDate": "0000-00-00", 
"firstFlight": "1993-05-31T22:00:00.000Z", 
"deliveryDate": "1993-06-29T22:00:00.000Z", 
"registrationDate": "2004-05-11T22:00:00.000Z", 
"lineNumber": "", "planeSeries": "", 
"codeIataAirline": "2L", 
"codeIcaoAirline": "", 
"planeOwner": "", 
"enginesCount": "2", 
"enginesType": "JET", 
"planeAge": "24", 
"planeStatus": "active", 

]
Close Menu