HERE EV Charge Points API
EV Charging Stations API Developer's Guide

# Stations

This resource retrieves a list of charging stations for electric vehicles that match the specified criteria.

Requests against this resource use the HTTP GET method. The search criteria are specified by means of query parameters, which must include a search geometry.

A search geometry can be one of:

• prox – a circular area defined by the coordinates of its center and a radius.
• corridor – a path defined as a set of points (latitude, longitude pairs) and a width.
• bbox – a square defined by its top left latitude and longitude and its bottom right latitude and longitude.

## Request Example

The code block below shows a search request for charging stations in Berlin:

GET https://ev-v2.cc.api.here.com/ev/stations.xml
?prox=52.516667,13.383333,5000
-H 'Authorization: Bearer {YOUR_TOKEN}"


The following code block shows a search request for charging stations in Berlin with multiple connector types filtering:

GET https://ev-v2.cc.api.here.com/ev/stations.xml
?prox=52.516667,13.383333,5000
&connectortype=30,31
-H 'Authorization: Bearer {YOUR_TOKEN}"


## Request Parameters

The table below documents both mandatory and optional request parameters supported by this resource.

Parameter Required Description
app_id - Legacy Yes

A-20 byte Base64 URL-safe encoded string used for the authentication of the client application.

You must include an app_id and app_code with every request. For more information on authentication, see the Identity & Access Management Developer Guide.

app_code - Legacy Yes

A-20 byte Base64 URL-safe encoded string used for the authentication of the client application.

You must include an app_id and app_code with every request. For more information on authentication, see the Identity & Access Management Developer Guide.

prox prox, bbox or corridor must be present

A circular search area defined by the latitude and longitude of its center (compliant with WGS 84) and an integer representing the radius of the area in meters, all separated by commas.

For example, prox=52.516667,13.383333,5000 searches for charging stations within 5km of latitude 52.50° N and 13.55 ° E, which is within Berlin.

Radius can be a maximum of 200 km.

bbox prox, bbox or corridor must be present

Bounding box defined by the latitude and longitude (compliant with WGS 84) of its top left and bottom right corners. The top left and bottom right pairs are separated by a semicolon and the latitude and longitude pairs are separated by commas.

For example, one possible bounding box value is bbox=52.8,11.37309;52.31,13.2.

The bounding box can have a maximum height / width of 400km. If this limit is exceeded, the service responds with 'HTTP 400 Bad Request' response.

corridor prox, bbox or corridor must be present
A strip defined as a semicolon-separated list of points (pairs of comma-separated latitude and longitude WGS 84 compliant values) For example,
corridor=52.51666,13.38333;
52.13333,11.61666;53.56527,10.00138
specifies a journey from Berlin to Hamburg via Magdeburg.

Maximum corridor area is 5000 km2. If this limit is exceeded, the service responds with 'HTTP 400 Bad Request' response.

Note that requests to the stations resource can be a maximum of 4 kb in size in total. Since the corridor query parameter is the item that is most likely to contain the most information, a useful guideline is that this parameter can contain approximately 150 points (latitude/longitude pairs with an accuracy of 5 decimal points [for example, 11.37309]). Note that the amount of data you can include depends on the exact formulation of the request. If URL size is over 4 kb use POST HTTP method for this resource.

connectortype No

Comma-separated list of integer values identifying the connector types to be included in the response.

The available connector types are:

• 0 – Unspecified
• 1 – Other
• 2 – Unallowed
• 3 – Small Paddle Inductive
• 4 – Large Paddle Inductive
• 5 – Domestic plug/socket type B (NEMA 5-15)
• 6 – Domestic plug/socket type B (NEMA 5-20)
• 7 – Domestic plug/socket type D (BS 546 (3 pin))
• 8 – Domestic plug/socket type E (CEE 7/5)
• 9 – Domestic plug/socket type F (CEE 7/4 (Schuko))
• 10 – Domestic plug/socket type E+F (CEE 7/7)
• 11 – Domestic plug/socket type G (BS 1363, IS 401 & 411, MS 58)
• 12 – Domestic plug/socket type H (SI 32)
• 13 – Domestic plug/socket type I (AS/NZS 3112)
• 14 – Domestic plug/socket type I (CPCS-CCC)
• 15 – Domestic plug/socket type I (IRAM 2073)
• 16 – Domestic plug/socket type J (SEV 1011) (T13)
• 17 – Domestic plug/socket type J (SEV 1011) (T15)
• 18 – Domestic plug/socket type J (SEV 1011) (T23)
• 19 – Domestic plug/socket type J (SEV 1011) (T25)
• 20 – Domestic plug/socket type K (Section 107-2-D1)
• 21 – Domestic plug/socket type K (Thailand TIS 166 - 2549)
• 22 – Domestic plug/socket type L (CEI 23-16/VII)
• 23 – Domestic plug/socket type M (South African 15 A/250 V)
• 24 – Domestic plug/socket type IEC 60906-1 (3 pin)
• 25 – AVCON Connector
• 26 – Tesla Connector (high power wall)
• 27 – Tesla Connector (universal mobile)
• 28 – Tesla Connector (spare mobile)
• 29 – JEVS G 105 (CHAdeMO)
• 30 – IEC 62196-2 type 1 (SAE J1772)
• 31 – IEC 62196-2 type 2 (Mennekes)
• 32 – IEC 62196-2 type 3 (SCAME)
• 33 – IEC 62196-2 type 1 combo (SAE J1772)
• 34 – IEC 62196-2 type 2 combo (Mennekes)
• 35 – 60309 : industrial P + N + E (AC)
• 36 – 60309 : industrial 3P + E + N (AC)
• 37 – 60309 : industrial 2P + E (DC)
• 38 – 60309 : industrial P + N + E (AC) (CEEPlus)
• 39 – 60309 : industrial 3P + N + E (AC) (CEEPlus)
• 40 – Better place plug/socket
• 41 – Marechal plug/socket
• 42 – Domestic plug/socket type J (SEV 1011) (T13, T23)
• 43 – Tesla Connector
• 44 – IEC 61851-1
• 45 – IEC 62196-2 type 2 (SAE J1772)
• 46 – 60309 : industrial 2P + E (DC)
• 47 – I-type AS/NZ 3112 (Australian 15A/240V)
• 48 – Domestic plug/socket type A (NEMA 1-15, 2 pins)
• 49 – Domestic plug/socket type C (CEE 7/17, 2 pins)
• 50 – IEC 62196-2 type 3a (SCAME)
• 51 – Domestic plug/socket type B (NEMA 14-50)
• 52 – GB/T (Chinese) AC connector
• 53 – GB/T (Chinese) DC connector
• 54 – IEC 62196-2 type 2

You can retrieve the list of currently supported connector types using the connectortypes resource.

For more information on the current connector types, see Connector Types.

powerfeedtype No

An integer identifying the type of power feed included in the response.

Note: This information in only provided for charging stations in North America and Australia. If you use this query parameter in requests to the resource for search geometries that do not report this information, then the response does not contain any charging stations.

The available values are as follows:

• 0 – Unspecified
• 1 – Level 1
• 2 – Level 2
• 3 – Level 3
• 4 – Other

You can retrieve the list of currently supported powerfeed types using the powerfeedtypes resource.

For more information on the current power feed types, see Powerfeed Types.

corridorwidth No

The width of the corridor in meters. This parameter takes effect only if corridor is included in the request.

The maximum corridor width is 20 km.

Default: 5000 meters

powermin No

At least one connector in the station must have a maxPowerLevel value greater than or equal to this parameter.

Accepted are float values: powermin=11.6

Default: doesn't apply

powermax No

At least one connector in the station must have a maxPowerLevel value less than or equal to this parameter.

Accepted are float values: powermax=55.3

Default: doesn't apply

sortkey No Criteria for sorting a list of search results:

The possible values are:

• distance – sorts stations in the response by the distance from the location specified by the prox query parameter. This means this sort key is only supported when requesting stations by proximity.
• locationname – sorts stations in the response according to the name element in the evStation element.
• none – doesn't sort stations.

Default: distance

sortorder No The sort order in the response.

The possible values are:

• asc (ascending)
• desc (descending)

Default: asc

maxresults No The maximum number of results a response can contain.

This parameter can be used with the offset parameter in the query and HasMore in the response for pagination.

Default: 50

offset No A value specifying the index of the first result. The offset together with the "maxresults" value can be used to support a paging mechanism on search results.

This parameter can be used with the maxresults parameter in the query and HasMore in the response for pagination.

Default: 0

## Response to this Request

For more information on responses to queries against the stations resource, see Stations Response.