# 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 — 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. Its commercial API family, Zapmap Spark (Search API, Plan API, Pay API), is described on marketing pages only: there is no developer portal, no API reference, no published base URL, no published authentication scheme, no machine-readable specification and no self-serve signup. Every route to access runs through a sales contact form and a data licence. This file is GENERATED by API Evangelist from the catalog entry and the artifacts in this repository. Zapmap publishes no llms.txt of its own (https://www.zapmap.com/llms.txt returns HTTP 403). ## APIs (commercial, contact-sales only, no published technical surface) - [Zapmap Spark Search API](https://www.zapmap.com/for-business/products/zapmap-spark/search-api): Charge point search over 50,000+ public charging locations in the UK and Ireland — location, live availability, kWh pricing, CPO network, power output, site facilities. No base URL, endpoints, auth scheme or spec published. - [Zapmap Spark Plan API](https://www.zapmap.com/for-business/products/zapmap-spark/plan-api): EV route planning with configurable charging-stop selection (price, facilities, deviation). No technical surface published. - [Zapmap Spark Pay API](https://www.zapmap.com/for-business/products/zapmap-spark/pay-api): Cross-network charging session start/stop with live cost, time and kWh across 10,000+ Zap-Pay enabled charge points. No roaming protocol named (no OCPI/OCPP reference anywhere). - [Zapmap Spark (family overview)](https://www.zapmap.com/for-business/products/zapmap-spark) ## Specs None. No OpenAPI, Swagger, GraphQL schema, AsyncAPI, Postman collection, WSDL or JSON Schema is published on any Zapmap host. This is a verified absence, re-probed 2026-07-27. ## Artifacts in this repository - [Authentication profile](authentication/zapmap-authentication.yml): observed auth model of the undocumented api.zap-map.com/v5 client API (X-Api-Key header + bearer user token). No credential values recorded. - [API conventions](conventions/zapmap-conventions.yml): versioning, response/error envelope, health endpoint, and the observed path+method inventory of the first-party client API. - [Error codes](errors/zapmap-error-codes.yml): the proprietary {success, resources, notices[]} error envelope and observed HTTP conditions. - [Lifecycle](lifecycle/zapmap-lifecycle.yml): versioning, and the verified absence of a status page, SLA, changelog and deprecation policy. - [Conformance](conformance/zapmap-conformance.yml): standards assessed — OCPI, OCPP, ISO 15118, OAuth 2, OIDC, RFC 9457, RFC 9116 all absent. - [Well-known index](well-known/zapmap-well-known.yml): every /.well-known/ probe and its status. No document is served. - [Domain security](security/zapmap-domain-security.yml): TLS 1.3, HSTS, DNSSEC, SPF and DMARC (p=reject) on zapmap.com. - [Review](review.yml): the full API Evangelist review — mandate analysis, access gate, data licensing, and every probed URL with its HTTP status. ## Access - [Contact / sales form](https://www.zapmap.com/contact) — the only documented route to a Spark credential; insights@zapmap.com for data enquiries. - [Data licensing](https://www.zapmap.com/data-licensing) — sui generis database rights asserted; express written permission required for substantial reuse; Open Charge Map (CC BY-SA 4.0) and OGL v3.0 subsets acknowledged. - [Data and Insights products](https://www.zapmap.com/for-business/products/data-and-insights) — the paid Locations, Utilisation and EV Driver Insights suite. ## Company - [Website](https://www.zapmap.com/) - [News](https://www.zapmap.com/news) - [EV statistics](https://www.zapmap.com/ev-stats) — free HTML charge point counts, charging price index and market stats. Web pages and PDFs, not a machine-readable feed. - [Help centre](https://help.zapmap.com/support/home) — consumer support, not developer documentation. - [Terms](https://www.zapmap.com/terms) - [Privacy policy](https://www.zapmap.com/privacy-policy) ## Notes for agents - There is no public Zapmap API you can sign up for. Do not attempt to construct requests against api.zap-map.com — it is Zapmap's own credential-gated client backend, not a third-party product, and every path answers 401 "Missing API Key" without a Zapmap-issued credential. - The UK Public Charge Point Regulations 2023 oblige charge point OPERATORS (not Zapmap) to publish open data. If you need open EV charging data for the UK, go to the operators or to Open Charge Map, not to Zapmap.