Skip to content
Branch: master
Find file Copy path
Find file Copy path
2 contributors

Users who have contributed to this file

@joepio @jurrian
51 lines (32 sloc) 2.33 KB

Open Raadsinformatie API docs

Open Raadsinformatie (ORI) aims to make governmental decision making more transparent by aggregating and standardizing meeting & decision data. Currently, the API includes data from more than 110 municipalities (gemeenten) and 5 provinces.


The ORI API has several endpoints for different goals:

  • the REST API for fetching individual resources
  • an Elastic endpoint for full-text search

If you want to know how to query these endpoints, check out example_requests.http.



The ORI REST API is hosted at the subdomain. Use this to get individual meetings / motions / agenda items / persons / etc, such as It is by far the most performant API for ORI, as it stores the various representations (TTL, RDF/XML, N3, N-Triples, JSON-LD) as static files. Since this API serves RDF, it might be a good idea to get familiar with linked data.

Read more about the REST API in its github repo and its documentation..



This is an ElasticSearch endpoint. Elastic has powerful full-text search capabilities.

The repo for this API can be found here. Read the Elastic v7.0 docs for more information. Only specific Elastic features (endpoints) are publicly available. This is to prevent (malicious or accidental) write / remove commands.


Who's behind this project?

ORI was initiated by the Open State Foundation. VNG Realisatie is the main funder. Ontola / Argu is responsible for the technology.

I have feedback / question about one of the API's

For technical questions, please create an issue in the aforementioned Github repos. If you have general questions about Open Raadsinformatie, get in touch with project leader Sander Bakker

You can’t perform that action at this time.