Luchtmeetnet API

Beginner's Pick Environment / No Auth Required Beginner HTTPS
Free to Use
48 D
Measured Score 0 50 100 Speed 5/30 Consistency 4/20 Security 20/20 Browser access 15/15 Transparency 4/15 TESTED 2026-08-10

Overview

Luchtmeetnet API provides real-time and predicted air quality measurements from the official Dutch national air quality monitoring network (RIVM). It is completely free with no authentication required, covering pollutants like NO2, PM10, PM2.5, and ozone across hundreds of stations in the Netherlands. Developers can fetch station data, component measurements, and LKI (air quality index) values with simple GET requests.

Beginner Tip

No API key is needed — just browse the available stations first using the /stations endpoint, then use a station number to fetch current measurements. The API returns metric-based pollution data, so check the Luchtmeetnet docs for the list of supported component codes like "NO2" or "PM25".

Measurement Record

What actually happened when we called this API from our own infrastructure. Every value below was recorded by the request, not copied from the provider's documentation.

Request
GET https://api.luchtmeetnet.nl/open_api/stations?organisation_id=1
Result
HTTP 200 · application/json · 888 bytes
Response time
561 ms (median of 3) · fastest 291 ms
Transport
TLSv1.3 · TLS_AES_128_GCM_SHA256 · certificate issued by Amazon
Browser CORS
Allowed — Access-Control-Allow-Origin: *
Recorded
2026-08-10

Fields Returned

Top-level fields present in the response we captured, with the type and value we actually received.

Field Type Value received
number string NL01912
location string Ridderkerk-Voorweg

Captured Response

Captured from a real request to https://api.luchtmeetnet.nl/open_api/stations?organisation_id=1 on 2026-08-10. Long arrays and nested objects are truncated to keep the shape readable.

JSON Response · Captured
{
  "pagination": {
    "last_page": 1,
    "first_page": 1,
    "prev_page": 1,
    "current_page": 1,
    "page_list": [
      1
    ],
    "next_page": 1
  },
  "data": [
    {
      "number": "NL01912",
      "location": "Ridderkerk-Voorweg"
    }
  ]
}

Field Reference

data List of station or measurement objects returned by the query
pagination Pagination metadata including total record count and current page information

Implementation Example

Calls a real endpoint of this API. Replace any placeholder credentials with your own key.

Request
const url = "https://api.luchtmeetnet.nl/open_api/stations?organisation_id=1";
const response = await fetch(url);
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

How This API Fails

We deliberately sent this API a broken request and recorded exactly what came back on 2026-08-10. Knowing the shape of an error before you hit it makes error handling much easier to write.

HTTP 404 Requesting a path that does not exist application/json
{
  "reason": "not_found",
  "message": "Not Found"
}
HTTP 400 Sending an invalid value for "organisation_id" application/json
{
  "reason": "validation_error",
  "message": "Errors found during request validation",
  "errors": [
    {
      "reason": {
        "constraint": "type_error.integer",
        "requirement": null
      },
      "message": "value is not a valid integer",
      "field": "organisation_id"
    },
    {
      "reason": {
        "constraint": "type_error.none.allowed",
        "requirement": null
      },
      "message": "value is not none",
      "field": "organisation_id"
    }
  ]
}

Common Errors & Troubleshooting

Generated guidance based on this API's documentation, not observed by us. Treat it as a starting point and check against the provider's own error reference.

404 Not Found The station number or component code used in the URL does not exist
First query /stations to get valid station numbers, then use those exact values in measurement endpoints
Empty data array No measurements are available for the requested time range or component at that station
Try a recent time window (last 1 hour) and verify the station reports the specific component you are querying
Rate limit / 429 Too many requests sent in a short period
Add a short delay between requests when iterating over multiple stations; cache responses where possible

Measured Score Breakdown

Live HTTP request to the API endpoint

Speed 5/30
Consistency 4/20
Security 20/20
Browser access 15/15
Transparency 4/15
Endpoint Response Time 561ms

Fully tested on Aug 10, 2026

Technical Specifications

Auth No Auth
HTTPS REQUIRED
CORS UNKNOWN
Category Environment
Difficulty Beginner
Endpoint last called: 2026-08-10

Related Tags

Similar APIs

View All →