Fuel Operations
The authorize request starts a fueling session at a specific fueling point. When this endpoint is called, the API has no information about whether/how the customer has paid; only that the pump should be released for fueling. The terminate request stops the running transaction; this can be used to stop a session before the customer has finished fueling, and may occur at any time after a successful authorize.
See Authorize fueling and Terminate fueling in the API Reference for the endpoint details, and Events for the payload of the state-change events these operations trigger.
Possible pump states
These are the possible states a fuel pump can report (via SiteInformation / pump status, and
reflected in stateId on events). You may not see every status; it depends on how the terminal
connected to the pump is configured.
| Status Description | Id |
|---|---|
| Idle - ready to authorize | 0 |
| Fueling in progress | 1 |
| Busy | 2 |
| Unavailable - nozzle lifted | 3 |
| Pump error | 4 |
| Offline | 5 |
| Closed | 6 |
| Not ready for app operation | 7 |
| Unknown | 99 |
After a fueling operation completes, use the transactionId returned during authorization to
fetch transaction details. See Get transaction in the API Reference.