Read the EVSE IDs imported from your previous CSMS

get/v1/tenants/{tenant_id}/ocpi/evse-ids
Requires an API key

The eMI3 EVSE IDs published instead of Ivora's generated ones, so partners keep the IDs they know after you move your network to Ivora. Requires stations:read.

Path parameters

  • tenant_idintegerRequired

Returns · 200

  • tenant_idintegerRequired
  • partyOcpiPartyRequired
    Child attributes
    • country_codestringRequired
    • party_idstringRequired
    • sharedbooleanRequired
      true: Ivora's shared party US*IVR.
  • dataarray of OcpiEvseIdRequired
    By station and EVSE number.
    Child attributes
    • station_idintegerRequired
    • evse_numberintegerRequired
    • evse_idstringRequired
    • appliesbooleanRequired
      Whether partners receive this ID now: its party is the one your locations publish under (party). Otherwise the EVSE is published with Ivora's generated ID until staff approve that party.
    • updated_bystringRequired
    • updated_atstringRequired
GET /v1/tenants/{tenant_id}/ocpi/evse-ids
curl --fail-with-body "https://api.ivoracharge.com/v1/tenants/1042/ocpi/evse-ids" \
  -H "Authorization: Bearer $IVORA_API_KEY"
Response · 200
{
  "tenant_id": 1042,
  "party": {
    "country_code": "string",
    "party_id": "party_0123456789abcdef",
    "shared": false
  },
  "data": [
    {
      "station_id": 1,
      "evse_number": 1,
      "evse_id": "evse_0123456789abcdef",
      "applies": false,
      "updated_by": "string",
      "updated_at": "2026-09-30T17:00:00Z"
    }
  ]
}
Try it is not available here yetRequests from this page are off until the production API at https://api.ivoracharge.com is public. Use the code samples from your application server; Ivora grants production access. Keys are created in Developer tools.