How do I search for charging stations near me?
GET /api/v1/ev-charger/stations?lat=40.7128&lon=-74.0060&radius_km=10 returns stations within that radius. Optional filters are plug_type, level, network, and open_now.
EV Charger API
Coordinate Search
Network + Plug Reference
Placeholder Status
EV charging stations. Find them fast.
Search charging stations by coordinates with radius, plug-type, level, and network filters, then look up station details by ID. Occupancy status routes exist as placeholders until live status is wired.
lat/lon · searchNetworks · plug typesStatus · placeholderGET + POST · batch
Find stations near any city.
This calls the live EV Charger API. Pick a city to search for stations within a 10km radius.
Request builder
Coordinates in, stations out.
GET /ev-charger/stations
Reference and batch endpoints
GET /networks and /plug-types return distinct reference values. GET /status/batch or POST the same route with a station_ids array returns status for up to 50 stations.
Output preview
Live response from the API, plus the exact request to reproduce it.
Loading live station data...
Why EV Charger API
Charging data, wherever you are.
Coordinate-based search
Search stations by lat/lon with a configurable radius, defaulting to 10km.
Plug type and level filters
Narrow results by plug_type (e.g. CCS) or charging level to match your vehicle's connector.
Network filtering
Filter stations by network name substring, e.g. EVgo or ChargePoint.
Station detail lookup
GET /stations/:id returns full station details or a 404 with search guidance when not found.
Batch status checks
GET or POST /status/batch accepts up to 50 station IDs and returns placeholder occupancy until live status is wired.
Networks, plug types, and levels reference
GET /networks, /plug-types, and /levels return distinct reference values for building filters.
/api/v1/ev-charger
Endpoints, at a glance.
Coordinate-based station search, station detail lookup, network/plug/level reference data, single-station status, and batch status checks.
GET/api/v1/ev-charger/stations
Station search
Coordinate-based station search. Requires lat and lon. Optional radius_km, plug_type, level, network, and open_now.
GET/api/v1/ev-charger/stations/search
Address search
Requires address. Currently returns HTTP 501 with guidance to geocode and use /stations.
GET/api/v1/ev-charger/stations/:id
Station detail
Full station details by ID, or 404 with search guidance when not found.
GET/api/v1/ev-charger/networks
Networks
Distinct charging network values.
GET/api/v1/ev-charger/plug-types
Plug types
Distinct plug-type values.
GET/api/v1/ev-charger/levels
Levels
Charging-level descriptions (1, 2, and 3).
GET/api/v1/ev-charger/status/:id
Station status
Placeholder status payload for a single station ID. Real-time occupancy is not live yet.
GET/api/v1/ev-charger/status/batch
Batch status (GET)
Comma-separated station_ids, up to 50 IDs. Returns placeholder status until live occupancy is wired.
POST/api/v1/ev-charger/status/batch
Batch status (POST)
JSON body { "station_ids": ["..."] }, up to 50 IDs. Same placeholder status shape as GET.
| Parameter | Type | Required | Description |
|---|---|---|---|
| lat / lon | number | yes | Coordinates for /stations, e.g. 40.7128 / -74.0060. |
| radius_km | number | no | Search radius in kilometers. Defaults to 10. |
| plug_type | string | no | Filter by plug type, e.g. CCS or CHAdeMO. |
| level | integer | no | Filter by charging level: 1, 2, or 3. |
| network | string | no | Case-insensitive network name substring, e.g. EVgo. |
| open_now | boolean | no | true applies 24/7-hours filtering. |
| address | string | search | Address input for /stations/search. Currently returns HTTP 501. |
| id | string | yes* | Station ID path parameter for /stations/:id and /status/:id. |
| station_ids | string / array | yes* | Comma-separated (GET) or array (POST), up to 50 IDs, for /status/batch. |
Address-based search (/stations/search) currently returns HTTP 501. GET /status/:id and /status/batch return placeholder status until live occupancy is available.
Error reference
Failures you can plan for.
Address-based search always returns a 501 today — use coordinate-based search instead.
400Validation Error
Missing lat/lon, missing address on the search route, or invalid/missing station_ids.
400Batch Limit Error
Batch status requested with more than 50 station IDs.
401Authentication Error
Missing or invalid gateway API key. Send x-api-key or api_key with every request.
404Not Found
Station ID not found for the station details route.
500Internal Server Error
Internal DB/service failure while processing station or status requests.
501Not Implemented
Address-based search (/stations/search) is not yet implemented.
Example validation error (400)
{
"error": "Missing required query parameters: lat, lon"
}FAQ
API questions developers ask first.
Can I look up a specific station's details?
Yes. GET /stations/:id returns full station details, or a 404 with search guidance if the station ID does not exist.
How do I check status for one station or many?
GET /status/:id currently returns a placeholder payload — real-time occupancy is not live yet. GET /status/batch?station_ids=12345,67890 or POST the same route with { "station_ids": [...] } accepts up to 50 IDs and returns the same pending-status shape.
Is address-based search supported?
GET /stations/search requires an address query parameter, but currently returns HTTP 501 with guidance to geocode first and use coordinate search at /stations.
How do I authenticate requests?
Send your Datpaq API key as an x-api-key header or an api_key query parameter. Keys are created in the Datpaq dashboard and a free tier is included.
Add EV charging data in one request.
Coordinate-based station search plus network, plug-type, and charging-level reference data. Status routes return placeholder occupancy until live status is wired.