Delete a mileage registration
Deletes an unapproved, uninvoiced mileage registration — by default together with its linked travel-time registration.
Deletes the registration, its financial data, invoicing potential and employee reimbursement posting. When a travel-time registration is linked, it is deleted too unless ?ignoreTravelTimeRegistration=true (then only the mileage goes; the time registration stays). Answers 200 with a JSON null body.
Use it to:
- Employee removing a trip registered by mistake
Not for:
- Approved or invoiced trips — refused (37848 / 37849)
Behaviour:
- Not idempotent.
- A second delete of the same ID fails with 500 Code 100 (row gone).
- Safe to retry only under a condition. Safe in effect — a retry after success fails with Code 100 but changes nothing.
- Side effect: Path (b): deletes the linked travel-time registration in the same transaction.
- Changes are visible to the next read immediately.
- Path (a) runs in one transaction scope; path (b) inside the time-registration delete transaction.
Call first: GET /v1/mileage-registration, GET /v1/mileage-registration/{mileageRegistrationID}
See also: DELETE /v1/time-registration/{id}
Not yet documented: behaviour → side effects; examples.
curl -X DELETE "https://app3.timelog.com/your-account/api/v1/mileage-registration/123?ignoreTravelTimeRegistration=false" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_TOKEN"
import requests
import json
url = "https://app3.timelog.com/your-account/api/v1/mileage-registration/123?ignoreTravelTimeRegistration=false"
headers = {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN"
}
response = requests.delete(url, headers=headers)
print(response.json())
const response = await fetch("https://app3.timelog.com/your-account/api/v1/mileage-registration/123?ignoreTravelTimeRegistration=false", {
method: "DELETE",
headers: {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN"
}
});
const data = await response.json();
console.log(data);
package main
import (
"fmt"
"net/http"
)
func main() {
req, err := http.NewRequest("DELETE", "https://app3.timelog.com/your-account/api/v1/mileage-registration/123?ignoreTravelTimeRegistration=false", nil)
if err != nil {
panic(err)
}
req.Header.Set("Content-Type", "application/json")
req.Header.Set("Authorization", "Bearer YOUR_API_TOKEN")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
fmt.Println("Response Status:", resp.Status)
}
require 'net/http'
require 'json'
uri = URI('https://app3.timelog.com/your-account/api/v1/mileage-registration/123?ignoreTravelTimeRegistration=false')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
request = Net::HTTP::Delete.new(uri)
request['Content-Type'] = 'application/json'
request['Authorization'] = 'Bearer YOUR_API_TOKEN'
response = http.request(request)
puts response.body
"null"
{
"error": "Unauthorized",
"message": "Authentication required. Please provide a valid API token",
"code": 401
}
{
"error": "Not Found",
"message": "The requested resource was not found",
"code": 404
}
{
"Code": 102,
"Details": [
{
"Message": "Mileage can not be deleted because it is approved",
"ErrorCode": 37848
}
],
"Message": "Business rules exception.",
"Parameters": "ignoreTravelTimeRegistration: false",
"Url": "https://app{server-number}.timelog.com/{account}/api/v1/mileage-registration/1"
}
{
"Code": 100,
"Details": [],
"Message": "Unknown error occur in system, please contact system administrator.",
"Parameters": "ignoreTravelTimeRegistration: false",
"Url": "https://app{server-number}.timelog.com/{account}/api/v1/mileage-registration/99999999"
}
/v1/mileage-registration/{mileageRegistrationID}Target server for requests. Edit to use your own host.
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.
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.The registration's integer ID.
true = delete only the mileage and keep the linked travel-time registration (its link is removed with the row). false = delete both.
Request Preview
Response
Response will appear here after sending the request
Authentication
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
The registration's integer ID.
Query Parameters
true = delete only the mileage and keep the linked travel-time registration (its link is removed with the row). false = delete both.
Responses
*Success without content: HTTP 200 with the literal JSON body null. Body is the JSON literal null.
Order: none
Empty result: none*