> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ionage.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Identifiers

> How Nexus resources are addressed in paths and responses

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.

```text theme={null}
GET /stations/A1B2C3D4
```

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.

```text theme={null}
GET /stations/{stationId}/chargers/{chargerId}/connectors/1
```

## 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.