Create Meter Entry
Create a new Meter Entry. If you need to create many Meter Entries at once, use the Bulk API to avoid Rate Limiting errors.
- application/json
Request Body
- vehicle_id integer required
Possible values:
>= 1
- value float required
The value of the meter. The unit can be configured at the
Account
level, or overridden at theVehicle
level. - date date-time required
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.
- void boolean
Default value:
false
Whether to mark this Meter Entry void or not. See Voiding Meter Entries.
- meter_type string
Possible values: [
secondary
]If a secondary meter is available, use this field to indicate that this is a secondary meter reading.
- 201
- 401
- 422
- 500
OK
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
- id integer
Possible values:
>= 1
- created_at date-time
The date and time at which this record was created.
- updated_at date-time
The date and time at which this record was most recently updated.
- account_id integer
Possible values:
>= 1
- auto_voided_at date-time
The date and time at which this Meter Entry was automatically voided.
- category string
Possible values: [
starting
,ending
,nightly
,manual
]A category to describe the function of this Meter Entry.
- meter_type string
Possible values: [
secondary
]Indicates whether or not this meter is a secondary meter.
- meterable_id NullableId
Possible values:
>= 1
- meterable_type string
Possible values: [
FuelEntry
,Issue
,PurchaseDetail
,ServiceEntry
,SubmittedInspectionItem
,VehicleAssignment
,WorkOrder
]The type of the object with which this Meter Entry is associated.
- value string
The current value of the meter.
- vehicle_id NullableId
Possible values:
>= 1
- void boolean
Default value:
false
Indicates whether or not this Meter Entry has been voided.
- gps_provider object
The GPS provider that submitted this Meter Entry.
- date date
The date on which this Meter Entry was recorded.
- vehicle_archived_at date-time
The date and time at which the
Vehicle
associated with this Meter Entry was archived, if applicable. - auto_void_reason string
The reason this Meter Entry was automatically voided.
- is_sample boolean
Default value:
false
Indicates whether or not this Meter Entry is sample data.
- gps_device_id NullableId
Possible values:
>= 1
- source string
The source of this Meter Entry.
- active_meter_conflicts_caused_count integer
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-11-06",
"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 (from schema)
Schema
- status integer
Possible values:
>= 400
and<= 599
- title string
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.
- detail string
A human-readable explanation specific to this occurrence of the problem.
- instance string
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 (from schema)
- Example
Schema
errors object
typeitems string
{
"errors": {}
}
{
"errors": {
"field1": [
"error1",
"error2"
],
"field2": [
"error3"
]
}
}
Something unexpected happened
- application/json
- Schema
- Example (from schema)
Schema
- status integer
Possible values:
>= 400
and<= 599
- title string
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.
- detail string
A human-readable explanation specific to this occurrence of the problem.
- instance string
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"
}