Discover/rwsverkeersinfo API
live

rwsverkeersinfo APIrwsverkeersinfo.nl ↗

Fetch Dutch traffic peak hour forecasts from Rijkswaterstaat Verkeersinformatie. Get severity levels, congestion summaries, and 15-minute interval graph data per day part.

Endpoint health
verified 3d ago
get_peak_forecast
1/1 passing latest checkself-healing
Endpoints
1
Updated
2mo ago

What is the rwsverkeersinfo API?

The rwsverkeersinfo.nl API exposes one endpoint — get_peak_forecast — that returns the current Dutch traffic spits (peak hour) forecast published by Rijkswaterstaat Verkeersinformatie. Each response includes 7 or more distinct fields per forecast object: a severity level on a 1–4 scale, a plain-text summary, expected congestion in kilometers, and time-series graph data at 15-minute intervals, covering all listed day parts such as morning and evening rush hours.

This call costs1 credit / call— charged only on success
Try it

No input parameters required.

→ api.parse.bot/scraper/6211231b-86fc-4c78-90b0-5e5bbb65290c/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/6211231b-86fc-4c78-90b0-5e5bbb65290c/get_peak_forecast' \
  -H 'X-API-Key: $PARSE_API_KEY'
Python SDK · recommended

Typed, relational, agent-ready

A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.

  • Fully typed · autocompletes
  • Objects link to objects
  • Typed errors & pagination

Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:

uv add parse-sdk
uv run parse init
uv run parse add --marketplace rwsverkeersinfo-nl-api

uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.

"""Walkthrough: RWS Verkeersinformatie — Dutch traffic peak-hour forecasts."""
from parse_apis.rwsverkeersinfo_nl_api import RwsVerkeersinfo, ParseError

client = RwsVerkeersinfo()

# Fetch all current peak-hour forecasts (typically morning + evening).
try:
    for forecast in client.forecasts.list(limit=10):
        print(f"{forecast.date} {forecast.daypart_label}: severity {forecast.severity}/4")
        print(f"  {forecast.severity_label}")
        print(f"  {forecast.summary[:100]}")

        # Show first few graph data points for expected vs average traffic intensity.
        for point in forecast.graph_data[:3]:
            print(f"    {point.time} — expected: {point.expected}, average: {point.average}")
except ParseError as e:
    # Upstream page structure changed or extraction failed.
    print(f"Parse error ({e.code}): {e}")

print("exercised: forecasts.list / Forecast fields / GraphPoint fields")
All endpoints · 1 totalmissing one? ·

Returns the current traffic peak (spits) forecast for all listed day parts (typically morning and evening). Each forecast includes a severity level (1-4), a textual summary, an explanation of expected congestion in kilometers, and 15-minute interval graph data showing expected and average traffic intensity values. No input parameters; the endpoint always returns the latest published forecast.

Input

No input parameters required.

Response
{
  "type": "object",
  "fields": {
    "title": "Page title string",
    "forecasts": "Array of forecast objects, one per listed day part (e.g. morning, evening)",
    "disclaimer": "General disclaimer text about the page"
  },
  "sample": {
    "data": {
      "title": "Spitsverwachting",
      "forecasts": [
        {
          "id": 3229,
          "date": "2026-08-17",
          "daypart": "AM",
          "summary": "De vakantie is voorbij in de regio Noord. Waar in de afgelopen weken vrijwel geen sprake was van een echte ochtendspits, zullen de spitsen nu weer langzaam op gang komen. Houd hier rekening mee als je op pad gaat.",
          "severity": 2,
          "graph_data": [
            {
              "time": "06:00",
              "average": 0,
              "expected": 0
            },
            {
              "time": "06:15",
              "average": 14,
              "expected": 14
            },
            {
              "time": "08:30",
              "average": 80,
              "expected": 80
            },
            {
              "time": "09:45",
              "average": 25,
              "expected": 25
            }
          ],
          "daypart_label": "ochtend",
          "severity_label": "Lichte spits (light peak)",
          "severity_explanation": "Bij een lichte spits verwachten we tot 200 kilometer file op de rijkswegen."
        }
      ],
      "disclaimer": "Op deze pagina vind je de spitsverwachtingen van Rijkswaterstaat Verkeersinformatie."
    },
    "status": "success"
  }
}

About the rwsverkeersinfo API

What the API returns

The single get_peak_forecast endpoint returns a structured JSON response with three top-level fields: title (the page title string from the source), disclaimer (the general disclaimer text associated with the forecast page), and forecasts — an array of forecast objects, one per day part listed on the page (typically morning and evening rush hour).

Each object in the forecasts array carries a severity level (integer 1–4, where higher numbers indicate more severe congestion), a textual summary describing expected traffic conditions, an explanation that quantifies expected congestion in kilometers, and 15-minute interval graph data visualising predicted traffic intensity across the day part window.

Inputs and freshness

get_peak_forecast accepts no input parameters. The response reflects whatever forecast Rijkswaterstaat Verkeersinformatie is currently publishing for the day, so results vary by time of day and day of week. There are no filters for specific roads, provinces, or routes — the endpoint returns all day-part forecasts as a single payload.

Coverage scope

The data covers the national-level spits forecast for the Netherlands, as published by Rijkswaterstaat. The severity scale and textual content match what appears on the rwsverkeersinfo.nl spitsverwachting page. Individual road incidents, real-time road closures, and historical forecast archives are not part of this endpoint's response.

Reliability & maintenanceVerified

The rwsverkeersinfo API is a managed, monitored endpoint for rwsverkeersinfo.nl — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when rwsverkeersinfo.nl changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.

This isn't an official rwsverkeersinfo.nl API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.

Last verified
3d ago
Latest check
1/1 endpoint passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Display morning and evening rush-hour severity badges in a Dutch commuter app using the 1–4 severity level field.
  • Plot expected congestion intensity over time using the 15-minute interval graph data for data journalism or dashboards.
  • Send automated Slack or push notifications when the severity level exceeds a threshold before weekday rush hour.
  • Feed the congestion-in-kilometers summary into a route-planning tool to advise whether to depart early or late.
  • Archive daily forecast objects to analyse seasonal patterns in Dutch rush-hour predictions.
  • Embed the plain-text summary and disclaimer into a travel planning newsletter covering Dutch road conditions.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo2005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min
Team$300/mo20,000300 req/min
Company$1,000/mo100,000500 req/min

Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does Rijkswaterstaat offer an official developer API for traffic data?+
Rijkswaterstaat publishes open traffic data through the Nationaal Dataportaal Wegverkeer (NDW) at ndw.nu, which offers feeds for road incidents and counts. The rwsverkeersinfo.nl spitsverwachting forecast page does not have a documented public API of its own; this Parse API gives you structured access to that forecast data.
What does the severity level field represent?+
The severity field inside each forecast object is an integer from 1 to 4. A value of 1 indicates minimal expected congestion; 4 indicates the most severe peak-hour conditions. The level corresponds to what Rijkswaterstaat Verkeersinformatie displays on the spitsverwachting scale. The textual summary and congestion-in-kilometers explanation fields provide the human-readable description behind that number.
Does the API cover individual road incidents or specific highway delays?+
Not currently. The get_peak_forecast endpoint returns the national-level day-part forecast — severity, summary, congestion volume, and graph data — but does not break down predictions by road, highway number, or region. You can fork this API on Parse and revise it to add an endpoint targeting incident-level or route-specific data from other Rijkswaterstaat sources.
Can I retrieve historical spits forecasts from previous days?+
Not currently. The endpoint returns the forecast that is live at the time of the request. There is no date or offset parameter for retrieving past forecasts. You can fork this API on Parse and revise it to add persistence or a historical data endpoint if your use case requires archival data.
How many day parts does a typical response include?+
The forecasts array contains one object per day part listed on the source page. On a typical weekday this is two entries — morning (ochtendspits) and evening (avondspits). On weekends or public holidays the array may have fewer entries or different labels, depending on what Rijkswaterstaat is currently publishing.
Page content last updated . Spec covers 1 endpoint from rwsverkeersinfo.nl.
Related APIs in Maps GeoSee all →
nsinternational.nl API
Access data from nsinternational.nl.
ratp.fr API
Monitor real-time traffic conditions and service disruptions across Paris's RATP and RER networks to plan your commute efficiently. Get instant updates on line statuses, delays, and service alerts for all metro and regional rail lines.
9292.nl API
Plan trips across Dutch trains, buses, trams, metros, and ferries by searching for locations and getting detailed journey information including travel times and costs. Find the best routes through the Netherlands' public transport network with real-time trip planning.
ariasurf.com API
Plan your next surf session by searching thousands of worldwide surf spots and accessing detailed hourly forecasts with swell conditions, wind patterns, tidal information, and water temperature data. Get real-time predictions to catch the perfect waves whenever and wherever you want to surf.
weatherforecast.com API
Get detailed 12-day weather forecasts for any location worldwide, with temperature, wind, rain, humidity, and UV index data updated three times daily. Search locations and retrieve comprehensive weather information suitable for travel planning, research, and general forecasting needs.
tomtom.com API
Get TomTom Traffic Index congestion rankings for cities worldwide or within a specific country, and retrieve detailed traffic metrics for a given city (including AM/PM and monthly trends).
magicseaweed.com API
Search for surf spots worldwide and get detailed forecasts including wave height, wind conditions, tide times, and weather data to plan your next session. Discover popular breaks and access real-time conditions for any location to catch the best waves.
queue-times.com API
Monitor real-time wait times, crowd levels, and historical data across 130+ theme parks worldwide to plan your visits and avoid peak hours. Get daily statistics and predictions to make informed decisions about when and where to experience attractions with minimal wait times.