Reference · built on requestCommons signalTransit, roads & mobility

Open Charge Map API

Global registry of EV charging locations with connections, operators, and status, contributed and imported, from Open Charge Map.

Request accessPricing ↗

About

Open Charge Map is a non-commercial, non-profit registry of electric vehicle charging locations, hosted and supported by a community of businesses, charities, and developers. Its API version 3.1 at api.openchargemap.io/v3 returns sites as POI records: address, coordinates, operator, usage type, status type, cost text, and one ConnectionInfo entry per port with connection type, power in kW, current type, and quantity. Reference lists for those IDs come from /referencedata. Data comes from user contributions, licensed CC BY 4.0, and from imported third-party providers whose own terms apply. Every result names its DataProvider so you can show the required attribution.

An operator uses it to find chargers around a route, depot, or property in countries other sources leave out, and to compare what a site reports about its ports before proposing a stop.

This is a reference listing. It documents what Fibric would read from Open Charge Map API and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Sites from GET /poi, filtered by countrycode, latitude, longitude, distance, distanceunit, boundingbox, polygon, or polyline with distance
  • Per POI: ID, UUID, AddressInfo, OperatorID, UsageTypeID, UsageCost, StatusTypeID, DateLastStatusUpdate, DateLastConfirmed, NumberOfPoints, and DataQualityLevel
  • Connections per site: ConnectionTypeID, StatusTypeID, PowerKW, Amps, Voltage, CurrentTypeID, Quantity, and an optional operator Reference
  • Filters by operatorid, connectiontypeid, usagetypeid, statustypeid, dataproviderid, and opendata=true for openly licensed records only
  • Change tracking with modifiedsince, greaterthanid, and sortby modified_asc or id_asc; output as json, geojson, xml, csv, or kml
  • Reference data from GET /referencedata: ConnectionTypes, Operators, Countries, UsageTypes, StatusTypes, CurrentTypes, and DataProviders with their IDs
  • UserComments and MediaItems per site when includecomments=true, and the computed IsRecentlyVerified flag

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Find a charger where no national dataset reaches

    Charge Readiness queries /poi around a vehicle's next stop in any country, checks StatusType and UsageType for each site, and proposes the stop that matches the vehicle's connection type.

    With Charge Readiness

  • Re-plan a route around chargers

    Route Resequence passes the planned path as a polyline with a search distance and proposes a stop order that puts a compatible charger inside the vehicle's remaining range.

    With Route Resequence

  • Tell a guest where to charge tonight

    Arrival Prep reads sites within a short distance of a property, their UsageCost text and membership requirements, and proposes a line for the pre-arrival message.

    With Arrival Prep

  • Track what changed near a depot

    Depot Charging polls /poi with modifiedsince and sortby=modified_asc for a bounding box around the yard and proposes an update to the off-site charging options it offers drivers.

    With Depot Charging

Requirements

  • A free Open Charge Map API key from Register An Application under my apps
  • A custom HTTP user-agent and a client value so Open Charge Map can tell your app from other callers
  • A latitude and longitude, bounding box, or polyline for each query, plus operatorid or connectiontypeid values from /referencedata to narrow results
  • Visible attribution of each result's DataProvider and its license terms to end users, as the terms require
Authentication
A free Open Charge Map API key, registered under my apps in your profile after sign-in, sent as the case-sensitive X-API-Key header or the key query parameter, with a custom user-agent.

Limits

  • No service level agreement. Open Charge Map may ban callers that send excessive or duplicate queries; high-volume users should run a mirror
  • Licenses are mixed. User-contributed data is CC BY 4.0; imported provider data keeps the provider's terms, so filter opendata=true for open data only
  • StatusType says whether a site or port is generally operational; the POI model carries no current occupancy state
  • This listing is read-only. The API also accepts comments, check-ins, and photos from authenticated users; those calls are not part of this signal

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request Open Charge Map API ↗

Questions and answers

How do I get an API key and where does it go?
Sign in to openchargemap.org, open my apps from the my profile menu, and choose Register An Application. Send the key as the X-API-Key header, which is case sensitive, or as the key query parameter. Set a custom user-agent as well.
What does a compact response leave out?
With compact=true the API returns reference IDs such as UsageTypeID and DataProviderID instead of the expanded UsageType, StatusType, DataProvider, OperatorInfo, and SubmissionStatus objects. AddressInfo is still included. Hydrate the IDs from /referencedata. verbose=false also drops null fields.
Who owns the data and what must I show?
User-contributed data that Open Charge Map redistributes is licensed CC BY 4.0. Data imported from third-party providers stays under each provider's copyright and terms. Each record names its DataProvider, and the terms require that attribution and license terms be visible to your end users.
Ask about Open Charge Map API

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This Commons signal listing is developed, published, and supported by Fibric. It reads public data published by Open Charge Map (api.openchargemap.io). Upstream agencies and projects are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy