Skip to content

Changelog

2026-08-27 — HTML conversion

Converted the documentation from Carmoove_API_Dynamic_Data_v1.6_FR.pdf (version 1.6, 24/11/2025) to this site.

A first pass (comparing the v1.5 and v1.6 PDFs, see history below) confirmed that version 1.6 adds two history endpoints — GET /v1/vehicles/history (all vehicles) and GET /v1/vehicle/{id}/history (specific vehicle) — whereas the corresponding entry in the source PDF's version tracking table explicitly mentions only the first of the two (a truncated entry in the original document).

The real backend for this API was then identified and verified: carmoove-backend/customer-services/usage-data-api (Go repo, cloned read-only via SSH — the name doesn't contain "dynamic", but its router.go matches the documented endpoints exactly, and its creation date, 15/07/2024, matches the PDF's creation date exactly). Several real discrepancies between the PDF and the implementation were corrected:

  • Field casing: the PDF capitalizes some field names (Id, VIN, Ignition, Movement, Mileage, Autonomy, Voltage, Energy, Temperature, Name, Data…) which are actually all lowercase in the real JSON (id, vin, ignition, movement, mileage, autonomy, voltage, energy, temperature, name, data). Fixed throughout Endpoints.
  • Response shape of "all vehicles" endpoints: the PDF presents their responses as a single object, whereas they are actually JSON arrays (one element per vehicle or per reading) — except GET /v1/vehicles/history, which returns an object { "status": [...], "error": ... }.
  • GET /v1/vehicle/{id}/history and GET /v1/vehicles/history: the PDF doesn't specify the response shape; in reality, both return an object { "status": [...], "error": ... } where each element of status does not include the state object (unlike the current-status /status endpoints).
  • trip object: two fields, first_position and last_position (each { latitude, longitude }), exist in the real response but aren't documented in the PDF. Added to Endpoints.
  • POST /v1/login: the real response includes three fields absent from the PDF — refresh_token, refresh_until, and update_password. Added to Authentication.
  • POST /v1/refreshToken: a real endpoint, entirely absent from the PDF (whereas the equivalent exists and is documented on the Car Sharing API side). Added to Authentication.
  • Undocumented endpoints, not added to this site (changing a vehicle's status rather than reading it — out of scope for the PDF, mentioned here for information): POST /v1/vehicle/{id}/state/{stolen|accident|maintenance|breakdown|towing} and POST /v1/vehicle/{id}/privacy/{on|off}.

Everything else (the vehicle, location, can, status, electric, sensors, state structures, the list of endpoints and their routes, the UNKNOWN_VEHICLE/NO_DATA error codes) matches the real implementation.

Earlier history (PDF)

Date Version Change(s)
15/07/2024 1.0 1st version of the document.
26/07/2024 1.1 Proofreading and formatting.
06/09/2024 1.2 Added information about the limit on the number of data points reported by the API.
04/10/2024 1.3 Added data from external sensors.
18/11/2024 1.4 Added electric vehicle data.
23/01/2025 1.5 Added vehicle states (towing, service, breakdown, …) and the list of a vehicle's trips.
24/11/2025 1.6 Added a call to retrieve the history of all vehicles (truncated entry in the source PDF — the real implementation shows that a per-vehicle history endpoint was also added).