Record an odometer reading for a charge

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

The reading is stored with source set to partner_api — provenance cannot be chosen by the caller. Readings are append-only evidence: implausible jumps and decreases are never rejected at write time, they are surfaced asynchronously as verification results. To correct history, record a new reading.

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

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

date-time | null

When the reading was taken (ISO8601: yyyy-MM-ddTHH:mm:ssZ). Defaults to the time of the request.

string | null

Your own identifier for this reading, echoed back on reads. Maximum 128 characters.

Responses

422

Validation failed — odometerKm missing or outside 0-4000000, readingAt unparseable, or sourceRef longer than 128 characters

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