Flight History and Schedule (range of days) / TIER 3
What is the history or schedule of a specific flight within a specific range of dates in past or in future?
This endpoint is the similar to the Flight status endpoint. The only difference is that instead of returning the flight data on a single date, it returns the data over a range of dates, thus allowing to get insights on the flight history or schedule within the specified range.
All limitations and considerations applicable to Flight status endpoint are applicable to this endpoint as well.
Request
- Base URL: https://api.aerodatabox.com
- URL: https://api.aerodatabox.com/flights/{searchBy}/{searchParam}/{dateFromLocal}/{dateToLocal}
- Auth: API key in header X-Api-Key
Path parameters
Criteria to search flight by<p>Possible values:</p>
<ul> <li><b>0 - Number</b>: Search by flight number</li> <li><b>1 - Reg</b>: Search by aircraft registration</li> <li><b>2 - CallSign</b>: Search by ATC call-sign</li> <li><b>3 - Icao24</b>: Search by 24-bit ICAO Mode-S Transponder code</li> </ul>Criteria to search flight by
Value of the search criteria. If searchBy is:
- number, then this field shoud be Flight number (with or without spaces, IATA or ICAO, any case formats are acceptable, e.g. KL1395, Klm 1395)
- callsign, then this field should be ATC call-sign of the flight (with or without spaces, any case formats are acceptable, e.g.AFL1482, nca 008X);
- reg, then this field should be Aircraft tail-number (with or without spaces or dashes, any case formats are acceptable, e.g.PH-BXO, DeMhJ);
- icao24, then this field should be Aircraft ICAO 24-bit Mode-S address specified in hexadecimal format (e.g. 484161, 483EFD).
Beginning of the range of local dates of departure or arrival (in format: YYYY-MM-DD, e.g.: 2019-08-29). Maximum/minimum allowable value is determined by the current data coverage limitations and your pricing plan.
End of the range of local dates of departure or arrival (in format: YYYY-MM-DD, e.g.: 2019-08-29). Maximum/minimum allowable value is determined by the current data coverage limitations and your pricing plan. This date must be bigger than the dateFromLocal. The maximum difference between this date and dateFromLocal is limited and is determined by your pricing plan (ranging from 7 to 30 days as per moment of writing).
Query parameters
Direction of flight<p>Possible values:</p>
<ul> <li><b>1 - Arrival</b></li> <li><b>2 - Departure</b></li> <li><b>3 - Both</b></li> </ul>- If set to Both (default, recommended for best results) then the dateFromLocal and dateToLocal parameters shall be considered as both departure and arrival dates. If a flight departs OR arrives on dates within the specified range (in the local timezone of the origin or destination, respectively), it will be returned.
- If set to Departure then the dateFromLocal and dateToLocal parameters shall be considered as departure dates only. Only the flights departing on dates within the specified rang(in the local timezone of origin) will be returned.
- If set to Arrival then the dateFromLocal and dateToLocal parameters shall be considered as arrival dates only. Only the flights arriving on dates within the specified rangd (in the local timezone of destination) will be returned.
Response
OK
Changes
No recorded changes to this operation across all 1 revision of this API.