Public-Flights Flight API
Provide your bearer token in the Authorization header when making requests to protected resources.
Example: Authorization: Bearer 123
Unique numeric id of flight
Match pattern:^[0-9]+$
Only ‘application/json’ is allowed
Example:application/json
Resource version of the API
Match pattern:v4
Example:v4
OK
yyyy-MM-dd’T’HH:mm:ss.SSSZ
yyyy-MM-dd’T’HH:mm:ss.SSSZ
yyyy-MM-dd’T’HH:mm:ss.SSSZ
yyyy-MM-dd’T’HH:mm:ss.SSSZ
yyyy-MM-dd’T’HH:mm:ss.SSSZ
yyyy-MM-dd’T’HH:mm:ss.SSSZ
yyyy-MM-dd’T’HH:mm:ss.SSSZ
expected security filter
Allowed values:AD
yyyy-MM-dd’T’HH:mm:ss.SSSZ
yyyy-MM-dd’T’HH:mm:ss.SSSZ
yyyy-MM-dd
hh:mm:ss
The service type category of the commercial flight. For example: J = Passenger Line, C=Passenger Charter, F = Freight Line and H = Freight Charter etc.
Returns a list of flight IDs for flights scheduled within the specified datetime range (filters on scheduleDateTime). Max date range is three days.
From date of search period. Format: yyyy-MM-dd’T’HH:mm:ss
To date of search period (inclusive). Format: yyyy-MM-dd’T’HH:mm:ss
Only ‘application/json’ is allowed
Example:application/json
Resource version of the API
Match pattern:v4
Example:v4
List of flight IDs
Retrieves flights for a specific date. If scheduleDate is provided as query parameter, it will retrieve flights for that date. If not provided it is defaulted to today. If there are more hits then allowed on one page response headers will contain the URLs where other pages of the results can be reached.For example:
Link: <protocol://server_address:port/public-flights/resource> ; rel=“first”,
<protocol://server_address:port/public-flights/resource?page=10> rel=“last”,
<protocol://server_address:port/public-flights/resource?page=3> rel=“next”,
<protocol://server_address:port/public-flights/resource?page=1> rel=“prev”
Scheduled date to get flights for. Format: yyyy-MM-dd. Defaults to today if not provided
See: scheduleDate. Prefer scheduleDate. If both scheduleDate and scheduledate are used scheduleDate takes precedence
Scheduled time to get flights from. Format: HH:mm
Flight number as printed on the ticket
>= 5 characters<= 8 characters
See: flightName. Prefer flightName. If both flightName and flightname are used flightName takes precedence
>= 5 characters<= 8 characters
Direction of the flight
Allowed values:AD
See: flightDirection. Prefer using flightDirection. If both flightDirection and flightdirection are used flightDirection takes precedence
Allowed values:AD
Prefix in flight number as printed on the ticket. For exmaple: KL. This can either be a 2-character (IATA) airline prefix or 3-character (ICAO) airline prefix. Only one airline (or airlineCode) can be queried at the same time.
>= 2 characters<= 3 characters
IATA or ICAO code of airport in route; multiple values, comma separated
>= 1 characters
Include flights of earlier an scheduleDate when these have enough delay to shift to the date that is queried upon.
Default:false
See: includedelays. Prefer includedelays. If both includeDelays and includeDelays are used, includedelays take precedence.
Default:false
Default:0
>= 0<= 499
Specifies which field to use for sorting. Allowed values are flightName, scheduleDate, scheduleTime, flightDirection, mainFlight, airlineCode, id, and all fields from the searchDateTimeField parameter. Use plus or minus sign to indicate ascending or descending order. Multiple fields are allowed and should be separated by a comma. For example “-scheduleDate, +scheduleTime”.
Match pattern:^((\+|-| )?(flightName|scheduleDate|scheduleTime|flightDirection|mainFlight|airlineCode|id|estimatedLandingTime|actualLandingTime|publicEstimatedOffBlockTime|actualOffBlockTime|expectedTimeBoarding|expectedTimeGateClosing|expectedTimeGateOpen|expectedTimeOnBelt|scheduleDateTime|lastUpdatedAt)(,|$))+$
Default:+scheduleTime
From date of search period. Format: yyyy-MM-dd’T’HH:mm:ss
To date of search period (inclusive). Format: yyyy-MM-dd’T’HH:mm:ss
Query by a specific DateTime field. Allowed fields are estimatedLandingTime, actualLandingTime, publicEstimatedOffBlockTime, actualOffBlockTime, expectedTimeBoarding, expectedTimeGateClosing, expectedTimeGateOpen, expectedTimeOnBelt, scheduleDateTime, lastUpdatedAt
Allowed values:estimatedLandingTimeactualLandingTimepublicEstimatedOffBlockTimeactualOffBlockTimeexpectedTimeBoardingexpectedTimeGateClosingexpectedTimeGateOpenexpectedTimeOnBeltscheduleDateTimelastUpdatedAt
Query by ScheduleDate range.
Query by ScheduleDate range
Query based on operational/non-operational flights.true for operational and false for non-operational flights
Only ‘application/json’ is allowed
Example:application/json
Resource version of the API
Match pattern:v4
Example:v4
OK