You're looking at our new API platform. If you still integrate through our legacy API platform, you need to migrate your integrations here and switch to JWT-based authentication. The legacy system will be permanently decommissioned on 1 October 2026 - after that, any integration that hasn't moved across will stop working. See what you need to do →
Overview
This portal is our new API Management platform. We are moving away from our legacy API platform to this new one, which brings improved features, better performance, and stronger security for every API consumer at Schiphol.
This is not an optional upgrade. The legacy platform will be switched off, so every API consumer still using it must migrate here to keep their integrations working. The sooner you start, the more time you have to test and avoid disruption.
Migration Timeline
The following timeline can change based on the progress we make and will be updated accordingly. Plan your migration around these dates and don't wait until the final weeks.
The new developer portal - the one you're on now - launched. You can create your account, request API access, and start migrating your integrations here today.
This portal and the legacy platform run in parallel so you can migrate at your own pace. Create your account here, request access, switch to JWT authentication, and validate everything in acceptance before this window closes.
The legacy platform will be permanently shut down on 1 October 2026. Any integration still pointing at the old system - or still using API-key authentication - will stop working. All users must have completed their migration to this portal by this date.
Account creation, access approval, and switching to JWT can take time - especially if several teams migrate at once near the deadline. Start now so you have room to test and resolve any issues well before 1 October 2026.
What This Means for You
To move your integrations onto this platform before the legacy system is switched off, complete the steps below here on this portal.
- Create an account on this portal (if you don't already have one)
- Request access to the APIs you currently use, here
- Switch your API authentication to JWT tokens (OAuth 2.0)
- Update your applications with the new API credentials and endpoint URLs
- Validate everything in acceptance (ACC) before switching production traffic
Key Changes
Authentication Method
This platform uses JWT (JSON Web Tokens) for API authentication instead of the static API-key method used by the legacy platform. Instead of sending an App Id / App Key on every request, you exchange your Client ID & Secret for a short-lived token and send it as a Bearer token. This provides:
- Enhanced security with token-based, short-lived credentials
- Better control over token expiration and renewal
- An industry-standard authentication protocol (OAuth 2.0 Client Credentials)
- Improved API request tracking and monitoring
| Aspect | Legacy Old platform | Now This platform |
|---|---|---|
| Authentication | Static API keys (App_Id / App_Key headers) | JWT Bearer token (OAuth 2.0 Client Credentials) |
| Credential lifetime | Long-lived, rarely rotated | Short-lived tokens (OAuth 2.0) |
| Endpoint URLs | Legacy hostnames & paths | New Schiphol API endpoints |
| API versioning | resourceVersion parameter |
Version in the endpoint URL (e.g. /v4/) |
| Account | Legacy developer account | New account on this portal |
The API Consumer Migration Guide walks you through updating your endpoint URLs and implementing JWT authentication with ready-to-use code samples. New to the platform? Start with the Getting Started Guide.
Endpoint URLs
Your API base URLs change on this platform. You must update your applications to call the new Schiphol API endpoints - the legacy hostnames and paths stop working once the legacy platform is decommissioned. The exact new URL for each API is shown on that API's page in the API catalogue.
API Versioning
API versioning is handled differently here. Instead of the legacy resourceVersion parameter, the API version is part of the endpoint URL (for example /v4/). Target the version directly in the URL and remove any resourceVersion handling from your integration.
Account Migration
On this portal you'll need to register a new account yourself. Public accounts are not migrated automatically - sign up here, then request access to the APIs you use.
Once your account is set up, you may need to re-request access to your APIs to ensure proper setup and security on the new platform. This is a one-time effort.
If you are unable to complete the migration, or if you run into any issues, please reach out to us at api-support@schiphol.nl and we will assist you.
Next Steps
We will continue to send detailed migration instructions and timeline updates by email. Please make sure your contact information is up to date so you don't miss critical announcements.
As part of the migration we will provide you with:
- Detailed migration guides and documentation
- Step-by-step instructions for account creation and API access requests
- JWT token implementation examples and best practices
- Support during the transition period
- Advance notice before the 1 October 2026 decommissioning date
Office Hours & Support
We run office-hours sessions to help you plan and execute your migration and to answer any integration questions.
If you are interested in a dedicated migration office-hours session, please email our support team. If enough people show interest, we will organise one.
Frequently Asked Questions
Do I really have to migrate?
Yes. The legacy platform will be permanently decommissioned on 1 October 2026. Any integration that has not migrated to this portal by then will stop working.
Will my legacy API keys keep working?
Only until the legacy platform is switched off. This platform does not use static API keys - you must switch to JWT (OAuth 2.0) tokens. We strongly recommend migrating well before the deadline.
Can I run both platforms in parallel?
Yes. This portal and the legacy platform run side by side during the migration window, so you can migrate and validate one integration at a time without downtime.
Where do I start?
Create your account here on this portal, then follow the API Consumer Migration Guide to update your endpoints and switch to JWT authentication.
Need Help?
If you are unable to complete the migration or have specific questions about how this change affects your integration, please contact us at api-support@schiphol.nl. You can also browse the guides below or the API catalogue for endpoint details.
Last updated: August 2026