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

> Prefixed opaque IDs and how to store them

Every resource is addressed by a stable, opaque, prefixed public ID.

| Prefix | Resource | Example |
| - | - | - |
| `op_` | Operator | `op_9df5f4f7b0f64f9e` |
| `st_` | Station | `st_d1ed2dd3f9ef4b4e` |
| `ch_` | Charger | `ch_2cf24dba5fb0a30e` |
| `con_` | Connector | `con_3a7bd3e2360a3d80` |
| `drv_` | Driver | `drv_9df5f4f7b0f64f9e` |
| `veh_` | Vehicle | `veh_9df5f4f7b0f64f9e` |
| `ses_` | Session | `ses_9df5f4f7b0f64f9e` |
| `res_` | Restriction | `res_708192a3b4c5d6e7` |

Payment transactions are the exception: they use a `TXN`-prefixed reference such as
`TXN20260917_7K4N2P9R5T8V3X6Z`.

## Store them verbatim

Persist these IDs as the key for anything you hold about a FLO resource. Specifically,
do not key your records on:

* **your own database IDs** — they do not round-trip through the API,
* **phone numbers** — a driver's number can change,
* **registration numbers** — a vehicle's plate can change.

Treat the IDs as opaque strings. The prefix is a readability aid, not a contract to
parse; do not derive a type by slicing the string, and do not assume a fixed length.

> [!NOTE]
>
> IDs are unique within a fleet and are not interchangeable with Nexus API
> identifiers, which use a different 8-character `nexusID` format.


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