Create Meter Entry
POSThttps://secure.fleetio.com/api/v1/meter_entries
Create a new Meter Entry. If you need to create many Meter Entries at once, use the Bulk API to avoid Rate Limiting errors.
Request
- application/json
Body
Possible values: >= 1
The value of the meter.
The unit can be configured at the Account
level, or overridden at the Vehicle
level.
Meter Entries must follow the correct sequence, incrementing in value by date. For each entry, Fleetio validates to ensure that the value falls between any entries logged before and/or after. We recommend using ISO-8601 formatted dates to avoid ambiguity.
2023-03-14T13:46:27-06:00
Whether to mark this Meter Entry void or not. See Voiding Meter Entries.
false
If this is a secondary meter reading, use this field.
If the vehicle's secondary meter is disabled, secondary meter values will be hidden in the web and mobile views until enabled.
Possible values: [secondary
]
Responses
- 201
- 401
- 422
- 500
OK
Response Headers
- application/json
- Schema
- Example (auto)
Schema
Possible values: >= 1
The date and time at which this record was created.
2023-03-14T13:46:27-06:00
The date and time at which this record was most recently updated.
2023-03-14T13:46:27-06:00
Possible values: >= 1
The date and time at which this Meter Entry was automatically voided.
2023-03-14T13:46:27-06:00
A category to describe the function of this Meter Entry.
Possible values: [starting
, ending
, nightly
, manual
]
Indicates whether this Meter Entry is for a secondary meter.
Possible values: [secondary
]
Possible values: >= 1
The type of the object with which this Meter Entry is associated.
Possible values: [FuelEntry
, Issue
, PurchaseDetail
, ServiceEntry
, SubmittedInspectionItem
, VehicleAssignment
, WorkOrder
]
The current value of the meter.
Possible values: >= 1
Indicates whether or not this Meter Entry has been voided.
false
The GPS provider that submitted this Meter Entry.
The date on which this Meter Entry was recorded.
2023-03-14
The date and time at which the Vehicle
associated with this Meter Entry
was archived, if applicable.
The reason this Meter Entry was automatically voided.
Indicates whether or not this Meter Entry is sample data.
false
Possible values: >= 1
The source of this Meter Entry.
The number of active meter conflicts caused by this Meter Entry.
{
"id": 0,
"created_at": "2023-03-14T13:46:27-06:00",
"updated_at": "2023-03-14T13:46:27-06:00",
"account_id": 0,
"auto_voided_at": "2023-03-14T13:46:27-06:00",
"category": "starting",
"meter_type": "secondary",
"meterable_id": 0,
"meterable_type": "FuelEntry",
"value": "string",
"vehicle_id": 0,
"void": false,
"gps_provider": {},
"date": "2023-03-14",
"vehicle_archived_at": "2024-07-29T15:51:28.071Z",
"auto_void_reason": "string",
"is_sample": false,
"gps_device_id": 0,
"source": "string",
"active_meter_conflicts_caused_count": 0
}
Request could not be authenticated
- application/json
- Schema
- Example (auto)
Schema
Possible values: >= 400
and <= 599
A short, human-readable summary of the problem type. It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization.
A human-readable explanation specific to this occurrence of the problem.
A URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.
{
"status": 0,
"title": "string",
"detail": "string",
"instance": "string"
}
Unprocessable Entity
- application/json
- Schema
- Example (auto)
- Example
Schema
errors object
{
"errors": {}
}
{
"errors": {
"field1": [
"error1",
"error2"
],
"field2": [
"error3"
]
}
}
Something unexpected happened
- application/json
- Schema
- Example (auto)
Schema
Possible values: >= 400
and <= 599
A short, human-readable summary of the problem type. It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization.
A human-readable explanation specific to this occurrence of the problem.
A URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.
{
"status": 0,
"title": "string",
"detail": "string",
"instance": "string"
}
Authorization: Authorization
name: Authorizationtype: apiKeyin: headerdescription: Prefix the value with "Token", for example: "Token 76cbe06c49a64". You can generate a new API key [here](https://secure.fleetio.com/api_keys).
name: Account-Tokentype: apiKeyin: headerdescription: You can find your Account-Token [here](https://secure.fleetio.com/api_keys)
- curl
- ruby
- python
- csharp
- go
- java
- nodejs
- php
- CURL