# GetApi NDW EV Charging Point Lookup

> GetApi NDW EV Charging Point Lookup 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-15).

Retrieves real-time status and details for a specific EV charging point (laadpunt) in the Netherlands by its unique station ID.

## Facts

- Endpoint: GET https://api.getapi.nl/api/v1/ndw/laadpunten/%7Bid%7D
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/getapi-ndw-ev-charging-point-lookup-c362011d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MeCPz4x80gdMLtwaYy5n4

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-ev-charging-point-lookup-c362011d
```

Example prompt: Can you check if the EV charging station with ID NL*EVI*E123456*1 is currently available and tell me what connector types it supports?

## When to prefer this

Use this endpoint when you have a specific Dutch EV charging station ID (in EVSE/NDW format like NL*EVI*E123456*1) and need its current availability status, location details, and connector types. Prefer this over a search/list endpoint when you already know the exact station identifier and need precise, real-time data for a single point.

## Known failure modes

- Station ID not found: found=false with no result object
- Invalid or malformed ID format causes 400 error
- Station data temporarily unavailable from NDW source
- Network timeout if NDW upstream is slow
- Missing or expired payment header returns 402 Payment Required

## How this service works

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

## Output

Returns a JSON object with found status and, if found, a result object containing: station ID, city, name, real-time availability status (e.g. AVAILABLE), street address, latitude/longitude coordinates, operator name, postal code, supported connector types (e.g. Type2, CCS), and the timestamp of the last data update.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "found": true,
  "result": {
   "id": "NL*EVI*E123456*1",
   "city": "Amsterdam",
   "name": "Laadplein Amsterdam Centrum",
   "status": "AVAILABLE",
   "address": "Damrak 1",
   "latitude": 52.3728,
   "operator": "Vattenfall",
   "longitude": 4.8936,
   "postal_code": "1012LG",
   "connector_types": [
    "Type2",
    "CCS"
   ],
   "source_updated_at": "2026-05-14T12:10:00+00:00"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/getapi-ndw-ev-charging-point-lookup-c362011d/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)