Pdok Nl APIs
3 APIs215 Endpoints1 Category
Categories
API Catalog(3 of 3)
Habitatrichtlijn verspreiding van habitattypen WFS
Jentic publishes the only available OpenAPI specification for Habitatrichtlijn verspreiding van habitattypen WFS, keeping it validated and agent-ready. This WFS (Web Feature Service) provides geographic distribution data for habitat types within Natura 2000 areas in the Netherlands, covering the 2007-2012 reporting period. The API exposes 208 endpoints representing individual habitat type distributions and their geographic extent, enabling spatial queries on dry heathlands, wet forests, dune vegetation, salt marshes, pioneer communities, and dozens of other habitat classifications defined under the EU Habitats Directive.
208 endpointsMossel- en oester habitats
Jentic publishes the only available OpenAPI specification for Mossel- en oester habitats, keeping it validated and agent-ready. This PDOK API provides annual survey data of mussel and oyster bank areas on the tidal flats of the Dutch Wadden Sea. The dataset is collected by IMARES on behalf of the Dutch Directorate for Animal Agro-Chains and Animal Welfare, covering the extent and location of shellfish habitats. The API offers listing and individual feature retrieval for mussel and oyster habitat spatial records.
3 endpointsOppervlaktewaterlichamen
Jentic publishes the only available OpenAPI specification for Oppervlaktewaterlichamen, keeping it validated and agent-ready. This PDOK API provides nationwide spatial data for surface water bodies managed by Rijkswaterstaat (RWS), the Dutch national water authority. The dataset represents the spatial foundation for the EU Water Framework Directive (KRW) in the Netherlands, compiled from district-level data as both line and polygon features. It covers rivers, canals, lakes, and other surface water bodies with their official WFD classifications.
4 endpointsConnect Your Agent
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.