Skip to main content
Every resource is addressed by a stable, opaque, prefixed public ID. 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.
IDs are unique within a fleet and are not interchangeable with Nexus API identifiers, which use a different 8-character nexusID format.