Migration Overview
What changes?
If you are already using one of our APIs — Student (previously: Leerlingen), Invoice (previously: Rekeningen), Invoice GraphQL (previously: Rekeningen GraphQl), Staff (previously: Personeel), or Boarding School (previously: Internaat) — only one thing changes:
New endpoint URL — update your base URL to the new endpoint. This includes:
a new host and path prefix
a version segment added to the path (e.g.
students/{version}, invoices/{version}, staff/{version}, …)
The request/response structure of each API remains identical.
Authentication — nothing changes
Authentication works the same as it does today. You already obtain a JWT Bearer token from the identity server and include it on your requests — that does not change.
The identity server URL stays the same: https://www.identityserver.be/connect/token
Authorization: Bearer <your-existing-token>Rate limiting — new behaviour
The gateway now enforces a per-client rate limit across all APIs. New response headers X-RateLimit-Limit and X-RateLimit-Remaining show your remaining quota, and a 429 Too Many Requests is returned when the limit is reached. See the Rate limiting page for headers, retry logic, and the full contract.
Which API are you migrating?
Select your API in the navigation, or jump directly to the relevant migration guide:
Implementation guides (PDF)
The original technical specification for each API is available as a PDF document. These PDFs describe the direct backend API and were written before the API gateway was introduced — use them as a reference for request/response structure, but refer to the migration guides on this portal for the correct endpoint URLs.
REST API - Implementation Guides
Download the Student (Leerlingen), Invoice (Rekeningen), and other API guides from the Informat support page