Create Logistics Recharges (Bulk)
Create Logistics Recharges (Bulk)
Create multiple logistics recharges (fuel consumption records) in a single request
POST
Create Logistics Recharges (Bulk)
Create Logistics Recharges (Bulk)
Create multiple fuel consumption records in a single API call. Optimized for batch processing of up to 5,000 records per request.Request
Headers
Your API key for authenticationExample:
sk_live_1234567890abcdefYour organization UUIDExample:
a8315ef3-dd50-43f8-b7ce-d839e68d51faBody Parameters
Array of recharge records to create (1 to 5,000). Each record uses the same format as the single POST /recharges endpoint.Each record contains:
fuel_id(string, required): UUID of the fuel typecountry(string, required): ISO 3166-1 alpha-2 country codedate(string, required): Date in YYYY-MM-DD formatquantity(number): Amount of fuel consumedvehicle_license_plate(string): Vehicle license platetoc_id(string): UUID of the vehicle typeproject_id(string): UUID of a project to associate with
Processing options for the bulk operation.
continue_on_error(boolean, default:true): Iftrue, continues processing remaining records even if some fail. Iffalse, stops at the first error.
Response
Returns a summary of the bulk operation with HTTP 201.Number of successfully created recharges
Number of recharges that matched an existing record and were updated (upsert)
Array of error objects for records that failed to process
Example
Successful Response
| Field | Type | Description |
|---|---|---|
total_received | integer | Number of records in the request |
total_processed | integer | Records processed (success + failed) |
success | integer | Records created/updated successfully |
failed | integer | Records that failed validation |
results | array | Successfully processed records with their IDs |
errors | array | Error details for failed records |
Upsert Behavior
Records with the same combination ofcountry, date, quantity, and vehicle_license_plate within the organization are updated instead of duplicated. This matches the deduplication behavior of CSV file uploads.
Daily Batch Upload from CSV
Common Errors
401 Unauthorized
Cause: Missing or invalid API key403 Forbidden
Cause: The authenticated user is not a member of the organization422 Validation Error
Cause: Empty records array or exceeding 5,000 records.Partial Failures
Whencontinue_on_error is true (default), individual record failures are reported in the errors array while successfully processed records are included in results. Common per-record errors:
- Invalid
fuel_id: Fuel not found or inactive - Invalid
country: Not Valid Country Code, must be ISO 3166-1 alpha-2
Related Endpoints
Create Recharge
Create a single recharge
List Recharges
Retrieve fuel consumption records
Batch Delete Recharges
Delete multiple recharges at once
Create Requests (Bulk)
Bulk create shipment requests