Explore the technical features and details of our APIs: Documentation

About the Rest API Flight Information

Schiphol offers a wealth of information on current and scheduled flights to and from the airport, carried out by more than 90 different airlines.

The Schiphol flight information is managed by the airlines and airline handlers in the Central Information System Schiphol ( CISS ). Part of this flight information is made available via the Rest API Flight Information (API) to developers. The offered flight information relates to passenger flights and cargo flights (scheduled flights and charter flights).

The API provides the following detailed flight information:

• Destinations
• Airlines that operate the flights to and from Schiphol
• Aircraft types operated by the airlines
• Flights data elements
• Flight statuses

Making requests

In all requests both the APP ID and APP KEY have to be provided. Up to and including version 3 of the API, these should be included as request parameters (app_id and app_key). For version 4 and higher these are included in headers (app_id and app_key) instead.

For all requests it is also necessary to provide the version of the requested resource in a header. (resourceVersion).

Finally, an accept header needs to be provided with the request. In this header you can specify if you want json or xml as a response. The default response is json.

Acceptable values are: application/json, application/xml, application/*, */*

Example API Version 4

HTTP Headers

Accept: application/json
app_id: [app_id]
app_key: [app_key]
ResourceVersion: v4

HTTP Call

domain/flights?includedelays=false&page=0&sort=%2BscheduleTime

Pagination

For all requests that match more than 20 results pagination is applied in the response. This is done in the following manner.

When the first page of a multi-page result set is returned it will contain the link header with the following absolute paths

HTTP Reponse Header

link: <domain/flights?app_id=[app_id]&app_key=[app_key]&page=1>; rel="next", <domain/flights?app_id=[app_id]&app_key=[app_key]&page=155>; rel="last"

When other pages, being not the first or last, of a multi-page result set are returned it will contain the link header with the following absolute paths

HTTP Reponse Header

link: <domain/flights?app_id=[app_id]&app_key=[app_key]>; rel="first", <domain/flights?app_id=[app_id]&app_key=[app_key]&page=1>; rel="prev", <domain/flights?app_id=[app_id]&app_key=[app_key]&page=3>; rel="next", <domain/flights?app_id=[app_id]&app_key=[app_key]&page=155>; rel="last"

When the last page of a multi-page result set is returned it will contain the link header with the following absolute paths

HTTP Reponse Header

link: <domain/flights?app_id=[app_id]&app_key=[app_key]>; rel="first", <domain/flights?app_id=[app_id]&app_key=[app_key]&page=154>; rel="prev"