---
title: "Create Meter Entry"
method: POST
path: "/meter_entries"
tags: ["Meter Entries"]
---

# Create Meter Entry

`POST /meter_entries`

## Request

- Base URL: `https://secure.fleetio.com/api`
- URL: `https://secure.fleetio.com/api/meter_entries`
- Auth: API key in header `Authorization` and API key in header `Account-Token`
- TypeScript: <https://skmtc.dev/fleetio/apis/fleetio-developer-api/docs/meter_entries/post.ts> (a function with typed inputs; its response is checked against the schema)

Create a new Meter Entry. If you need to create many Meter Entries at once,
use the [Bulk API](/docs/overview/bulk-api) to avoid [Rate Limiting
errors](/docs/overview/rate-limiting).

## Request body

- object
  - `vehicle_id` integer, required
  - `value` number, float, required: The value of the meter. The unit can be configured at the `Account` level, or overridden at the `Vehicle` level.
  - `date` string, 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](/docs/overview/date-formatting) formatted dates to avoid ambiguity.
  - `void` boolean: Whether to mark this Meter Entry void or not. See [Voiding Meter Entries](https://help.fleetio.com/s/article/Meter-Entry-Mark-As-Void-Unmark-As-Void).
  - `meter_type` 'secondary', nullable: 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.

## Response `201`

OK

- MeterEntryCreated, nullable: A MeterEntry
  - `id` integer, required
  - `created_at` string, date-time: The date and time at which this record was created.
  - `updated_at` string, date-time: The date and time at which this record was most recently updated.
  - `account_id` integer, required
  - `auto_voided_at` string, date-time, nullable, required: The date and time at which this Meter Entry was automatically voided.
  - `category` 'starting' | 'ending' | 'nightly' | 'manual', nullable, required: A category to describe the function of this Meter Entry.
  - `meter_type` 'secondary', nullable, required: Indicates whether this Meter Entry is for a secondary meter.
  - `meterable_id` integer, nullable, required
  - `meterable_type` 'FuelEntry' | 'Issue' | 'PurchaseDetail' | 'ServiceEntry' | 'SubmittedInspectionItem' | 'VehicleAssignment' | 'WorkOrder', nullable, required: The type of the object with which this Meter Entry is associated.
  - `value` string, required: The current value of the meter.
  - `vehicle_id` integer, nullable, required
  - `void` boolean, required: Indicates whether or not this Meter Entry has been voided.
  - `gps_provider` object, nullable, required: The GPS provider that submitted this Meter Entry.
  - `date` string, date, required: The date on which this Meter Entry was recorded.
  - `vehicle_archived_at` string, date-time, nullable: The date and time at which the `Vehicle` associated with this Meter Entry was archived, if applicable.
  - `auto_void_reason` string, nullable: The reason this Meter Entry was automatically voided.
  - `is_sample` boolean: Indicates whether or not this Meter Entry is sample data.
  - `gps_device_id` integer, nullable
  - `source` string, nullable: The source of this Meter Entry.
  - `active_meter_conflicts_caused_count` integer: The number of active meter conflicts caused by this Meter Entry.

## Other responses

- `401`: Request could not be authenticated
- `422`: Unprocessable Entity
- `500`: Something unexpected happened

---

[API](https://skmtc.dev/fleetio/apis/fleetio-developer-api.md) - [All operations](https://skmtc.dev/fleetio/apis/fleetio-developer-api/llms.txt) - [OpenAPI document](https://skmtc.dev/fleetio/apis/fleetio-developer-api/revisions/49558d744bd7?raw)