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

# Conventions

> Response format and date/time conventions shared by all FuelBoss API endpoints.

All endpoints return JSON and require a valid access token unless otherwise specified.

<Info>
  This guide covers concepts and workflows. The API reference section of this tab documents every endpoint's request and response schema — including field-level descriptions and enumeration values — and includes an interactive playground.
</Info>

To stay compatible with [non-breaking changes](/fuelboss/api-integration-guide/versioning), your integration must ignore response fields it does not recognise and handle enum values it does not recognise — for example by treating them as "unknown" — rather than failing.

## Date and time formats

All dates and times sent to the API must be in **ISO 8601 format with an explicit UTC offset** — a numeric offset such as `+08:00` or `-04:00`, or `Z` for UTC:

```text theme={null}
2026-07-06T14:00:00+08:00
2026-07-06T14:00:00-04:00
2026-07-06T14:00:00Z
```

The offset you send is honored as-is: the value is interpreted as an absolute instant and stored in UTC. Timestamps **without** an offset (e.g. `2026-07-06T14:00:00` or `2026-07-06`) are **rejected with `400 Bad Request`**.

Unless suffixed with `Utc`, dates and times returned by the API are expressed in the **local time zone of the bunkering port**, with the port's UTC offset included (e.g. `2026-07-06T14:00:00+02:00` for a port in CEST). Fields suffixed with `Utc` (e.g. `lastChangedAtUtc`) are always returned in UTC.


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