Skip to content

Changelog

2026-08-27 — HTML conversion

Converted from Carmoove_API_Car-Sharing_v1.13_FR.pdf (version 1.13, 27/10/2025) to this site.

The real backend source code (car-sharing-api, Go) was available for this API and was used for verification — a first for this conversion, as the two previous ones (Static Data, Dynamic Data) relied respectively on client-side consumer code and on no external source at all.

Checks performed:

  • All documented routes were checked against router.go, which lists every route actually registered by the API.
  • Authentication (v1/login.go): the /v1/login flow matches the PDF. However, the /v1/refreshToken response documented in the PDF (§4.2) only lists token and until — the source code shows it also includes refresh_token and refresh_until (RefreshResponse struct). Corrected in Authentication.
  • Bluetooth-token params/commands (v1/bluetooth.go, PDF §12.1-12.2): documented as POST /v1/bluetooth-token/params and POST /v1/bluetooth-token/commands with authorizationId in the body. The real handlers only accept the GET method, with authorizationId as a query parameter. Corrected in Endpoints. Two error codes returned by these endpoints (AUTHORIZATION_NOT_ACTIVE, AUTHORIZATION_EXPIRED) are not documented anywhere in the PDF; added to Errors.
  • Parking (v1/parking.go, PDF §14): the by-id endpoints are documented in the singular (/v1/parking/{id}) whereas the router registers them in the plural (/v1/parkings/{id}). The creation response field is documented as parkingId while the real JSON returns parking_id. Both corrected in Endpoints.
  • SIV data (§15): the PDF prints the route without a separator (GET /v1/vehicle/{id}siv) — a layout typo, corrected to /v1/vehicle/{id}/siv, confirmed by the router.

The rest of the documented surface (vehicles, devices, remote actions, statuses, authorization lists, bookings) was verified at the route existence/method level via router.go, but not field-by-field in the source code given the volume (over 60 routes) — beyond the corrections listed above, the content faithfully follows the PDF.

The source PDF's version-tracking table (below) is complete and consistent from one version to the next, unlike Dynamic Data's, which contained a truncated entry.

Prior history (PDF)

Date Version Change(s)
14/03/2022 0.1 Document created.
29/03/2022 1.0 1st version of the document.
28/07/2022 1.1 Added vehicle archiving function.
06/02/2023 1.2 Added device model identifier and feature availability.
21/04/2023 1.3 Added Teltonika-specific Bluetooth functions and license plate as a parameter for some functions.
13/05/2023 1.4 Added light and trunk commands, alternative parameterless GET requests, and fuel level in vehicle status.
20/09/2023 1.5 Added location privacy.
25/03/2024 1.6 Added list of vehicles authorized per user, deletion of a user's authorizations, status of scenarios configured on devices, and lists of current, expired, and upcoming authorizations.
18/07/2024 1.7 Added accessories installed with the device (parking/energy/other card detector, key detector).
27/01/2025 1.8 Added date of the last message sent by the device, status of a vehicle's various states (towing, maintenance, breakdown, theft…), offset/limit parameters in per-vehicle authorization lists, list of a vehicle's trips, and vehicle status updates.
11/02/2025 1.9 Added login with a user account, user password update, and a trip's start/end point.
10/03/2025 1.10 Added the INVALID_PASSWORD_LENGTH error for password updates. Changed vehicle creation.
01/04/2025 1.11 Added the CLOSE-WINDOWS and OPEN-WINDOWS actions, and window commands.
20/10/2025 1.12 Added booking and parking spot functions. Added energy and bluetoothName fields in vehicle information. Added encryptReadio and digitalOutput fields in Teltonika commands.
27/10/2025 1.13 Added extra data in the vehicle list, calls for bookings and parking, and a vehicle's SIV data.