SettingsDelete a car

Delete a car

Permanently deletes a car that has never been used on a mileage registration.

Hard delete. Refused (37830) as soon as any mileage registration uses the car — a car with history can only be deactivated, which the API cannot do. Ordinary users can delete only their own private cars; users with access to the car administration page can delete any unused car of the account.

Use it to:

  • Remove a car added by mistake

Behaviour:

  • Not idempotent.
  • Safe to retry only under a condition. A repeat after success hits an unknown id (500 Code 100).
  • Side effect: Clears the CALLER's default-car setting if it pointed to this car. Another user's setting that pointed to it is treated as empty from then on.
  • Changes are visible to the next read immediately.

Call first: GET /v1/car

See also: GET /v1/mileage-registration

Not yet documented: examples.

curl -X DELETE "https://app3.timelog.com/your-account/api/v1/car/123" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
"null"
DELETE
/v1/car/{id}
DELETE
Base URLstring

Target server for requests. Edit to use your own host.

Bearer Token
Bearer Tokenstring
Required

OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp). The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user. > Not yet documented: how to obtain a token. > Not yet documented: token lifetime.

OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp). The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user. > Not yet documented: how to obtain a token. > Not yet documented: token lifetime.
path
idinteger
Required

CarRead.CarID. Refers to CarRead.CarID. Look up valid values with GET /v1/car.

Format: int32
Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

Bearer token. OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp).

The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user.

Not yet documented: how to obtain a token.

Not yet documented: token lifetime.

Path Parameters

idinteger
Required

CarRead.CarID.

Refers to CarRead.CarID. Look up valid values with GET /v1/car.

Responses

*Success without content: HTTP 200 with the literal JSON body null. Literal JSON null (TafSuccessResult).

Order: none

Empty result: none*