Skip to main content

iWantFuel 3rd party Ordering API

Seamless Fuel Ordering for the Digital Era

Executive Summary

iWantFuel has redefined how businesses manage refuelling. With the release of our powerful new Fuel Ordering API, clients can now initiate and manage fuel purchases directly from third-party software, whether that’s a fleet management system, telematics platform, ERP, or custom-built application.

Our API supports integration across more than 20 development environments and languages, making fuel transactions faster, more secure, and fully automated.

This is not just an API, it’s the future of smart refuelling.

Why iWantFuel API?

Traditional refuelling methods are plagued by inefficiencies, delays, and fraud risk. Businesses rely on manual processes, fuel cards, and paper trails that are outdated and unreliable.

With the iWantFuel API, we solve these issues by enabling:

  • Real-time fuel orders from your existing software.
  • Geolocation-driven site selection based on price or proximity.
  • Automated driver and vehicle validation for complete control.
  • Upfront payment enforcement, eliminating credit risk.
  • Cross-platform compatibility with over 20 languages and libraries.

Core Use Cases

Use Case Benefit
Fleet Management Integration Automatically trigger fuel orders based on vehicle location, tank level, or route—no manual input needed.
ERP & Accounting Systems Seamlessly sync fuel orders and costs in real time, ensuring accurate and up-to-date financial records.
Logistics Platforms Enable dispatchers to place fuel orders directly within their workflow—no switching systems.
Mobile Apps Let drivers refuel effortlessly with no cards, no cash, and no admin—just tap and go.

Supported Technologies

Our RESTful API is compatible with the most widely used platforms and libraries, including:

  • Languages: C#, Java, JavaScript, PHP, Python, Go, Ruby, Swift, Kotlin, Objective-C, R, OCaml, Dart
  • Protocols & Tools: cURL, HTTP (raw), PowerShell, Shell (wget)
  • Frameworks: RestSharp, Fetch, Axios, URLSession, Guzzle, Requests, libcurl, Unirest, Dio, XHR

This ensures that any developer, anywhere, can implement the iWantFuel API in minutes.

Sample Payload

{
  "Asset_Reg": "CFM81479",
  "Driver_Mobile": "0711425972",
  "Asset_Latitude": "-33.90867357575131",
  "Asset_Longitude": "18.59708217135603",
  "Fill_Type": "Exact Quantity",
  "Best_Site_Price_Threshold_KM": "10",
  "Cheapest_or_Closest": "Closest",
  "internal_order_number": "",
  "Total_Litres_or_Currency": "100"
}

This payload lets the API intelligently determine the most suitable refuelling site (based on live pricing and distance), verify the driver and vehicle, and initiate a secure transaction instantly.

Payload Criteria & Validation

To ensure seamless processing and eliminate errors or fraud, the iWantFuel API enforces strict validation on the payload. Each field plays a critical role in determining eligibility, location matching, and transaction routing.

Here’s a breakdown of the required fields and their purpose:

Field Requirement Description
Asset_Reg Must be loaded under client profile The vehicle registration must exist on the client's account.
Driver_Mobile Must be loaded under client profile The mobile number must belong to an authorized driver in the client's profile.
Asset_Latitude & Asset_Longitude Required Determines the nearest or most cost-effective refuelling site. These must be accurate GPS coordinates.
Fill_Type Must be one of: Exact Quantity, Exact Currency, or Fill up Specifies how the fuel quantity or cost should be calculated.
Best_Site_Price_Threshold_KM Required Sets the maximum travel radius (in km) the asset is allowed to move for refuelling at the best price.
Cheapest_or_Closest Must be either: Cheapest or Closest Defines whether the system should prioritize cost savings or minimal travel distance.
internal_order_number Optional Can be used to pass through a reference from your internal ERP, TMS, or finance system.
Total_Litres_or_Currency Required The max amount (in litres or currency) the system should allocate. If Fill up is selected, it will cap based on the asset’s registered tank size.

If any of these fields are missing or invalid, the API will return a clear error message with an HTTP 422 status, helping integrators correct the issue quickly.

Security & Authentication

All API endpoints are protected using API key and Secret Key authentication. Clients are issued unique credentials to ensure secure and isolated usage.

Benefits to Your Business

All API endpoints are protected using API key and Secret Key authentication. Clients are issued unique credentials to ensure secure and isolated usage.

  • Zero fraud exposure, eliminate card skimming, duplicate swipes, and unauthorized refuels.
  • Zero paperwork, API-driven, with clean digital records
  • Zero delays, Orders placed instantly, drivers notified in real time.
  • Zero fees, no card fees, no subscription costs, no setup charges
  • Complete control, you choose how, when, and where vehicles refuel

Conclusion

The iWantFuel API is more than a technical integration, it’s a leap forward in fleet fuel management. By connecting your systems directly to our platform, you gain precision, efficiency, and security, all while reducing operating costs and eliminating fraud.

Whether you're a tech team looking to integrate, or a fleet manager wanting more control, our API is ready to plug into your workflow.

Get the Code

To activate your free Order API, please contact us at This email address is being protected from spambots. You need JavaScript enabled to view it..

We’ll also provide you with a complete Postman collection to help you get started quickly and easily.