Introduction
The Octane Integration API lets your ERP, fleet or accounting system pull confirmed fuel transactions and receive them as signed webhooks. Start here.
The Octane Integration API gives your systems reliable, near-real-time access to your own fuel transaction data. It is designed for ERP, fleet-management and accounting integrations, and is available to Octane customers on request.
Two ways to get your data
Pull API
A REST endpoint that returns your confirmed and external transactions, filterable by date range, corporate group, corporate and status, with cursor-based pagination.
Webhooks (Push)
Octane calls a URL you provide whenever one of your transactions is confirmed or an external transaction is recorded. Every delivery is signed with HMAC-SHA256.
Both channels return the same transaction record, so you can start with the Pull API and add webhooks later without changing your data model.
How access works
| Authentication | A static, long-lived API key sent in the X-API-Key header. No login or token refresh. |
| Scope | A key belongs to one customer account and covers all of that customer's corporate groups and corporates. |
| Network | Production keys are pinned to an allow-list of your IP addresses, and each key is limited to 60 requests per minute. |
| Data | Only CONFIRMED and EXTERNAL transactions are ever returned or pushed. |
Keys are issued and managed by Octane. To get started, ask your Octane account manager to enable the integration for your account. See the Quickstart for the full onboarding checklist.
What is not included
- Self-service key management: keys are created, switched on and off by Octane.
- Notifications for later status changes (for example a transaction being voided after confirmation). See Detecting voids and cancellations.
- Keys scoped to a single corporate group or corporate. A key always covers the whole customer account.