HERE EV Migration Guide - Introduction
EV Charge Points API v2 has reached end of life (EOL). This guide explains your migration options and helps you choose the best path based on your current architecture and data needs.
What changes
- EVCP API v2 is deprecated and should be replaced.
- For EV station discovery, use HERE Geocoding and Search API v7 with
show=ev. - For richer EV attributes (for example tariffs and availability predictions), use EV Charge Points API v3 after obtaining a place ID.
Recommended replacement APIs
1) HERE Geocoding and Search API v7 (GS7) for discovery
Use the following endpoints with show=ev:
/browse/discover/lookup
This provides EV charging station search and core EV attributes.
Reference: EV attributes in HERE Geocoding and Search API v7
2) EV Charge Points API v3 for advanced EV details
After you retrieve station place IDs from HERE Geocoding and Search API v7 (or your own search stack), call EVCP API v3 to get advanced EV content such as:
- tariff information
- availability predictions
- additional station-level EV details
Reference: Introduction to HERE EV Charge Points API v3
Migration options
Choose one of the following migration models.
How to choose
- If you only need station discovery and basic EV content, choose Option A.
- If you need advanced EV details and additional capabilities, choose Option B (recommended).
- If you must keep a proprietary search platform, choose Option C.
Migration note
Migration paths vary by customer. Teams already using HERE Geocoding and Search API v7 can usually extend existing calls with show=ev. Teams not yet using HERE Geocoding and Search API v7 can either adopt HERE Geocoding and Search API v7 as the discovery layer or continue with proprietary discovery and integrate EVCP API v3 for advanced EV content.
Feature Comparison Table
| Feature | EV Charge Points API v2 (EOL) | HERE Geocoding and Search API v7 API with show=ev parameter | EV Charge Points API v3 |
|---|---|---|---|
| Schema | Proprietary EMI³-based | Proprietary EMI³-based | OCPI |
| Search | EVCP API v2 | HERE Geocoding and Search API v7 | HERE Geocoding and Search API v7* |
| Basic Place attributes (id, name, lat/lon, opening hours, address, route point) | YES | YES | YES |
| EV Place attributes (accessibility (public/restricted), CPO, eMSP) | YES | YES | YES |
| EVSE attributes (EVSE UID, EVSE ID, payment method) | YES | YES | YES |
| Connector attributes (connector type, format (cable/socket), power, AC/DC, current, voltage) | YES | YES | YES |
| Dynamic Availability status | YES | YES | YES |
| Prices/Tariffs | Ad-hoc only | NO | Ad-hoc, eMSP Subscription |
| Additional EV attributes (restriction reason, parking type, energy mix, floor level, facility type/amenities, nearby places, last successful charge timestamp) | NO | NO | YES |
| Truck and 2-wheeler categories | NO | YES | YES |
| V3 Truck Add-on: Truck attributes (light/medium/heavy, dimensional restrictions (L,W,H), weight limit, pull-through, trailer permitted) | NO | NO | YES |
| V3 Predictions Add-on: Premium (add-on) (availability/wait time predictions, busy times) | NO | NO | YES |
* Search can also be implemented by the customer based on an EV Charge Points Static product, see Access the static EV data layer.
Option A: 1 API (Basic content)
HERE Geocoding and Search API v7 API with EV add-on
Use only HERE Geocoding and Search API v7 with show=ev when your use case needs EV filtering and basic EV charging station attributes.
Best for:
- straightforward station discovery
- lightweight integrations
- replacing EVCP v2 with minimal architecture change
Option B: 2 APIs (Advanced content)
HERE Geocoding and Search API v7 API + EVCP API v3
Use HERE Geocoding and Search API v7 for search and place ID retrieval, then EVCP API v3 for advanced EV information.
Best for:
- richer EV user experiences
- tariff-aware and availability-aware workflows
- customers who want the most complete HERE EV capability
Option C: Data + API (Advanced content)
3rd-party/proprietary search (without HERE Geocoding and Search v7 API) + EVCP API v3
Keep your existing search engine (for example, based on HERE data products such as POIs, Places, or HMC), and use EVCP API v3 for advanced EV details by place ID.
Best for:
- customers with a custom search stack
- organizations that require full control over search logic
- advanced EV data use cases without HERE Geocoding and Search v7 API discovery