...
Therefore we recommend switching to the renewed API & changing the authentication in one go.
Note |
---|
On the renewed API rate limiting is applied. Each client is allowed to perform 1800 req/min. |
TL;DR for CCG with JWK
Beta | Production |
|
|
Set up clients in ACM
The current Geosecure clients are being phased out.
...
More information about moving from Geosecure clients to ACM clients: https://confluencevlaamseoverheid.voalm.vlaanderen.beatlassian.net/wiki/display/GAEP/Scenario%2527s%2Bvoor%2Boverschakeling%2Bvan%2Bde%2BAPI-clients
More information about managing Client Credential Grant clients in ACM: https://confluencevlaamseoverheid.voalm.vlaanderen.beatlassian.net/wiki/display/GAEP/Module%2BOAuth%2BClient%2BCredentials%2BGrant%253A%2BAPI-Client%2Bbeheren
Authenticate on the GIPOD API with an ACM token
...
The renewed GIPOD API endpoint ( https://gipod.api.vlaanderen.be ) will work with both Geosecure and ACM authentication, but the existing GIPOD API endpoint ( https://private-api.gipod.vlaanderen.be ) will only work with Geosecure authentication.
...
Questions about converting Geosecure clients to ACM clients: uitfaseringgeosecure@vlaanderen.be
Questions about managing ACM clients: integraties@vlaanderen.be
Questions about the GIPOD API: digitalgipod@athumi.vlaanderen@vlaanderen.beeu