Charge Point Operators

Last edit: 2026.06.17 TomTom Orbis Maps

Important note
This API is not available as part of our free evaluation or Pay As You Grow (PAYG) offering. Click the Request Access button above to contact our Sales team.

Private Preview Notice

Important notes:

This TomTom Orbis Maps API is restricted to private preview.
This API is powered by the TomTom Orbis Maps.
See the TomTom Orbis Maps documentation for more information.

Purpose

The Charge Point Operators (CPO) endpoint enables clients to access a list of available CPOs in a given country or subdivision. This helps EV drivers choose their preferred Charge Point Operators while searching for EV charging stations.
The list of CPOs is sorted by ranking, with popular CPOs at the top.
CPOs can be queried for a specific set of countries/subdivisions using the countrySet filter parameter, or worldwide by omitting the filter.

Request data

HTTPS method: GET

For ease of viewing and identification:

Constants and parameters enclosed in curly brackets { } must be replaced with their values.
See Request parameters for the required and optional parameters and their values. The generic request format is as follows.

Request format

get

Request URL format

1
https://{baseURL}/maps/orbis/places/ev/cpos?key={Your_API_Key}&[countrySet={countryCodesOrSubdivisions}]&[view={view}]

Request curl command example

get

Request curl command example

1
curl 'https://api.tomtom.com/maps/orbis/places/ev/cpos?key={Your_API_Key}&countrySet=USA,US-FL,DEU&view=Unified'

Request parameters

The following table describes the parameters that can be used in a request.

Required parameters must be used or the call will fail.
Parameters and values are case-sensitive.
Optional parameters may be used.

Required parameters Description

Required parameters	Description
`baseURL` string	Base URL for calling the API. Values: `api.tomtom.com` `kr-api.tomtom.com` (see the Region-specific content page)
`key` string	An API Key valid for the requested service. Value: Your valid `API Key`.

baseURL string

Base URL for calling the API.
Values:

api.tomtom.com
kr-api.tomtom.com (see the Region-specific content page)

key string An API Key valid for the requested service. Value: Your valid API Key.

Optional parameters Description

Optional parameters	Description
`countrySet` string	Comma-separated list of country/subdivision codes. Supports both `alpha2`/`alpha3` formats for country codes defined by ISO 3166-1 alpha-2 and alpha-3. Restricts results to the specified countries/subdivisions. If omitted, worldwide data is returned, organized by country/subdivision. Example: `FR,NLD,US-FL,USA-TX`
`view` string	Geopolitical View. The context used to resolve the handling of disputed territories. Enum: `Unified`, `AR`, `IL`, `IN`, `MA`, `PK`, `RS`, `RU`, `TR`, `CN`, `TW` Default values: Argentina, default view: `AR`, available views: `Unified`, `IL`, `IN`, `MA`, `PK`, `RS`, `RU`, `TR`, `CN`, `TW` India, default view: `IN`, available views: - Morocco, default view: `MA`, available views: `Unified`, `AR`, `IL`, `IN`, `PK`, `RS`, `RU`, `TR`, `CN`, `TW` Pakistan, default view: `PK`, available views: `Unified`, `AR`, `IL`, `IN`, `MA`, `RS`, `RU` , `TR`, `CN`, `TW` Serbia, default view: `RS`, available views: `Unified`, `AR`, `IL`, `IN`, `MA`, `PK`, `RU`, `TR`, `CN`, `TW` Russia, default view: `RU`, available views: `Unified`, `AR`, `IL`, `IN`, `MA`, `PK`, `RS`, `TR`, `CN`, `TW` Turkey, default view: `TR`, available views: `Unified`, `AR`, `IL`, `IN`, `MA`, `PK`, `RS`, `RU`, `CN`, `TW` China, default view: `CN`, available views: `Unified`, `AR`, `IL`, `IN`, `MA`, `PK`, `RS`, `RU`, `TR`, `TW` Taiwan, default view: `TW`, available views: `Unified`, `AR`, `IL`, `IN`, `MA`, `PK`, `RS`, `RU`, `TR`, `CN` Others, default view: `Unified`, available views: `AR`, `IL`, `IN`, `MA`, `PK`, `RS`, `RU`, `TR`, `CN`, `TW`

countrySet string

Comma-separated list of country/subdivision codes. Supports both alpha2/alpha3 formats for country codes defined by ISO 3166-1 alpha-2 and alpha-3.
Restricts results to the specified countries/subdivisions. If omitted, worldwide data is returned, organized by country/subdivision.
Example: FR,NLD,US-FL,USA-TX

view string

Geopolitical View. The context used to resolve the handling of disputed territories.
Enum: Unified, AR, IL, IN, MA, PK, RS, RU, TR, CN, TW
Default values:

Argentina, default view: AR, available views: Unified, IL, IN, MA, PK, RS, RU, TR, CN, TW
India, default view: IN, available views: -
Morocco, default view: MA, available views: Unified, AR, IL, IN, PK, RS, RU, TR, CN, TW
Pakistan, default view: PK, available views: Unified, AR, IL, IN, MA, RS, RU , TR, CN, TW
Serbia, default view: RS, available views: Unified, AR, IL, IN, MA, PK, RU, TR, CN, TW
Russia, default view: RU, available views: Unified, AR, IL, IN, MA, PK, RS, TR, CN, TW
Turkey, default view: TR, available views: Unified, AR, IL, IN, MA, PK, RS, RU, CN, TW
China, default view: CN, available views: Unified, AR, IL, IN, MA, PK, RS, RU, TR, TW
Taiwan, default view: TW, available views: Unified, AR, IL, IN, MA, PK, RS, RU, TR, CN
Others, default view: Unified, available views: AR, IL, IN, MA, PK, RS, RU, TR, CN, TW

Request headers

The following table describes HTTP request headers.

Required headers	Description
TomTom-Api-Version	The version of the API being called. Currently, only version 1 is supported. Example: `1`

Optional headers	Description
Tracking-ID	Specifies an identifier for the request. It can be used to trace a call. The value must match the regular expression `'^[a-zA-Z0-9-]{1,100}$'`. An example of the format that matches this regular expression is UUID (e.g., `9ac68072-c7a4-11e8-a8d5-f2801f1b9fd1`). For details check RFC 4122. If specified, it is replicated in the Tracking-ID response header. It is only meant to be used for support and does not involve tracking of you or your users in any form. Value: An `identifier` for the request.
Accept	Specifies one of the following values as the response format of an API request: `application/json` Default if the header is not provided. `application/xml`
Accept-Encoding	Enables response compression. For details check RFC-9110 Value: `gzip`
If-None-Match	Clients can provide an entity tag (ETag) that was returned as a header in a previous response. This allows clients to check the freshness of the data. If the data has not changed, the service responds with a 304 (Not Modified) status. Value: An entity tag. Example: F13887B89265DBD6F8E38C3A96F21EF0

Response data

Response body

Json Response body example

1
{
2
  "results": [
3
    {
4
      "countryCode": "USA",
5
      "operators": [
6
        { "id": "EC2YV6HR", "name": "EcoCars", "paymentApplicationIds": ["QV9Tbvhb", "pEp9gSMe"] },
7
        { "id": "SE7DRIH3", "name": "Sollus Electronic Industry LTDA" },
8
        { "id": "POTQK6QF", "name": "Porsche" }
9
      ],
10
      "countrySubdivisions": [
11
        {
12
          "countrySubdivisionCode": "FL",
13
          "operators": [
14
            { "id": "EPELFOVD", "name": "EPE" },
15
            { "id": "EXEJX3XI", "name": "Enel X Way" },
16
            { "id": "NIITUN2N", "name": "Nissan" }
17
          ]
18
        }
19
      ]
20
    }
21
  ]
22
}

XML Response body example

1
<response>
2
    <results>
3
        <item>
4
            <countryCode>FR</countryCode>
5
            <operators>
6
                <operator>
7
                    <id>TEONML2T</id>
8
                    <name>Tesla</name>
9
                </operator>
10
                <operator>
11
                    <id>PORHOK3V</id>
12
                    <name>Powerdot</name>
13
                    <paymentApplicationIds>
14
                        <paymentApplicationId>EDKFIOVZ</paymentApplicationId>
15
                        <paymentApplicationId>OEXM3ZBP</paymentApplicationId>
16
                        <paymentApplicationId>ENADGFAQ</paymentApplicationId>
17
                        <paymentApplicationId>SR6TVFLW</paymentApplicationId>
18
                        <paymentApplicationId>PL26DTVW</paymentApplicationId>
19
                        <paymentApplicationId>VAPOYF4C</paymentApplicationId>
20
                    </paymentApplicationIds>
21
                </operator>
22
                <operator>
23
                    <id>ELXYTO3Y</id>
24
                    <name>Electra</name>
25
                    <paymentApplicationIds>
26
                        <paymentApplicationId>OEXM3ZBP</paymentApplicationId>
27
                        <paymentApplicationId>ENADGFAQ</paymentApplicationId>
28
                        <paymentApplicationId>QEJLA5RN</paymentApplicationId>
29
                        <paymentApplicationId>SR6TVFLW</paymentApplicationId>
30
                        <paymentApplicationId>PL26DTVW</paymentApplicationId>
31
                    </paymentApplicationIds>
32
                </operator>
33
            </operators>
34
        </item>
35
    </results>
36
</response>

Response fields

The following table describes all the fields that can appear in a response. Fields are listed by the response section they belong to and in the order that they appear in the response.

Primary fields
Field	Description
`results` array	Array of results `item` objects.

item object
Field	Description
`countryCode` string	Requested country code. If `countrySet` filter is absent, by default `countryCode` returned is in ISO 3166-1 alpha-2 format.
`operators` array	List of available `operator` brand objects.
`countrySubDivisions` array	Array of `countrySubDivision` objects.

operatorBrand object
Field	Description
`id` string	Unique identifier of the brand.
`name` string	Name of the brand.
`paymentApplicationIds` string (list)	List of payment applications supported by this brand.
`restrictedPaymentApplicationIds` string (list)	List of payment applications restricted to the current request and supported by this brand.

countrySubDivision object
Field	Description
`countrySubdivisionCode` string	Country subdivision code in ISO 3166-1 alpha-2.
`operators` array	List of available `operator` brand objects.

Response codes

Code	Meaning & possible causes
`200`	OK: If any matching charging station was found, the body of the response will contain the data. Otherwise, an empty response will be returned: Empty response example - JSON `1 {}`
`400`	Bad request: One or more parameters were incorrectly specified or are out of range.
`403`	Forbidden: Possible causes include: Forbidden Not authorized Account inactive Account over queries per second limit Rate limit exceeded
`404`	Not Found: The requested resource could not be found, the HTTP request method or path is incorrect.
`405`	Method Not Allowed : The client used an HTTP method other than `GET`.
`406`	Media Type Not Acceptable
`414`	The requested URI is too long
`429`	Too Many Requests: The API Key is over QPS (Queries per second).
`5xx`	Server Error: The service was unable to process your request. Contact support to resolve the issue.

Response headers

The following table lists HTTP response headers.

Header	Description
Access-Control-Allow-Origin	The EV Search service allows cross-origin resource sharing. Value: `*` This asterisk signifies access to the TomTom API using the Access-Control-Allow-Origin (ACAO) header in its response, indicating which origin sites are allowed.
Content-Encoding	The EV Search service supports HTTP compression if requested by the client. Value: `gzip`
Cache-Control	The Cache-Control general-header field is used to specify directives that must be obeyed by all caching mechanisms along the request/response chain. Supported by HTTP/1.1 clients. May not be supported by HTTP/1.0 clients. Value: `no-cache`
Content-Type	Indicates the format of the response as chosen by the client. Format: `type/subtype; charset=utf-8` Value: `type/subtype: application/json`
ETag	Entity-tag of the served resource. Can be used by the client in the `If-None-Match` header field of subsequent requests in order to optimize the update procedure. Value: Example: ” `F13887B89265DBD6F8E38C3A96F21EF0` “
Tracking-ID	An identifier for the request. If the Tracking-ID header was specified, it is replicated in the response. Otherwise, it is generated automatically by the service. It is only meant to be used for support and does not involve tracking of you or your users in any form. Value: An `identifier` for the request.

Error response

The error response content type depends on the Accept header.

Error response example - JSON

1
{
2
  "message": "Missing parameter 'parameterName'",
3
  "detailedError": {
4
    "code": "MissingParameter",
5
    "message": "Missing required parameter 'parameterName'."
6
  },
7
  "httpStatusCode": "400"
8
}

Error response example - XML

1
<ErrorEvResponse>
2
  <message>Missing parameter 'parameterName'</message>
3
  <detailedError>
4
    <code>MissingParameter</code>
5
    <message>Missing required parameter 'parameterName'.</message>
6
  </detailedError>
7
</ErrorEvResponse>

Error response fields

Primary fields	Description
`message` string	A human-readable description of the error.
`detailedError` object	Detailed information about the error. `detailedError` object
detailedError object
Field	Description
`code` string	One of a server-defined set of error codes.
`message` string	A human-readable description of the error code. It is intended as an aid to developers and is not suitable for exposure to end users.