Quickstart

Get the integration enabledCopy Anchor Link

Ask your Octane account manager to enable API integration on your account. Access requires that the integration is switched on for your account and that you have an active charging profile with Octane.

Send your IP addressesCopy Anchor Link

Production keys only accept requests from an allow-list of IP addresses or CIDR ranges that you provide. Send the public egress IPs of the systems that will call the API. The allow-list is applied on Octane's side before your key is switched on, so requests from other addresses are rejected with 403 IP_NOT_ALLOWED.

Optionally, provide an HTTPS webhook URL if you want Octane to push new transactions to you.

Receive your API keyCopy Anchor Link

Octane creates the key and shares it with you once, together with your webhook secret if you set a webhook URL. Neither value is shown again, so store them in a secrets manager immediately.

A key looks like this:

oct_live_a1b2c3d4_Gk7fP2xQ9vLm3nRt8wYb5cHj6sDz1eAu4iFo0pNq

The oct_live_ prefix identifies a production key. The a1b2c3d4 segment is a non-secret key prefix that Octane uses to identify your key in support conversations. The rest is the secret.

Make your first requestCopy Anchor Link

Fetch yesterday's confirmed transactions:

curl "https://prod-app.octanetech-api.com/api/v1/integration/transactions?from=2026-09-20T00:00:00Z&to=2026-09-21T00:00:00Z&limit=50" \
  -H "X-API-Key: $OCTANE_API_KEY"

A successful response looks like this (trimmed):

{
  "data": [
    {
      "id": 185432,
      "status": "CONFIRMED",
      "created_at": "2026-09-20T08:59:36.340Z",
      "confirmed_at": "2026-09-20T09:00:02.110Z",
      "corporate": { "id": 67, "name": "Acme Logistics" },
      "fuel": { "type": { "id": 2, "name": "Benzine 92" }, "liters": 18.5, "price_per_liter": 13.75, "amount": 254.38 },
      "fees": { "total_amount": 255.435000 }
    }
  ],
  "pagination": { "limit": 50, "has_more": false, "next_cursor": null }
}

See the Transactions endpoint for every field.

Receive your first webhook (optional)Copy Anchor Link

If you provided a webhook URL, Octane can send a webhook.test event on request so you can check connectivity and your signature verification before real traffic arrives. Ask your account manager to trigger it.

Your endpoint should:

1. Read the raw request body (before JSON parsing).
2. Verify the X-Octane-Signature header with your webhook secret. See Signature verification.
3. Respond with any 2xx status within 500 ms. Acknowledge first, process afterwards.

Only transactions created after the webhook URL was set are pushed, so use the Pull API to backfill history.