Zapmap
Zapmap (Zapmap Limited, company number 05960749, Bristol, United Kingdom) operates the UK's most comprehensive public electric-vehicle charging map and cross-network payment platform, covering 120,000+ charge points across 100+ charge point operators for 1.3 million registered drivers, and holds the Department for Transport contract to act as its electric vehicle chargepoint open data provider. It sits in the e-mobility data layer of the energy value chain, between the charge point operators legally obliged to publish open charge point data under the UK Public Charge Point Regulations 2023 and the drivers, automotive OEMs, fleets, e-mobility providers and government bodies that consume it. Its API posture is honestly commercial and closed: the Zapmap Spark suite (Search, Plan and Pay APIs) is described only on marketing product pages, with no developer portal, no public API reference, no machine-readable specification, no published authentication scheme and no self-serve signup — every route to access runs through a sales contact form and a data licence. The open data mandate in this market binds charge point operators, not Zapmap; the mandated open data that Zapmap aggregates is redistributed to DfT under contract and sold to the rest of the industry through the paid Insights product rather than published as an anonymous open feed. No consumer energy usage or billing API is offered — this is open-data-fed, closed-surface market data, with no consumer data right in play.
Zapmap is tracked in the API Evangelist network. This page is the human-readable profile that sits on top of the machine-readable index we maintain at apis.io.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Zapmap is in the network as a tracked entity. We haven't yet indexed a public API surface for it — when one is published, the artifacts, score, and agent-readiness read will appear here automatically. The source repository is where that profile is built.
← All providers · Data indexed from github.com/api-evangelist/zapmap · machine-readable index on apis.io