---
title: "Update Meter Entry"
method: PATCH
path: "/meter_entries/{id}"
tags: ["Meter Entries"]
---

# Update Meter Entry

`PATCH /meter_entries/{id}`

## Request

- Base URL: `https://secure.fleetio.com/api`
- URL: `https://secure.fleetio.com/api/meter_entries/{id}`
- 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/:id/patch.ts> (a function with typed inputs; its response is checked against the schema)

Update a Meter Entry

## Path parameters

- `id` string, required

## Request body

- object
  - `vehicle_id` integer
  - `value` number, float: The value of the meter. The unit can be configured at the `Account` level, or overridden at the `Vehicle` level.
  - `date` string, date-time: 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 `204`

OK

## Other responses

- `401`: Request could not be authenticated
- `404`: The requested resource could not be located
- `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)