The Netherlands' National API Strategy Frank Terpstra, Senior Advisor at Geonovum

1. The Netherlands' National API
Strategy
11-12-2019 APIdays

2. Kennisplatform APIs
(API knowledge platform)

3. Bottom up initiative
 Started on the work floor of several government organisations
 In 2018 we launched with a manifesto :
– To exchange knowledge on APIs between government organisations,
their (IT) suppliers and users
– To formulate a strategy that lets (public sector)APIs meet user needs
– To improve interoperability and usability of public sector APIs by
establishing an API strategy
– First concept done end of 2018
– API strategy formalised an widely used by the end of 2019
 Manifesto supported by many government organizations and
companies

4. API strategy: Working groups
Communication &
government policy
User requirements
API Designrules
Security
Architecture
Editor

5. API strategy: Working groups
What problem do we solve?
- what are APIs & how do they help solve this problem?
- when are APIs relevant for my organisation?
- Examples of API usage in the Netherlands
Communication &
government policy
User requirements
API Designrules
Security
Architecture
Editor

6. API strategy: Working groups
User is first and foremost a Developer!
- what does a Developer need?
- Persona’s
- Reccomendations
Communication &
government policy
User requirements
API Designrules
Security
Architecture
Editor

7. API strategy: Working groups
Rules and Principles!
- Normative standard
- General REST principles, naming conventions
versioning,..
- Extensions (non normative, work in progress)
Communication &
government policy
User requirements
API Designrules
Security
Architecture
Editor

8. API strategy: Working groups
Security by Design
- Dutch public sector profile for OAuth (Open Autorisation)
Communication &
government policy
User requirements
API Designrules
Security
Architecture
Editor

9. API strategy: Working groups
- API impact on IT architecture
- Sharing best practices on application architecture
Communication &
government policy
User requirements
API Designrules
Security
Architecture
Editor

10. Timeline
 started in 2018,
 Kickoff 26th April 2018
 Public consultation started February 2019 (ended 27th march)
 Results of Public consultation incorporated in version published
in July 2019
– (including API design rules in English)
 API design rules submitted as national standard (October
2019)
– (editorial changes splitting API strategy in three parts)
 API strategy presented at highest level of Dutch Digital
government (november 2019)

11. Current state of API adoption

12. 30+ APIs conform to “API Designrules”
Digitaal stelsel omgevingswet(DSO):
Informatiehuis Ruimte ruimtelijke plannen opvragen API
Stelselcatalogus muteren API
Stelselcatalogus opvragen API
Omgevingsdocument opvragen API
Omgevingsdocument toepasbaar opvragen API
Omgevingsdocument presenteren API
Regels verifiëren API
Verzoek ophalen API
Activiteiten bepalen API
Werkzaamheden bepalen API
Samengestelde registratie Toepasbare Regels Services API
Conclusie bepalen API
Toelichting ophalen API
Voorschriften bepalen API
Verzoek indienen API
Bevoegd gezag bepalen API
Behandeldienst bepalen API
Behandeldienst configuratie beheren API
Kadaster APIs
BRT API
BRK-DKK API
BAG API
DUO RIO metadata API
RCE data API
VNG Zaakgericht werken APIs:
Catalogi API specificatie
Zaken API specificatie
Documenten API specificatie
Besluiten API specificatie
Autorisaties API specificatie
Notificaties API specificatie
Notificaties API specificatie voor consumers
Haal centraal:
BRP-bevragen ingeschreven Persoon
BRK bevragen Kadastraal Onroerende Zaken
VNG Open Raads- en Staten informatie
Ministerie van BZK Basisregistratie Ondergrond Bronhouderportaal BRO API (1.0.0)

13. Future work
 Formal approval API design rules as national standard
 Getting attention of policy makers & top level
management
 Completing extensions
 Explore ODATA, GraphQL, gRPC
 Connecting with government IT architecture initiatives
(NORA)
 European cooperation?

15. BAG API
Kadaster
The BAG API improves the accessibility of the Key registry Addresses and
Buildings enormously – not just for geo/GIS experts, but for everyone. Via this
API one can easily obtain information on addresses and buildings. This data is
very relevant for the “energy transition” for example .

16. Kadaster when receiving the award: “within the first year the BAG
API exceeded the number of requests of all other distribution
methods over the previous seven years combined”
Update 6 months later: “we have received so many request, we
have stopped counting”

17. Online information
General(in Dutch)
 https://apigov.nl
Main Github (mixed Dutch & English)
 https://github.com/Geonovum/KP-APIs
Dutch profile OAuth (in English)
 https://docs.geostandaarden.nl/api/oauth/
API strategy part I(in Dutch)
 https://geonovum.github.io/KP-APIs/
API strategy part IIa: API designrules (in English)
 https://geonovum.github.io/API-Designrules/
APY strategy part IIb API designrules extensions (in English)
 https://geonovum.github.io/KP-APIs/API-strategie-extensies/

18. Thank You!