🧪 Create Fuel Transaction
Create a new fuel transaction. The fuel transaction will be created asynchronously, and you can check the status of the operation using the returned operation ID.
This endpoint is available for early access. The core schema is stable, but minor details — such as field names or added fields — may change before it becomes generally available. Backward compatibility is not guaranteed.
See API Stability & Versioning for details on provisional endpoints.
Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Query Parameters
Whether to process the request synchronously. If true, Catena will attempt to create or update the resource immediately with the TSP and return the result in the response. When performing synchronous operations, you are responsible for handling any necessary retries in case of transient failures.If false (default), Catena will create an asynchronous operation, and you can check the status of the operation using the returned operation ID.
Body
Fuel transaction model for creating new records
Unique identifier of the connection at Catena Telematics which will be used to create this resource. A connection represents a Fleet/TSP pairing.
Volume of fuel purchased
Unit for fuel_volume
m3, l, us_gal, uk_gal Catena identifier for the driver
Catena identifier for the vehicle
Catena identifier for the co-driver
Latitude of the location where the fuel transaction occurred in decimal degrees.
-90 <= x <= 90Longitude of the location where the fuel transaction occurred in decimal degrees.
-180 <= x <= 180Human-readable location where the fuel transaction occurred
Vehicle odometer reading at the time of the transaction
Unit for odometer
m, km, mi, ft, nmi Timestamp of the transaction as reported by the source system (must be UTC)
Jurisdiction where the transaction occurred (e.g., state or province code)
AL, AK, AZ, AR, CA, CO, CT, DE, FL, GA, HI, ID, IL, IN, IA, KS, KY, LA, ME, MD, MA, MI, MN, MS, MO, MT, NE, NV, NH, NJ, NM, NY, NC, ND, OH, OK, OR, PA, RI, SC, SD, TN, TX, UT, VT, VA, WA, WV, WI, WY, DC, AS, GU, MP, PR, VI, AB, BC, MB, NB, NL, NS, NT, NU, ON, PE, QC, SK, YT Type of fuel purchased
GASOLINE, GASOLINE, GASOLINE, DIESEL, DIESEL, DIESEL, ETHANOL, ETHANOL, ETHANOL, METHANOL, METHANOL, PROPANE, LPG, CNG, LNG, HYDROGEN, ELECTRICITY, HYBRID Name of the fuel vendor or station
Total cost of the transaction
Currency of the total cost
Response
The fuel transaction was created successfully.
Resource operation model
The ID of the partner that created the operation.
The ID of the connection
The type of resource to operate on (e.g., vehicle, driver).
asset, driver_association, driver_vehicle_association, driver_event_log, driver_safety_event, dvir_log, dvir_log_defect, engine_log, engine_status, fuel_transaction, fleet_info, hos_availability, hos_daily_snapshot, hos_event, hos_event_annotation, hos_event_attachment, hos_violation, ifta_summary, location_segment, message, group_message, user, vehicle, vehicle_location, vehicle_sensor, vehicle_region_segment, trailer, trailer_association, trailer_vehicle_association, trailer_location, trailer_status, workflow The type of operation to perform (e.g., create, update).
create, update The payload of the operation, containing the resource attributes to be created or updated.
Unique identifier for the resource operation.
Immutable: The datetime the record was created in Catena Telematics.
The datetime the record was last modified in Catena Telematics.
The datetime the record was logically deleted from Catena Telematics.
Unique identifier of the record. Can be null for create operations where the source does not exist yet.
The unique identifier of the resource in the source system. Required for update operations.
The status of the operation
pending, success, failed Log entries for each attempt to execute this operation.