Octane

Fuel transactions, straight into your ERP.

The Octane Integration API gives your fleet, ERP or accounting software every confirmed fuel transaction. Pull them by date range, or have Octane push each one to you the moment it is confirmed.

Start with the quickstartBrowse the API reference

Access is set up by your Octane account manager. No self-service signup.

One record, two ways to get it

Ask for transactions by date range with the Pull API, or give Octane an HTTPS endpoint and receive each one as a signed webhook seconds after it is confirmed. The transaction object is identical in both, so you can start with one channel and add the other later.

Pull API referenceWebhooks guide
GET /transactions?from=…&to=…Pull API response
{
  "data": [{
    "id": 185432,
    "status": "CONFIRMED",
    "confirmed_at": "2026-09-20T09:00:02Z",
    "vehicle": { "number_plate": "ABC 1234", … },
    "fuel": { "liters": 18.5, "amount": 254.38 },
    "fees": { "total_amount": 255.435000 }
  }],
  "pagination": { "has_more": false }
}
POST https://erp.example.com/octaneWebhook delivery
X-Octane-Event: transaction.confirmed
X-Octane-Signature: t=1758358803,v1=5257a8…

{
  "type": "transaction.confirmed",
  "data": { "transaction": { "id": 185432, … } }
}

How a transaction reaches you

  1. 1

    A driver fuels up

    The transaction is recorded at the station with the litres, the amount, the odometer reading and the pump photos.

  2. 2

    Octane confirms it

    Fraud checks pass, the amount is deducted from your balance, and the transaction becomes final.

  3. 3

    You receive it

    Within seconds as a signed webhook, or whenever you ask for it by date range through the Pull API. Same record, either way.

What a transaction contains

One record, identical whether you pull it or receive it by webhook. Amounts are rounded to two decimals; the total charged to your balance is kept at six so it reconciles exactly with your statement.

Read the full field reference
Vehicle
codenumber_platechassis_numberbrandmodeldepartment
Driver
idname
Fuel
typelitersprice_per_literamount
Station
nameprovideris_external
Totals
total_feestotal_vattotal_amount
Evidence
odometer_readingdistance_traveledfuel_consumptionimages

The essentials

Authentication
One static key per account, sent in the X-API-Key header
Base URL
https://prod-app.octanetech-api.com/api/v1/integration
Statuses
CONFIRMED and EXTERNAL transactions only
Pull limits
Up to 31 days per request, 100 records per page, 60 requests per minute
Webhook delivery
HMAC-SHA256 signed, 3 attempts, respond within 500 ms
Network
Production keys work only from the IP addresses you register

To get a key, ask your Octane account manager to enable API integration on your account and send them the public IP addresses your systems will call from. The quickstart walks through the rest.