Correct an odometer reading you recorded

Required scope: charge-odometer:write
Organization authorization: supported

Only readings with source partner_api can be corrected; readings from a vehicle integration, the driver app or the operator hub are another party's evidence and are rejected with 403. Omitted fields are left untouched, so sourceRef can be overwritten but not cleared — record a new reading instead.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
int64
required
int64
required
Body Params
int32 | null
0 to 4000000

Corrected odometer reading in whole kilometres. Values outside 0-4000000 are rejected with 422.

date-time | null

Corrected time of the reading (ISO8601: yyyy-MM-ddTHH:mm:ssZ)

string | null

Corrected identifier for this reading. Maximum 128 characters. Omitted fields are left untouched, so an existing sourceRef can be overwritten but not cleared.

Responses

422

Validation failed on one of the supplied fields

Language
Credentials
Bearer
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json