Version Change Document

There is a breaking change in the EV Location API. The current v1 endpoint will be decommissioned on 31st March 2026. Customers using v1 are advised to plan their migration to v2.

The core API concepts remain unchanged; however, v2 introduces several technical adjustments, such as updated data types for certain parameters and the removal of non‑relevant or not consistently reliable fields.

The sections below explain the changes in detail.

Authentication

The authentication endpoint is unchanged, and the existing OAuth endpoint remains in use.

Versioning of the APIs

Only the base URL for all four location endpoints has been updated from v1 to v2. The endpoint paths themselves remain unchanged.
1. Old Base URL - https://api.shell.com/ev/v1/locations
2. New Base URL - https://api.shell.com/ev/v2/locations

Change details on 3 endpoints: /locations, /id, /nearby

Data Type changes in Response payload
1. The response now includes three UUID fields (Location UUID, EVSE UUID, Connector UUID). Previously, these values were provided as integers. They have now all been updated to string data types to ensure proper UUID formatting and consistency.
2. Below are the exact parameter names in the response payload.
  1. Data.uid
  2. Data.evses.uid
  3. Data.evses.connectors.uuid
The following parameters have been removed in version v2.
1. Data.accessibility.remark
2. data.operatorComment
3. Data.evse.connectors.deleted
4. Data.evse.connectors.fixedCable
5. Data.evse.connectors.tariff
6. Data.evse.connectors.updated
7. Data.evse.connectors.updatedBy
8. Data.evse.deleted
9. Data.evse.physicalReference

Please note that the tariff component is made available in /locations/id endpoint. Tariff information can be fetched only per location.

Change details on /locations/markers endpoint

Three parameters have been removed from the response payload in v2.
1. Data.geoHash
2. Data.markerType
3. Data.uniquekey

Tariff Details

The tariff details will be available only in the locations/id end point which means, tariff details can be fetched only per location and not in bulk. This change is due to the dynamic pricing feature that has been enabled in our product.

Also, to fetch the tariff info, ProviderID is mandatory in the query parameter. ProviderId will be shared by Shell.

Below is a sample tariff component for reference.

"tariffs": [
    {
      "createdBy": "STAGE_TEST1",
      "currency": "",
      "elements": [
        {
          "priceComponents": [
            {
              "price": 1.7208002,
              "stepSize": 1,
              "type": "ENERGY",
              "vat": 21
            }
          ]
        },
        {
          "priceComponents": [
            {
              "price": 4.1202,
              "stepSize": 10,
              "type": "TIME",
              "vat": 8
            }
          ]
        },
        {
          "priceComponents": [
            {
              "price": 0.84033614,
              "stepSize": 1,
              "type": "FLAT",
              "vat": 19
            }
          ]
        }
      ],
      "endDateTime": "2026-09-02T15:03:09Z",
      "internalId": "CH*FR*SHE*9ddc09f2-1a66-47e9-b6f3-40b0d55tt923",
      "lastUpdated": "2025-09-10T08:43:09Z",
      "maxPrice": 999,
      "minPrice": 0,
      "operatorId": "FR*SHE",
      "powerRange": {
        "max": 150,
        "min": 0
      },
      "providerId": "Shell_RP_2",
      "startDateTime": "2026-01-21T08:43:09Z",
      "tariffAltText": null,
      "tariffId": "9ddc09f2-1a66-47e9-b6f3-40b0d55tt923",
      "tariffType": "DRIVER"
    }                              
]

Support

If you require assistance or have questions, please contact our technical team by raising a support ticket:

Raise a ticket

Select your language

EV Public Locations 2.1.2