# GetApi NDW Emissiezone by ID

> GetApi NDW Emissiezone by ID is a paid API for AI agents from api.getapi.nl, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-11).

Retrieves detailed information about a specific Dutch emission zone (emissiezone) by its unique identifier, including geometry, zone type, validity period, and vehicle restrictions.

## Facts

- Endpoint: GET https://api.getapi.nl/api/v1/ndw/emissiezones/%7Bid%7D
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/getapi-ndw-emissiezone-by-id-e3576103
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hmdZiufsgXg0-h3zQwQtw

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability getapi-ndw-emissiezone-by-id-e3576103
```

Example prompt: Can you look up the details for Dutch emission zone NL_ZEZ_AMS_001, including its geographic boundaries, which vehicles are restricted, and whether it's currently active?

## When to prefer this

Use this endpoint when you have a specific NDW emission zone ID and need full structured details — geometry, restrictions, and validity — in a single call. Prefer this over a geospatial search endpoint when the zone ID is already known (e.g. from a prior list/search call). Ideal for compliance checks, route planning systems, or map rendering pipelines that operate on the Netherlands road network.

## Known failure modes

- Unknown or invalid zone ID returns found:false with no result object
- Malformed ID format may return a 400 or 404 error
- Zone ID for a non-Dutch or unsupported region returns not found
- Expired or future zones may be returned but flagged via valid_from/valid_until fields
- Payment failure (x402) blocks the request before any data is returned

## How this service works

Ontdek, test en integreer krachtige API's voor web scraping, e-mailvalidatie, geolocatie
    en meer. Gratis starten.

## Output

A JSON object with a 'found' boolean and a 'result' object containing: zone ID, city, human-readable name, GeoJSON Polygon geometry with coordinate arrays, zone type (e.g. 'zero_emission'), ISO 8601 valid_from and valid_until timestamps, and an array of vehicle_restrictions specifying fuel_type, vehicle_type, and emission_class combinations that are restricted within the zone.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "found": true,
  "result": {
   "id": "NL_ZEZ_AMS_001",
   "city": "Amsterdam",
   "name": "Amsterdam Zero Emission Zone Centrum",
   "geometry": {
    "type": "Polygon",
    "coordinates": [
     [
      [
       4.89,
       52.37
      ],
      [
       4.91,
       52.37
      ],
      [
       4.91,
       52.38
      ],
      [
       4.89,
       52.38
      ],
      [
       4.89,
       52.37
      ]
     ]
    ]
   },
   "zone_type": "zero_emission",
   "valid_from": "2025-01-01T00:00:00+00:00",
   "valid_until": null,
   "vehicle_restrictions": [
    {
     "fuel_type": "diesel",
     "vehicle_type": "truck",
     "emission_class": "Euro6"
    }
   ]
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/getapi-ndw-emissiezone-by-id-e3576103/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.getapi.nl](https://www.zero.xyz/host/api.getapi.nl/llms.txt)