HERE EV Charge Points API v3

HERE EV Charge Points API v3 — 6 operation(s) across 6 path(s), OpenAPI 3.0.2 version 3.20.1, harvested verbatim from the HERE developer documentation. Use this API to get detailed information about charging locations. It builds on data retrieved from the HERE Geocoding and Search API v7 or HERE Map Content . Tariff information is provided by Charge Point Operators. HERE Technologies works to keep this data accurate and up to date, but can't guarantee its completeness. Actual tariffs at charging locations may differ from the data returned by the API. Some fields and parameters are in ALPHA status. These may change without notice. Fields and parameters marked with the RESTRICTED privilege qualifier are available only to customers with a specific contract with HERE.

Operations 6

GET /locations/{id} Fetch a single location #
GET /locations Fetch multiple locations #
GET /countryMetadata Fetch metadata by countries. #
GET /health Tests basic health of the service #
GET /version Retrieves API specification version information #
GET /openapi Retrieves this API specification in OpenAPI 3 format #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/here-ev-charge-points-v3"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

here-ev-charge-points-v3-openapi.yml Raw ↑
{"openapi":"3.0.2","info":{"title":"HERE EV Charge Points API v3","description":"Use this API to get detailed information about charging locations. It builds on data\nretrieved from the **HERE Geocoding and Search API v7** or **HERE Map Content**.\n\nTariff information is provided by Charge Point Operators. HERE Technologies works to\nkeep this data accurate and up to date, but can't guarantee its completeness. Actual\ntariffs at charging locations may differ from the data returned by the API.\n\nSome fields and parameters are in **ALPHA** status. These may change without notice.\n\nFields and parameters marked with the **RESTRICTED** privilege qualifier are\navailable only to customers with a specific contract with HERE.\n","version":"3.20.1"},"servers":[{"url":"https://evcp.hereapi.com/v3","description":"Production environment URL"}],"security":[{"Bearer":[]},{"ApiKey":[]}],"tags":[{"name":"Charging Location Lookup","description":"Endpoints to query charging location data"},{"name":"Charging Location Metadata","description":"Endpoints to query charging location metadata, namely operators and e-Mobility Service Providers."},{"name":"API Information","description":"Additional API Information"}],"paths":{"/locations/{id}":{"get":{"summary":"Fetch a single location","description":"Allows fetching a single location given its ID. The set of returned location properties can be controlled via the `fields` parameter.","operationId":"HERE EV Charge Points API v3 getLocation","tags":["Charging Location Lookup"],"parameters":[{"$ref":"#/components/parameters/xRequestId"},{"$ref":"#/components/parameters/id"},{"$ref":"#/components/parameters/fields"},{"$ref":"#/components/parameters/days"},{"$ref":"#/components/parameters/tariff"}],"responses":{"200":{"description":"EV charge point data","headers":{"X-Correlation-ID":{"$ref":"#/components/headers/X-Correlation-ID"},"X-Request-ID":{"$ref":"#/components/headers/X-Request-ID"}},"content":{"application/json":{"schema":{"$ref":"#/components/schemas/ChargingLocation"}}}},"400":{"$ref":"#/components/responses/BadRequestErrorResponse"},"401":{"$ref":"#/components/responses/UnauthorizedErrorResponse"},"403":{"$ref":"#/components/responses/ForbiddenErrorResponse"},"404":{"$ref":"#/components/responses/NotFoundResponse"},"500":{"$ref":"#/components/responses/InternalErrorResponse"},"503":{"$ref":"#/components/responses/ServiceUnavailableErrorResponse"},"default":{"$ref":"#/components/responses/GenericErrorResponse"}}}},"/locations":{"get":{"summary":"Fetch multiple locations","description":"Returns data for the specified location identifiers in the `items` property of the response. If no data is found for a location identifier, it appears in the `missing` property.","operationId":"HERE EV Charge Points API v3 getLocations","tags":["Charging Location Lookup"],"parameters":[{"$ref":"#/components/parameters/xRequestId"},{"$ref":"#/components/parameters/idList"},{"$ref":"#/components/parameters/fields"},{"$ref":"#/components/parameters/days"},{"$ref":"#/components/parameters/tariff"},{"$ref":"#/components/parameters/connectorTypes"}],"responses":{"200":{"description":"EV charge point data","headers":{"X-Correlation-ID":{"$ref":"#/components/headers/X-Correlation-ID"},"X-Request-ID":{"$ref":"#/components/headers/X-Request-ID"}},"content":{"application/json":{"schema":{"$ref":"#/components/schemas/ChargingLocations"}}}},"400":{"$ref":"#/components/responses/BadRequestErrorResponse"},"401":{"$ref":"#/components/responses/UnauthorizedErrorResponse"},"403":{"$ref":"#/components/responses/ForbiddenErrorResponse"},"500":{"$ref":"#/components/responses/InternalErrorResponse"},"503":{"$ref":"#/components/responses/ServiceUnavailableErrorResponse"},"default":{"$ref":"#/components/responses/GenericErrorResponse"}}}},"/countryMetadata":{"get":{"summary":"Fetch metadata by countries.","description":"Fetch metadata by countries, such as a list of e-Mobility Service Providers\n(eMSPs). If you don't specify any countries, the response includes all available\ncountries. If you don't specify any fields, the response includes only the list of\navailable countries.\n","operationId":"HERE EV Charge Points API v3 getCountryMeta","tags":["Charging Location Metadata"],"parameters":[{"$ref":"#/components/parameters/xRequestId"},{"$ref":"#/components/parameters/countryCodes"},{"$ref":"#/components/parameters/metaFields"}],"responses":{"200":{"description":"List of metadata entries by country.","headers":{"X-Correlation-ID":{"$ref":"#/components/headers/X-Correlation-ID"},"X-Request-ID":{"$ref":"#/components/headers/X-Request-ID"}},"content":{"application/json":{"schema":{"$ref":"#/components/schemas/MetadataByCountry"}}}},"400":{"$ref":"#/components/responses/BadRequestErrorResponse"},"401":{"$ref":"#/components/responses/UnauthorizedErrorResponse"},"500":{"$ref":"#/components/responses/InternalErrorResponse"},"503":{"$ref":"#/components/responses/ServiceUnavailableErrorResponse"},"default":{"$ref":"#/components/responses/GenericErrorResponse"}}}},"/health":{"get":{"summary":"Tests basic health of the service","operationId":"HERE EV Charge Points API v3 getHealth","tags":["API Information"],"parameters":[{"$ref":"#/components/parameters/xRequestId"}],"responses":{"200":{"description":"Health response in case of success","headers":{"X-Correlation-ID":{"$ref":"#/components/headers/X-Correlation-ID"},"X-Request-ID":{"$ref":"#/components/headers/X-Request-ID"}},"content":{"application/json":{"schema":{"$ref":"#/components/schemas/HealthResponse"}}}},"401":{"$ref":"#/components/responses/UnauthorizedErrorResponse"},"503":{"description":"Health response when the service is not healthy","headers":{"X-Correlation-ID":{"$ref":"#/components/headers/X-Correlation-ID"},"X-Request-ID":{"$ref":"#/components/headers/X-Request-ID"}},"content":{"application/json":{"schema":{"$ref":"#/components/schemas/HealthResponse"}}}},"default":{"$ref":"#/components/responses/GenericErrorResponse"}}}},"/version":{"get":{"summary":"Retrieves API specification version information","operationId":"HERE EV Charge Points API v3 getVersion","tags":["API Information"],"parameters":[{"$ref":"#/components/parameters/xRequestId"}],"responses":{"200":{"description":"Version of API","headers":{"X-Correlation-ID":{"$ref":"#/components/headers/X-Correlation-ID"},"X-Request-ID":{"$ref":"#/components/headers/X-Request-ID"}},"content":{"application/json":{"schema":{"$ref":"#/components/schemas/VersionResponse"}}}},"401":{"$ref":"#/components/responses/UnauthorizedErrorResponse"},"default":{"$ref":"#/components/responses/GenericErrorResponse"}}}},"/openapi":{"get":{"summary":"Retrieves this API specification in OpenAPI 3 format","operationId":"HERE EV Charge Points API v3 getOpenapi","tags":["API Information"],"parameters":[{"$ref":"#/components/parameters/xRequestId"}],"responses":{"200":{"description":"Version of API","headers":{"X-Correlation-ID":{"$ref":"#/components/headers/X-Correlation-ID"},"X-Request-ID":{"$ref":"#/components/headers/X-Request-ID"}},"content":{"application/json":{"schema":{"$ref":"#/components/schemas/OpenapiResponse"},"examples":{"openapi":{"$ref":"#/components/examples/OpenapiResponse"}}},"application/x-yaml":{"schema":{"type":"string"}},"text/x-yaml":{"schema":{"type":"string"}}}},"401":{"$ref":"#/components/responses/UnauthorizedErrorResponse"},"default":{"$ref":"#/components/responses/GenericErrorResponse"}}}}},"components":{"parameters":{"connectorTypes":{"name":"connectorTypes","in":"query","description":"Filter charging locations to only contain EVSEs and connector groups matching the\nrequested connector types.\n\nThis can reduce response size by returning only relevant data. Locations that\ndon't contain EVSEs matching the requested connector types aren't included in\nthe response.\n\nProvide a comma-separated list of connector type identifiers, as defined in the\nConnectorType schema. If you don't specify this parameter, the response includes\nall connector types and no filtering is applied.\n\nConnector types represent physical standards for EV charging connectors, such as\nIEC_62196_T2 and CHADEMO.\n\nFor a complete list of supported values, see the ConnectorType schema.\n","example":["IEC_62196_T2","IEC_62196_T2_COMBO","CHADEMO"],"explode":false,"required":false,"schema":{"type":"array","minItems":1,"maxItems":5,"uniqueItems":true,"items":{"$ref":"#/components/schemas/ConnectorType"}}},"countryCodes":{"name":"countryCodes","in":"query","description":"Filter metadata results to include only the specified countries. A comma-separated list of three-letter country codes according to ISO 3166-1 alpha 3.","example":["DEU","GBR","IRL"],"explode":false,"schema":{"type":"array","minItems":1,"maxItems":50,"items":{"$ref":"#/components/schemas/CountryCode"}}},"days":{"name":"days","in":"query","description":"Data is retrieved starting from the current day, based on the local time zone of\nthe location. Currently applies to data from the following fields: `predictions`.\n\nIf no parameter is provided, the default value is 2, which returns data for the\ncurrent day and the following day.\n\nIf a parameter is provided, the system attempts to return data for the specified\nnumber of days, starting from today.\n\nThe actual number of days returned may be fewer than requested, depending on data\navailability.\n","required":false,"example":1,"schema":{"type":"integer","minimum":1,"maximum":7,"default":2}},"fields":{"name":"fields","description":"The `fields` parameter allows requesting additional fields in addition\nto the minimal set of fields to control the amount of data returned. \nThe minimal set of fields is defined as follows:\n  * `id`\n  * `location`\n  * `name`\n  * `operator`\n  * `suboperator`\n  * `restrictions`\n  * `supportedVehicles`\n\nAdditional fields can be requested according to the following table. The fields\ncan be freely combined in the query. However some fields have dependencies to\nother fields as listed in the table. If a field is not present in the data, it\nwill be left out of the response.\n\n<table>\n  <tr>\n    <td><b>Fields-query</b></td>\n    <td><b>Returned fields</b></td>\n  </tr>\n  <tr>\n    <td>address</td>\n    <td>'address' in full details</td>\n  </tr>\n  <tr>\n    <td>evses</td>\n    <td>'evses' in full details, including 'connectors', 'maxPower', 'standard', 'status' etc</td>\n  </tr>\n  <tr>\n    <td><b>RESTRICTED</b> truckRestrictions</td>\n    <td>'truckRestrictions', 'vehicleLimitations', 'isPullThrough', 'evse.vehicleTypes', 'evse.vehicleLimitations', 'evse.noClearanceHeight'</td>\n  </tr>\n  <tr>\n    <td>locationInfo</td>\n    <td>'accessPoints', 'parkingType', 'supportPhoneNumber', 'timeZone', 'isPullThrough', 'openingHours', 'energyMix', 'cpoLocationId', 'reservationRequired'</td>\n  </tr>\n  <tr>\n    <td>emsps</td>\n    <td>'eMobilityServiceProviders'</td>\n  </tr>\n  <tr>\n    <td>connectorGroups</td>\n    <td>'connectorGroups', a summary of connectors grouped by max power and type. If also evses-field is requested, the groups include references to EVSEs and connectors.</td>\n  </tr>\n  <tr>\n    <td><b>RESTRICTED</b> predictions</td>\n    <td>'predictions' in charging location level. If also 'connectorGroups'-field is requested, gives predictions also in 'connectorGroups'.</td>\n  </tr>\n  <tr>\n    <td><b>ALPHA RESTRICTED</b> reliability</td>\n    <td>'reliability' indicators for 'evses' and 'connectorGroups'. Ignored if requested without 'evses' or 'connectorGroups' fields.</td>\n  </tr>\n  <tr>\n    <td>tariffs</td>\n    <td>'tariffs' for 'connectors' / 'connectorGroups'. Ignored if requested without 'evses' or 'connectorGroups' fields.</td>\n  </tr>\n  <tr>\n    <td>nearby</td>\n    <td><b>ALPHA</b> 'nearbyPlaces', 'facilityTypes', 'hasMoreNearbyPlaces'</td>\n  </tr>\n</table>\n","in":"query","style":"form","explode":false,"example":["evses","address"],"schema":{"type":"array","uniqueItems":true,"items":{"type":"string","enum":["address","evses","truckRestrictions","locationInfo","emsps","connectorGroups","predictions","reliability","tariffs","nearby"]}}},"id":{"name":"id","in":"path","description":"Identifier of the charging location, obtained for example from the Geocoding and Search API, or from the HERE Map Content Electric Vehicle Charging Location data. Only the last component of a colon-separated identifier is used to index the data. The other components are optional.","example":"here:evcp:charginglocation:246udbvs5xwtg-aGVyZS1ldjplY29tb3ZlbWVudDoyMTEzODY4NzI3","required":true,"schema":{"$ref":"#/components/schemas/IdParameter"}},"idList":{"name":"ids","in":"query","description":"A comma separated list of unique charging location identifiers.\n\nOnly the last component of a colon-separated identifier (the \"content id\")\nis used to index the data. The other components are optional.\n\nFor requests containing more than 50 identifiers, provide only the\ncontent ids (the last component) rather than full HRNs to reduce URL\nlength and improve compatibility.\n","example":["246udbvs5xwtg-aGVyZS1ldjplY29tb3ZlbWVudDoyMTEzODY4NzI3","276u33d811u8y-aGVyZS1ldjplY29tb3ZlbWVudDozMTMwMTI5MTU"],"required":true,"explode":false,"schema":{"type":"array","minItems":1,"maxItems":100,"items":{"$ref":"#/components/schemas/IdParameter"}}},"metaFields":{"name":"fields","description":"The fields parameter allows selecting which metadata fields are returned.\nIf no fields are specified, the response will only consist of a list of available\ncountries.\nPossible values are:\n* `eMobilityServiceProviders`: e-Mobility Service Provider names and ids.\n* `operators`: Charge point operator and suboperator names and ids.\n* `tariffs`: Tariff metadata is included in the e-Mobility Service Provider and\n  operator metadata details. No effect if used alone.\n* `connectorTypes`: Connector type identifier, common name, and max power.\n","in":"query","style":"form","explode":false,"schema":{"type":"array","minItems":1,"maxItems":4,"items":{"type":"string","enum":["eMobilityServiceProviders","operators","tariffs","connectorTypes"]}}},"tariff":{"name":"tariff","description":"Search option to choose the eMSP or CPO whose tariff the client wants\nto see in the response. This parameter is effective only if the `fields` is\nconfigured to return tariffs.\n\nSupported values:\n- no `tariff` parameter: return ad-hoc tariffs only\n- `all`: return all available tariffs (CPO + eMSP + Ad-hoc)\n- `adhoc`: return ad-hoc tariffs only\n- `cpo`: return all CPO tariffs\n- `emsp`: return all eMSP tariffs\n- `partner:<partnerId>`: return all tariffs for the specified partner\n- `partner:<partnerId>;name=<tariffName>[,<tariffName>...]`: return the\n  specified tariff names for the partner\n- `<partnerId>`: return all tariffs for the specified partner + Ad-hoc\n  tariffs\n- `<partnerId>,<tariffName>[,<tariffName>...]`: return the specified\n  tariff names for the partner + Ad-hoc tariffs\n\nThe `tariff` query parameter can be included multiple times to request\nmultiple filters. Group keywords such as `cpo` and `emsp` must be sent as\nseparate parameter values and cannot be combined with a `partnerId` in the\nsame `tariff` entry. The legacy format\n`<partnerId>[,<tariffName>...]` remains supported for backward\ncompatibility and continues to include Ad-hoc tariffs. New integrations\nare recommended to use\n`partner:<partnerId>[;name=<tariffName>[,<tariffName>...]]`.\n\nThe input is expected to be based on the response from the `CountryMetadata`\nendpoint, including only eMSPs / CPOs that are relevant for the client. \n\nSome eMSPs provide several tariffs (subscriptions / charge cards). The end user\nis expected to subscribe to only a few of them, and is hence expected to be\ninterested in only the related tariffs. The available tariffs are listed in the\n`CountryMetadata` response. If tariff name is not set or the name does not match\nwith the tariffs of the provider, all available tariffs for that provider for the\ncharging location are returned.\n\nAs tariff names may occasionally change, the client is encouraged to monitor\nthe list by regularly fetching the latest list of tariff names per eMSP or CPO\nfrom the `CountryMetadata` endpoint. \n\nIf the returned tariffs for multiple locations do not contain a requested tariff\nby the name, the client is recommended to try searching without any names.\nIf still no tariffs were returned, the reason may be that there are no tariffs\navailable for the locations, or that the partner has no roaming agreement for the\nlocations.\n\nIf the search by partnerId succeeds, the used tariff name may be outdated and the\nclient need to update the list from the `CountryMetadata` endpoint.\n\nThis search cannot be used to filter out locations not covered by the specified\neMSPs / CPOs.\n","in":"query","style":"form","explode":true,"schema":{"type":"array","maxItems":50,"items":{"description":"The keyword `all` to request all tariffs (ad-hoc and subscription,\nincluding both eMSP and CPO tariffs), the keyword `adhoc` to request\nad-hoc tariffs, the keyword `cpo` to request all CPO tariffs, the\nkeyword `emsp` to request all eMSP tariffs, a legacy string\nconsisting of eMSP or CPO `partnerId` and optionally a list of tariff\nnames, one or more, separated by a comma `,`, or the preferred\nexplicit format `partner:<partnerId>` optionally followed by\n`;name=<tariffName>[,<tariffName>...]`. Not provided or empty value\ndefaults to `adhoc`.\n\nThe query parameter must be repeated if multiple filters are requested. Group keywords\nsuch as `cpo` and `emsp` must be sent as separate parameter values and cannot be combined\nwith a `partnerId` in the same `tariff` entry. In the `partner:` format, any values listed\nafter `;name=` are interpreted as tariff names, even if a name matches a keyword such as\n`emsp` or `cpo`. In the legacy `<partnerId>,<tariffName>...` format, any values after the\n`partnerId` are likewise interpreted as tariff names, and legacy\npartnerId forms continue to include Ad-hoc tariffs for backward\ncompatibility. For tariff parameters repeating the same partnerId,\nonly the last instance is applied.\n","type":"string","maxLength":256,"minLength":1,"pattern":"^^(all|adhoc|cpo|emsp|partner:.{36}(;name=.*)?|.{36}(,.*)*)$"}},"example":["adhoc","all","cpo","emsp","partner:1f90fdf0-cca5-11ed-be23-42010aa40002","partner:1f90fdf0-cca5-11ed-be23-42010aa40002;name=Basic,Advanced","partner:1f098f1e-cca5-11ed-b774-42010aa40002;name=Roaming Plus","1f90fdf0-cca5-11ed-be23-42010aa40002","1f90fdf0-cca5-11ed-be23-42010aa40002,Basic,Advanced","1f098f1e-cca5-11ed-b774-42010aa40002,Roaming Plus"]},"xRequestId":{"name":"X-Request-ID","in":"header","description":"User-provided token that can be used to trace a request or a group of requests sent to the service","schema":{"type":"string"}}},"headers":{"X-Correlation-ID":{"description":"Auto-generated ID, which uniquely identifies the request, available in the response. When contacting support with an inquiry regarding a specific request, provide the value of this header which will help troubleshooting the issue.","schema":{"type":"string"},"example":"4199533b-6290-41db-8d79-edf4f4019a74"},"X-Request-ID":{"description":"User-provided token that can be used to trace a request or a group of requests sent to the service.","schema":{"type":"string"}}},"securitySchemes":{"ApiKey":{"type":"apiKey","in":"query","name":"apiKey","description":"A key generated specifically to authenticate API requests. For\nmore information on how to get an API key, see the [https://developer.here.com/documentation/identity-access-management/dev_guide/index.html](Identity\n& Access Management Guide).\n"},"Bearer":{"type":"http","scheme":"bearer","bearerFormat":"JWT","description":"A token obtained from a separate endpoint using client credentials\nand an OAuth 1.0a HMAC-SHA256 signed request. For more information on how\nto get a bearer token, see the [https://developer.here.com/documentation/identity-access-management/dev_guide/index.html](Identity\n& Access Management Guide).\n"}},"schemas":{"Address":{"type":"object","description":"Address of the EV charging location.","properties":{"label":{"type":"string","description":"The full address in a single string.","example":"Invalidenstrasse 116, 10115 Berlin, Germany"},"street":{"type":"string","description":"The name of the street.","example":"Invalidenstraße"},"houseNumber":{"type":"string","description":"House number.","example":"116"},"state":{"type":"string","description":"A division of a country; typically, a first-level administrative division of a country or equivalent.","example":"Berlin"},"county":{"type":"string","description":"A division of a state; typically, a secondary-level administrative division of a country or equivalent.","example":"Berlin"},"city":{"type":"string","description":"The primary locality of the address.","example":"Berlin"},"district":{"type":"string","description":"A division of city; typically an administrative unit within a larger city or a customary name of a city's neighborhood.","example":"Mitte"},"subdistrict":{"type":"string","description":"A subdivision of a district.","example":"Romantikkiez"},"block":{"type":"string","description":"Name or number of block. Used only in some countries.","example":"3"},"subblock":{"type":"string","description":"Name or number of sub-block. Used only in some countries.","example":"1"},"countryCode":{"type":"string","description":"A three-letter country code according to ISO 3166-1 alpha 3.","example":"DEU"},"postalCode":{"type":"string","description":"An alphanumeric string included in a postal address to facilitate mail sorting, such as postal code, postcode, or ZIP code.","example":"10115"},"languageCode":{"type":"string","description":"ISO 639-1 two-letter language code for the address fields.","example":"de"}}},"AnnualOpeningHoursDetailType":{"description":"Special opening dates and time periods, or closing dates.","type":"object","properties":{"date":{"type":"string","format":"date","example":"2020-12-24","description":"Date of special opening hours"},"periods":{"description":"A list of time periods when the charging location is open on the\nspecified date. The time periods are in the local time zone of the\ncharging location, and are represented as a list of objects with\n`from` and `to` properties.\n","type":"array","items":{"$ref":"#/components/schemas/TimePeriodType"}},"closed":{"type":"boolean","example":true,"description":"True if the charging location is closed on particular date. Either the `closed` or the `period` elements are included in the response, not both."}},"required":["date"]},"BusinessDetails":{"description":"Name and optionally other details about operator, suboperator, or e-Mobility service provider.","type":"object","properties":{"name":{"description":"Name of the company.","type":"string"},"website":{"description":"Link to the company's website, if available.","type":"string"},"partnerId":{"description":"A unique ID for the company. It can be used to assure correct mapping when the name changes.","type":"string"},"eMobilityIds":{"description":"e-Mobility ids for the company; there are often more than one, especially if the company operates in multiple countries, but not all companies have any.","type":"array","items":{"$ref":"#/components/schemas/EMobilityId"},"uniqueItems":true},"logo":{"description":"Image link to the company's logo, if available.","allOf":[{"$ref":"#/components/schemas/Image"}]}},"required":["name","partnerId"],"example":{"name":"ChargePoint","partnerId":"1f90fdf0-cca5-11ed-be23-42010aa40002","eMobilityIds":["DE-EV1"]}},"ChargingLocation":{"description":"An electric vehicle (EV) charging location. The semantics generally\nfollow the OCPI 2.2.1 standard.\n\nKnown EV-specific acronyms:\n* EV: Electric Vehicle\n* OCPI: Open Charge Point Interface (a standard with a rather wide\nadoption worldwide, https://evroaming.org/)\n* CPO: Charge Point Operator (company that runs the EV charging\nlocation)\n* eMSP: e-Mobility Service Provider (customer-facing company)\n* EVSE: Electric Vehicle Supply Equipment (the actual charger that can\ncharge one car at a time)\n\nA charging location includes a collection of one or more EV supply\nequipment (EVSE) instances.\n\nTypically, the charging location is the exact location of the group of\nEVSEs, simplified to a single point, but it can also be the entrance of\na parking structure which contains these EVSEs.\n\nEach EVSE supports more precise position, where applicable.\n","type":"object","properties":{"id":{"$ref":"#/components/schemas/Id"},"location":{"description":"A point representation of the EV charging location's geolocation.","allOf":[{"$ref":"#/components/schemas/Location"}]},"supportedVehicles":{"description":"Set of vehicle categories this charging location can support.\nFor example, the same location can be suitable for charging\npassenger cars and motorcycles.\n\nThere may be some further restrictions specified in other\nattributes, for example the available connector types may\nnot be suitable for all vehicles in the supported category.\n\nExtensible enum: `car` `twoWheeler` `truck` `...`  \n\n* `car`: The charging location is suitable for regular passenger cars, and\noptionally also for light commercial vehicles, such as vans, pickups and the\nlike, if signaled by `truckAccess` property.\nThis is the default category, used when there is no explicit information about\nsupport for other vehicle types.\n\n* `twoWheeler`: The charging location is suitable for motor bikes,\ne-scooters, and the like.\n\n* `truck`: The charging location is suitable for heavy vehicle charging,\nincluding, for example, rigid trucks and semi-trailer trucks, requiring more\nphysical space for parking and maneuvering than passenger cars.\n\nAs it is possible that new categories are supported in the future,\nunknown categories should be ignored.\n","type":"array","items":{"$ref":"#/components/schemas/EvVehicleCategory"},"uniqueItems":true},"name":{"description":"Display name of the location.","type":"string"},"accessPoints":{"description":"A list of points that provide access from road network to the EV\ncharging location.\n\nThis is not the same position where the charging location is located,\nbut a point on the nearest suitable road.\n\nIt can be rendered on map to illustrate from where to enter the\ncharging location.\n","type":"array","items":{"$ref":"#/components/schemas/Location"},"uniqueItems":true},"address":{"description":"Structured address.\n","allOf":[{"$ref":"#/components/schemas/Address"}]},"parkingType":{"description":"The general type of the charging location's parking.\n\nExtensible enum: `alongMotorway` `parkingGarage` `parkingLot` `onDriveway` `onStreet` `undergroundGarage` `...`  \n\n* `alongMotorway`: A parking facility/rest area along a motorway, freeway,\ninterstate, highway etc.\n* `parkingGarage`: Multi-story car park, mainly above ground.\n* `parkingLot`: A cleared area that is intended for parking vehicles, for example\nat super markets or bars.\n* `onDriveway`: The driveway of a house or building.\n* `onStreet`: A public parking space along a street.\n* `undergroundGarage`: Multi-story car park, mainly underground.\n\nAs it is possible that new types are supported in the future,\nunknown types should be ignored.\n","allOf":[{"$ref":"#/components/schemas/EvParkingType"}]},"operator":{"description":"Information about the operator, if available.","allOf":[{"$ref":"#/components/schemas/BusinessDetails"}]},"suboperator":{"description":"Information about the suboperator, if available.","allOf":[{"$ref":"#/components/schemas/BusinessDetails"}]},"facilityTypes":{"description":"Types of facilities / amenities nearby the EV charging location.\n\nExtensible enum: `hotel` `restaurant` `cafe` `mall` `supermarket` `sport` `recreationArea` `nature` `museum` `bikeSharing` `busStop` `taxiStand` `tramStop` `metroStation` `trainStation` `airport` `parkingLot` `carpoolParking` `fuelStation` `wifi` `business` `education` `finance` `health` `service` `store` `fastFood` `bakery` `truckStop` `playground` `toilets` `...`  \n\n* `hotel`: A place to stay overnight.\n* `restaurant`: A place to eat.\n* `cafe`: A place to have a coffee or other drinks.\n* `mall`: A shopping mall.\n* `supermarket`: A place to buy groceries.\n* `sport`: Sport facilities: gym, field etc.\n* `recreationArea`: A place for recreation, like a park, beach etc.\n* `nature`: Located in, or close to, a park, nature reserve etc.\n* `museum`: A museum or other cultural facility.\n* `bikeSharing`: A bike/e-bike/e-scooter sharing location.\n* `busStop`: A bus stop.\n* `taxiStand`: A taxi stand.\n* `tramStop`: A tram stop.\n* `metroStation`: A metro station.\n* `trainStation`: A train station.\n* `airport`: An airport.\n* `parkingLot`: A parking lot.\n* `carpoolParking`: A parking lot for carpooling.\n* `fuelStation`: A fuel station.\n* `wifi`: Wifi or other type of internet available.\n* `business`: Business facilities.\n* `education`: Educational facilities.\n* `finance`: Financial facilities.\n* `health`: Health facilities.\n* `service`: Service facilities.\n* `store`: A store.\n* `fastFood`: A fast food restaurant.\n* `bakery`: A bakery.\n* `truckStop`: A truck stop, rest area or similar.\n* `playground`: A playground or other place for children to play.\n* `toilets`: Toilets available for public use.\n\nAs it is possible that new facility types are supported in the future,\nunknown types should be ignored.\n","type":"array","items":{"$ref":"#/components/schemas/EvFacilityType"},"uniqueItems":true},"timeZone":{"description":"The time zone of the charging location. Based on IANA tzdata's\nTZ-values.\n","type":"string","example":"Europe/Berlin"},"openingHours":{"description":"The times when the EVSEs at the charging location can be accessed for\ncharging.\n","allOf":[{"$ref":"#/components/schemas/OpeningHoursType"}]},"cpoLocationId":{"description":"CPO's own id for the location, if available.\n\nThis id may be relevant for some clients to map the `ChargingLocation` data to\ntheir own or 3rd party systems.\n","type":"string"},"energyMix":{"description":"Details on the energy supplied at this location.","allOf":[{"$ref":"#/components/schemas/EnergyMix"}]},"connectorGroups":{"description":"Connector groups for the location.\n\nProvides an overview of the charging connectors in the location by\ntype and power.\n","type":"array","items":{"$ref":"#/components/schemas/ConnectorGroup"},"uniqueItems":true},"restrictions":{"description":"Reason(s) for restricted access type, multiple reasons can be\napplied as alternatives (with OR). Note: Private locations are not\neven included.\n\nExtensible enum: `customersOnly` `brandOnly` `carSharingOnly` `taxisOnly` `other` `...`  \n\n* `customersOnly`: Charging for customers of a hotel, restaurant, store\netc\n* `brandOnly`: Vehicle brand-restriction, for example Tesla, BMW\n* `carSharingOnly`: Charging for car sharing\n* `taxisOnly`: Charging for taxis\n* `other`: Charging is restricted due to other reasons\n\nAs it is possible that new restriction reasons are supported\nin the future, unknown reasons should be ignored.\n","type":"array","items":{"$ref":"#/components/schemas/EvAccessRestrictionReason"},"uniqueItems":true},"eMobilityServiceProviders":{"description":"eMSPs with a roaming agreement enabling access to the EV charging location. The details are without logo or website.","type":"array","items":{"$ref":"#/components/schemas/BusinessDetails"},"uniqueItems":true},"supportPhoneNumber":{"description":"The phone number that EV drivers should call when they need\nassistance at the charge location, in E.164 format.\n","type":"string"},"truckRestrictions":{"$ref":"#/components/schemas/TruckRestrictions"},"isPullThrough":{"description":"Most of the EV charging locations are designed for nose in/out\nparking or parallel parking, requiring manouvering when entering or exiting.\nLocations with at least one EVSE allowing pull through, i.e., exiting without\nreversing, are handy especially for cars or trucks with trailers.\nIf the layout is not known, nose or parallel parking can be assumed.\n","type":"boolean"},"vehicleLimitations":{"$ref":"#/components/schemas/VehicleLimitations"},"reservationRequired":{"description":"Indicates whether a reservation is required for using some EVSEs at the\ncharging location. The location may still also have EVSEs that can be used\nwithout a reservation.\n\nIf true, the driver should check at the EVSE-level whether a reservation is\nneeded in advance to be able to charge.\nIf false, the driver can use any available EVSEs without reservation.\nAbsence indicates the information is not known;

# --- truncated at 32 KB (128 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/here/refs/heads/main/openapi/here-ev-charge-points-v3-openapi.yml