Charging stations

/v2/charging answers from our own copy of the Open Charge Map dataset. It is refreshed on a schedule and served from our database, not from a live call to anyone's API. That is why it stays up when the upstream does not, why every response carries asOf (when the data was last refreshed), and why the same query returns the same answer twice.

Stations near a point

curl "https://api.cardog.app/v2/charging/stations?lat=43.6532&lng=-79.3832&radius_km=10" \
  -H "x-api-key: $CARDOG_API_KEY"

Results are nearest first. radius_km defaults to 10 and caps at 500. limit defaults to 20 and caps at 100.

The default filter hides decommissioned stations

We keep decommissioned stations, because "this charger existed and was retired" is also an answer. 8,116 of 105,985 records are NonOperational. The search default is status=Operational, so you never show a driver a dead charger by accident. Pass status=any (or status=NonOperational) when you want the history.

Filtering by connector

connector takes an OCM ConnectionTypeID, the same numeric vocabulary the connectors[].connectionTypeId field uses. In the data today:

min_power_kw filters on the station's best connector (maxPowerKw). min_power_kw=100 is the practical "DC fast charging only" switch.

One station

curl "https://api.cardog.app/v2/charging/stations/248113" \
  -H "x-api-key: $CARDOG_API_KEY"

The id is the source station id (OCM ChargePoint ID). It is the tail of the station:ocm/248113 ref and of every search hit's links.self.

What this surface does not have

v1's /charging proxied fields we cannot vouch for: photos, rating, network, and support contacts. They are dropped here, not nulled. They are absent from the contract, so nothing pretends to an answer the data does not hold. What remains (connectors with quantity, power, status, usage class, operator, address, coordinates) is normalized and typed.

Requests are metered at 1 credit per request. The rate card is the authority. License terms are in the reference.