Skip to main content
Each resource type is addressed differently. Getting this wrong is the most common cause of an unexpected 404.

Stations, chargers, and tariffs

These use id as their public stable identifier. IDs are exactly 8 alphanumeric characters (a-zA-Z0-9). A path ID in any other format returns 404 Not Found, the same as an ID that does not exist.
When these IDs are used as GET /sessions filters or in the POST /sessions/start body, an invalid format returns 400 Bad Request instead.

Customers

Customers use id, an opaque identifier that your system supplies when it creates the customer with PUT /customers/{id}. It must be unique within your account. Leading and trailing whitespace is trimmed.

Sessions

Sessions are addressed by a numeric session ID (a positive integer). It is returned as id on session responses and is the sessionId you pass to POST /sessions/stop.

Connectors

Connector IDs are 1-based positive integers, scoped to a charger. The API returns 404 Not Found when:
  • the path segment is not an integer,
  • the value is less than 1, or
  • the charger has no connector with that number.

Tariff references

tariffId fields in responses hold a tariff id, which you can pass to GET /tariffs/{id}. The field is omitted entirely when no tariff applies, so treat a missing field as “no tariff”, not as an error.