The Most Powerful Flight API Available

Great Applications Are Built On Great Data
Our comprehensive flight API allows you to integrate and display routes, schedules, timetables, flight tracking data and more on your website or application.

827 users join us in the last 30 days

Flight Data access includes:

  • Flight Tracker API: Display flight tracking data and all their relevant information on applications, websites or other platforms.
 
  • Airport Schedules API: The API service provides the flight schedules and timetables of all airports and airlines around the world and maintains this for the clients in a central database.
     
  • Historical Schedules API: The API provides flight schedule and airport timetable data based on a historical date or date range, and updates daily. Cancellations and delays are included.
     
  • Future Schedules API: The API returns flight information and airport schedule data based on a future date. It can be used to select flights after entering departure/arrival airports and dates when integrated.
     
  • Routes API: The Airline Routes API provides the data about the routes between all the airports an airline operates on.
 
  • Nearby API: The API service to find airports and cities nearby a certain location is developed based on the databases about airports and cities which Aviation Edge maintains.
 
  • Autocomplete API: This API helps to locate airports based on partial input. For example if you type Ams, it will come up with Amsterdam, Schiphol and other airports which include “ams” as part of their name or coding.
     
  • Satellite Tracker API: This API provides real-time position, speed, ID, TLE data among other details for objects orbiting around the Earth such as ISS, SpaceX and Virgin satellites, and more.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo.

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 tracker API and airport schedules API. It’s a REST API so depending on the development language you use, you can find the suitable method to develop it.

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]

Flight Tracker API - Request

Flight tracker and status API map

For information about all flights in the world

GET http://aviation-edge.com/v2/public/flights?key=[API_KEY]&limit=30000

For information about a specific flight based on: Flight IATA Number:

GET http://aviation-edge.com/v2/public/flights?key=[API_KEY]&flightIata=W8519

For information about a specific flight based on: Airlines:

GET http://aviation-edge.com/v2/public/flights?key=[API_KEY]&airlineIata=W8

Departure location:

GET http://aviation-edge.com/v2/public/flights?key=[API_KEY]&depIata=MAD

Arrival location:

GET http://aviation-edge.com/v2/public/flights?key=[API_KEY]&arrIata=GIG

Response

Track status of individual flights
Track flights of complete airlines
Track flight status based on departure airport
Track arriving flight status
[{“type”:”arrival”,
“status”:”landed”,
“departure”:{“iata_code”:”DUB”,
“icao_code”:”EIDW”,
“terminal”:”1″,
“gate”:”117″,
“delay”:3,
“scheduled_time”:”2020-07-18T06:30:00.000″,
“estimated_time”:”2020-07-18T06:30:00.000″,
“actual_time”:”2020-07-18T06:32:00.000″,
“estimated_runway”:”2020-07-18T06:32:00.000″,
“actual_runway”:”2020-07-18T06:32:00.000″},
“arrival”:{“iata_code”:”LGW”,
“icao_code”:”EGKK”,
“terminal”:”N”,
“scheduled_time”:”2020-07-18T08:10:00.000″,
“estimated_time”:”2020-07-18T07:26:00.000″,
“actual_time”:”2020-07-18T07:27:00.000″,
“estimated_runway”:”2020-07-18T07:27:00.000″,
“actual_runway”:”2020-07-18T07:27:00.000″},
“airline”:
{“name”:”Ryanair”,
“iata_code”:”FR”,
“icao_code”:”RYR”},
“flight”:
{“number”:”120″,
“iata_number”:”FR120″,
“icao_number”:”RYR120″}
}]

Airport Schedules API - Request

Departure schedule of a certain airport:

https://aviation-edge.com/v2/public/timetable?key=[API_KEY]&iataCode=JFK&type=departure

Arrival schedule of a certain airport

https://aviation-edge.com/v2/public/timetable?key=[API_KEY]&iataCode=JFK&type=arrival

Response

Track flight status based on departure airport
Airport Arrival schedules API

{
“type”: “departure”,
“status”: “landed”,
“departure”: {
“iataCode”: “JFK”,
“icaoCode”: “KJFK”,
“scheduledTime”: “2017-12-11T01:06:00.000”,
“estimatedRunway”: “2017-12-11T02:07:00.000”,
“actualRunway”: “2017-12-11T02:07:00.000” },
“arrival”: {
“iataCode”: “CVG”,
“icaoCode”: “KCVG”,
“estimatedRunway”: “2017-12-11T03:38:00.000”,
“actualRunway”: “2017-12-11T03:38:00.000”
},
“airline”: {
“name”: “Atlas Air”,
“iataCode”: “5Y”,
“icaoCode”: “GTI”
},
“flight”: {
“number”: “302”,
“iataNumber”: “5Y302”,
“icaoNumber”: “GTI302”
}]

Historical Schedules API - Request

For the departure schedule of a certain airport on a certain date:

https://aviation-edge.com/v2/public/flightsHistory?key=[API_KEY]&code=JFK&type=departure
&date_from=YYYY-MM-DD

For the arrival schedule of a certain airport on a certain date:

https://aviation-edge.com/v2/public/flightsHistory?key=[API_KEY]&code=JFK&type=arrival
&date_from=YYYY-MM-DD

For the schedule of a certain airport of a certain date range (also available for arrival)

https://aviation-edge.com/v2/public/flightsHistory?key=[API_KEY]&code=JFK&type=departure
&date_from=YYYY-MM-DD&date_to=YYYY-MM-DD

For the schedule of a certain airport of a certain date range (also available for arrival):

https://aviation-edge.com/v2/public/flightsHistory?key=[API_KEY]&code=JFK&type=departure
&date_from=YYYY-MM-DD&date_to=YYYY-MM-DD

For the schedule of a certain airport on a certain date (or range) but only flights with a certain status:

https://aviation-edge.com/v2/public/flightsHistory?key=[API_KEY]&code=JFK&type=arrival
&date_from=YYYY-MM-DD&date_to=YYYY-MM-DD&status=cancelled

For tracking individual historical flights:

https://aviation-edge.com/v2/public/flightsHistory?key=[API_KEY]&code=JFK&type=departure
&date_from=YYYY-MM-DD&date_to=YYYY-MM-DD&flight_number=[1234]

For filtering the flights of a certain airline from the arrival schedule of a certain airport on a certain date (also available for departure schedules and as a date range):

https://aviation-edge.com/v2/public/flightsHistory?key=[API_KEY]&code=JFK&type=arrival
&date_from=YYYY-MM-DD&&airline_iata=TK

Status can be: “active” (for departure schedules only), “landed” (for arrival schedules only), “cancelled”, “unknown”
Delay amount is included in minutes if a flight was delayed at the date.
The maximum date range can be 30 days.
The historical data starts from 14 May 2020.

More parameters available now! Check out here.

Response

{
“type”: “departure”,
“status”: “active”,
“departure”:
{
“iataCode”: “jfk”,
“icaoCode”: “kjfk”,
“terminal”: “7”,
“delay”: 10,
 “scheduledTime”: “2020-09-25t20:15:00.000”,
“estimatedTime”: “2020-09-25t20:09:00.000”,
“actualTime”: “2020-09-25t20:25:00.000”,
“estimatedRunway”: “2020-09-25t20:25:00.000”,
“actualRunway”: “2020-09-25t20:25:00.000”},
“arrival”:
 {
“iataCode”: “lhr”,
“icaoCode”: “egll”,
“terminal”: “5”,
“scheduledTime”: “2020-09-26t08:20:00.000”,
“estimatedTime”: “2020-09-26t07:32:00.000”
},
“airline”:
{
“name”: “aer lingus”,
“iataCode”: “ei”,
“icaoCode”: “ein”
},
“flight”:
{
“number”: “8814”,
“iataNumber”: “ei8814”,
“icaoNumber”: “ein8814”
},
“codeshared”:
{
“airline”:
{
“name”: “british airways”,
“iataCode”: “ba”,
“icaoCode”: “baw”
},
“flight”:
{
“number”: “114”,
“iataNumber”: “ba114”,
“icaoNumber”: “baw114”}
}
},

Future Schedules API - 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

(The date must be at least 7 days ahead of the current date)

More parameters available now! Check out here.

Response

Track flights of complete airlines
[{“weekday”: “1”,
“departure”:
{“iataCode”: “agp”,
“icaoCode”: “lemg”,
“terminal”: “2”,
“gate”: “d61”,
“scheduledTime”: “06:50”},
“arrival”:
{“iataCode”: “ory”,
“icaoCode”: “lfpo”,
“terminal”: “3”,
“gate”: “A”,
“scheduledTime”: “09:20”},
“aircraft”:
{“modelCode”: “a320”,
“modelText”: “airbus a320-232”},
“airline”:
{“name”: “vueling (vueling \u2764\ufe0f barcelona livery)”,
“iataCode”: “vy”,
“icaoCode”: “vlg”},
“flight”:
{“number”: “8172”,
“iataNumber”: “vy8172”,
“icaoNumber”: “vlg8172”}}]

Airline Routes API -Request

Airline Routes API map

For information about all routes.

GET http://aviation-edge.com/v2/public/routes?key=[API_KEY]&limit=1000&offset=0

https://aviation-edge.com/v2/public/routes?key=[API_KEY]&departureIcao=LROP

For information about a specific route. 

GET http://aviation-edge.com/v2/public/routes?key=[API_KEY]&departureIata=OTP&departureIcao=LROP&airlineIata=0B&airlineIcao=BMS&flightNumber=101

Response

[{ “departureIata”: “OTP”,
“departureIcao”: “LROP”,
“departureTerminal”: null,
“departureTime”: “09:15:00”,
“arrivalIata”: “TRN”,
“arrivalIcao”: “LIMF”,
“arrivalTerminal”: null,
“arrivalTime”: “10:45:00”,
“airlineIata”: “0B”,
“airlineIcao”: “BMS”,
“flightNumber”: “101”,
“codeshares”: null,
“regNumber”: “YR-BAP”
}]
 

Nearby API - Request

Nearby airports and cities map

For airports and cities nearby a certain latitude or longitude, within a certain distance.

https://aviation-edge.com/v2/public/nearby?key=[API_KEY]&lat=-5.466667
&lng=122.6333&distance=90

Response

Airports and cities near coordinates map

[{
“code”: “BUW”,
“icao”: “WAWB”,
“name”: “Baubau”,
“cityCode”: “BUW”,
“cityName”: “Baubau”,
“countryCode”: “ID”,
“countryName”: “Indonesia”,
“lat”: -5.466667,
“lng”: 122.63333,
“timezone”: “Asia/Makassar”,
“type”: “airport”,
“isRailRoad”: 0,
“isBusStation”: 0, “distance”: 0 },
{
“code”: “RAQ”,
“icao”: “WAWR”,
“name”: “Sugimanuru”,
“cityCode”: “RAQ”,
“cityName”: “Raha”,
“countryCode”: “ID”,
“countryName”: “Indonesia”,
“lat”: -4.916667,
“lng”: 122.583336,
“timezone”: “Asia/Makassar”,
“type”: “airport”,
“isRailRoad”: 0,
“isBusStation”: 0,
“distance”: 61404
}]

Autocomplete API - Request

To receive a response of possible options for autocomplete based on a query.

GET http://aviation-edge.com/v2/public/autocomplete?key=[API_KEY]&query=amsterdam

 

Response

[{
“countries”: null,
“citiesByCountries”: null,
“airportsByCountries”: null, “cities”:
[
{
“code”: “AMS”,
“name”: “Amsterdam”,
“cityCode”: “AMS”,
“cityName”: “Amsterdam”,
“countryCode”: “NL”,
“countryName”: “Netherlands”,
“lat”: 52.3730556, “lng”: 4.8922222,
“timezone”: “Europe/Amsterdam”,
“type”: “city” } ],
“airports”:
[
{
“code”: “ZYA”,
“name”: “Amsterdam Centraal Railway Station”,
“cityCode”: “AMS”,
“cityName”: “Amsterdam”,
“countryCode”: “NL”,
“countryName”: “Netherlands”,
“lat”: 52.3730556,
“lng”: 4.8922222,
“timezone”: “Europe/Amsterdam”,
“type”: “rail_station”,
“isRailRoad”: 1,
“isBusStation”: 0 },
{
“code”: “AMS”,
“name”: “Schiphol”,
“cityCode”: “AMS”,
“cityName”: “Amsterdam”,
“countryCode”: “NL”,
“countryName”: “Netherlands”,
“lat”: 52.30907,
“lng”: 4.763385,
“timezone”: “Europe/Amsterdam”,
“type”: “airport”,
“isRailRoad”: 0,
“isBusStation”: 0 } ],
“airportsByCities”:
[
{
“code”: “AMS”,
“name”: “Schiphol”,
“cityCode”: “AMS”,
“cityName”: “Amsterdam”,
“countryCode”: “NL”,
“countryName”: “Netherlands”,
“lat”: 52.30907,
“lng”: 4.763385,
“timezone”: “Europe/Amsterdam”,
“type”: “airport”,
“isRailRoad”: 0,
“isBusStation”: 0
}

Satellite Tracker API Output - Request

All on-orbit satellite information in one call:

https://aviation-edge.com/v2/public/satelliteDetails?key=[API_KEY]&limit=30000

Individual satellites based on NORAD number

https://aviation-edge.com/v2/public/satelliteDetails?key=[API_KEY]&code=408

Satellites based on launch year:

https://aviation-edge.com/v2/public/satelliteDetails?key=[API_KEY]&launchYear=1961

Individual satellites based on international designator (NSSDC ID) number:

https://aviation-edge.com/v2/public/satelliteDetails?key=[API_KEY]&intldes=1961-015EH

Filtering based on orbital apogee and perigee

https://aviation-edge.com/v2/public/satelliteDetails?key=[API_KEY]&orbitalapogee=1035

Response

Track satellites with NORAD number
Track satellites based on launch year
Track satellites on NSSDC ID
{
“code”:44238,
“country”:”US”,
“intldes”:”2019-029D”,
“launchDate”:”2019-05-24″,
“launchNum”:”29″,
“launchPart”:”D”,
“launchYear”:”2019″,
“name”:”STARLINK-24″,
“orbitalApogee”:”526″,
“orbitalInclination”:”53.00″,
“orbitalPerigee”:”524″,
“orbitalPeriod”:”95.13″,
“result”:
{
“ECI”:
{
“posX”:0.864328541,
“posY”:0.646453811,
“posZ”:0.0814768304,
“velX”:-0.0293383982,
“velY”:0.0319305522,
“velZ”:0.0568622704},
“geography”:
{
“alt”:525.7246056033,
“lat”:4.3437137883,
“lon”:-121.470211618},
“satelliteInfo”:
{
“classification”:”U”,
“idLaunchNumber”:”029″,
“idLaunchPiece”:”D “,
“idLaunchYear”:”19″,
“orbit”:7665,
“rightAscension”:40.7404,
“satnumber”:44238}
},
“size”:”LARGE”,
“tle1″:”1 44238U 19029D 20285.79176200 .00004147 00000-0 24451-3 0 9996”,
“tle2″:”2 44238 52.9975 40.7404 0001663 103.9813 256.1363 15.13648592 76654”,
“type”:”PAYLOAD”,
“updated”:”1602579810″}