ATK PRO / API REFERENCE
Fuel API (1.0)
This guide documents the published ATKPRO fuel-fill operations as four developer workflows: Get, Create, Update, and Delete.
How fuel records are identified
fuelFillID identifies one existing fuel-fill record. companyID and machineID filter the published list operation. Create and Update use the same /FuelFill/CreateEditFuelRecord endpoint, but are documented separately so developers supply the ID correctly.
The Swagger contract lists the parameters and types but does not mark them as required and does not publish response-body schemas. Validate business-required fields and response handling with the ATKPRO backend before production integration.
Get
Retrieve fuel-fill records using the filters published in Swagger.
List fuel records
/Maintenance/GetFuelFillsUse the numeric company identifier, an ISO 8601 date, and optionally a machine identifier. Swagger publishes a default machineID value of -1.
Query parameters
companyID |
integer <int32>
Numeric company identifier used to retrieve fuel fills. |
date |
string <date-time>
Date used by the published fuel-fill list operation. |
machineID |
integer <int32>
Optional machine filter. Swagger publishes a default value of -1. |
Example request
curl --request GET \
--url 'http://dev.bedamsure.com/Maintenance/GetFuelFills?companyID=1&date=2026-01-01T00%3A00%3A00Z&machineID=-1' \
--header 'accept: */*'Get one fuel record
/Maintenance/GetFuelFillfuelFillID |
integer <int32>
Fuel-fill record identifier to retrieve. |
Example request
curl --request GET \
--url 'http://dev.bedamsure.com/Maintenance/GetFuelFill?fuelFillID=123' \
--header 'accept: */*'Create
Create a new fuel-fill record with the combined Create/Edit operation. Do not supply an existing fuelFillID. Because Swagger does not define the exact new-record ID convention, confirm whether the backend expects the parameter to be omitted, empty, or zero.
Create fuel record
/FuelFill/CreateEditFuelRecordQuery parameters
fuelFillID |
integer <int32>
Fuel-fill record identifier. Supply the existing value when updating; the Swagger contract does not define the create-time empty-value convention. |
dateFilled |
string <date-time>
Date and time when the fuel was supplied. |
sourceId |
integer <int32>
Identifier of the source fuel tank or source record. |
destinationId |
integer <int32>
Identifier of the machine, tank, or destination receiving the fuel. |
sourceName |
string
Readable name of the fuel source. |
destinationName |
string
Readable name of the fuel destination. |
litres |
number <double>
Quantity of fuel supplied, in litres. |
cost |
number <double>
Cost recorded for this fuel transaction. |
machineHours |
number <double>
Machine hour reading at the time of the fuel fill. |
additionalInfo |
string
Optional notes or supporting information. |
fuelPurpose |
string
Business purpose for the fuel transaction. |
eligableRebate |
boolean
Whether the transaction is marked as eligible for a rebate. The parameter spelling follows Swagger. |
signatureUrl |
string
URL of the stored signature associated with the transaction. |
openingReading |
number <double>
Opening meter or tank reading. |
closingReading |
number <double>
Closing meter or tank reading. |
companyId |
integer <int32>
Numeric company identifier. The endpoint does not accept a company name in place of this ID. |
operatorUserId |
integer <int32>
Identifier of the operator who performed or recorded the fuel fill. |
rentalOrderNumber |
string
Related rental order number, when applicable. |
customerName |
string
Customer name associated with the transaction. |
siteName |
string
Site name associated with the transaction. |
activity |
string
Activity associated with the fuel usage. |
location |
string
Location where the transaction occurred. |
fuelFillType |
integer <int32> (FuelFillType)
Enum:
0 1Fuel-fill type published by Swagger. |
Example request
curl --request POST \
--url 'http://dev.bedamsure.com/FuelFill/CreateEditFuelRecord?dateFilled=2026-01-01T08%3A00%3A00Z&sourceId=10&destinationId=123&litres=50&cost=75&companyId=1&fuelFillType=0' \
--header 'accept: */*'Update
Update an existing fuel-fill record by supplying its fuelFillID together with the values that should be stored.
Update fuel record
/FuelFill/CreateEditFuelRecordQuery parameters
fuelFillID |
integer <int32>
Fuel-fill record identifier. Supply the existing value when updating; the Swagger contract does not define the create-time empty-value convention. |
dateFilled |
string <date-time>
Date and time when the fuel was supplied. |
sourceId |
integer <int32>
Identifier of the source fuel tank or source record. |
destinationId |
integer <int32>
Identifier of the machine, tank, or destination receiving the fuel. |
sourceName |
string
Readable name of the fuel source. |
destinationName |
string
Readable name of the fuel destination. |
litres |
number <double>
Quantity of fuel supplied, in litres. |
cost |
number <double>
Cost recorded for this fuel transaction. |
machineHours |
number <double>
Machine hour reading at the time of the fuel fill. |
additionalInfo |
string
Optional notes or supporting information. |
fuelPurpose |
string
Business purpose for the fuel transaction. |
eligableRebate |
boolean
Whether the transaction is marked as eligible for a rebate. The parameter spelling follows Swagger. |
signatureUrl |
string
URL of the stored signature associated with the transaction. |
openingReading |
number <double>
Opening meter or tank reading. |
closingReading |
number <double>
Closing meter or tank reading. |
companyId |
integer <int32>
Numeric company identifier. The endpoint does not accept a company name in place of this ID. |
operatorUserId |
integer <int32>
Identifier of the operator who performed or recorded the fuel fill. |
rentalOrderNumber |
string
Related rental order number, when applicable. |
customerName |
string
Customer name associated with the transaction. |
siteName |
string
Site name associated with the transaction. |
activity |
string
Activity associated with the fuel usage. |
location |
string
Location where the transaction occurred. |
fuelFillType |
integer <int32> (FuelFillType)
Enum:
0 1Fuel-fill type published by Swagger. |
Example request
curl --request POST \
--url 'http://dev.bedamsure.com/FuelFill/CreateEditFuelRecord?fuelFillID=123&dateFilled=2026-01-01T08%3A00%3A00Z&sourceId=10&destinationId=123&litres=55&cost=82.50&companyId=1&fuelFillType=0' \
--header 'accept: */*'Delete
Delete a fuel-fill record through ATKPRO’s shared delete operation.
Delete fuel record
/Admin/DeleteMasterMethodtableName and primaryKeyName values for fuel records before using this operation.Query parameters
primaryKeyID |
integer <int32>
Fuel-fill record identifier to delete. |
tableName |
string
Backend table name for fuel-fill records. Confirm the production value. |
primaryKeyName |
string
Backend primary-key column for fuel-fill records. Confirm the production value. |
Request template
curl --request POST \
--url 'http://dev.bedamsure.com/Admin/DeleteMasterMethod?primaryKeyID=123&tableName={CONFIRM_FUEL_TABLE}&primaryKeyName={CONFIRM_PRIMARY_KEY}' \
--header 'accept: */*'