Frequently Asked Questions
I am receiving an “Authentication parameters missing” 403 response
The Schiphol API platform requires all API calls to provide authentication in the form of an app_key and app_id. Check your account for your personal app_id and app_key, or sign-up for an account if you aren’t already registered for one.
Do the API’s return JSON or XML responses?
All API’s published by Schiphol support JSON responses. In addition, some API’s will also support XML responses. To change the response type, please provide the desired content type in the ‘Accept’ header. For example, you could use ‘application/xml’ for a XML response. A 406 http status code will return if the API does not support the desired content type. Please refer to the Activedocs to check a specific response type.
Are Schiphol API calls 'idempotent'?
Whenever a request returns the same response, regardless of the number of requests, the method is regarded as ‘idempotent’. To be considered idempotent, all Schiphol API’s follow the HTTP/Rest specification. It follows that these HTTP methods will also be regarded idempotent: GET, DELETE, OPTIONS, HEAD. The following HTTP methods are not regarded idempotent: POST, PUT, PATCH.
Over time, we will expand API's and introduce new URIs as new features are added. To preserve legacy usage, the URL’s of existing APIs will not change. We will endeavour to keep the same accessible addresses for each service going forward.
About the Flight API
I am receiving a 406 status code response
The ResourceVersion http header is not provided.
When requesting the list of flights, airlines, aircrafttypes or destinations I only receive 20 items.
To keep the responses down to a reasonable size the public-flight API uses pagination. In the “LINK” header in the response the URI for the “next” and “last” pages are returned.
I only receive 20 items when requesting the list of flights, airlines, aircraft types or destinations.
The public-flight API uses pagination in order to keep the responses down to a reasonable size. The URL for the ‘next’ and ‘last’ pages are returned in the ‘LINK’ header in the response.