Delete an employee expense

Deletes an unapproved, uninvoiced employee expense together with all its receipt files.

Only the expense's employee, or a user with the 'all registrations' privilege, may delete it. Approved, invoiced, closed-period and completed-project / completed-contract expenses are refused, and all violated rules are reported together.

Use it to:

Expense app withdrawing a draft expense
Integration rolling back an expense it created in error before approval

Not for:

Removing only a receipt — DELETE /v1/employee-expense/{employeeExpenseID}/image / deletefile

Behaviour:

Not idempotent.
A second delete of the same ID fails with 500 Code 100 (the expense no longer exists).
Safe to retry only under a condition. Retry after a lost response only after checking with GET that the expense still exists (a 500 Code 100 on retry means the first call succeeded).
Duplicates: n/a
Changes are visible to the next read immediately.

Call first: GET /v1/employee-expense, GET /v1/employee-expense/{employeeExpenseID}

See also: DELETE /v1/employee-expense/{employeeExpenseID}/image, DELETE /v1/employee-expense/{employeeExpenseID}/file

Not yet documented: examples.

curl -X DELETE "https://app3.timelog.com/your-account/api/v1/employee-expense/123" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"

import requests
import json

url = "https://app3.timelog.com/your-account/api/v1/employee-expense/123"
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/employee-expense/123", {
  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/employee-expense/123", 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/employee-expense/123')
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"

{
  "Code": 102,
  "Details": [
    {
      "Message": "This expense is approved by the manager.",
      "ErrorCode": 37703
    }
  ],
  "Message": "Business rules exception.",
  "Parameters": "employeeExpenseID: 1",
  "Url": "https://app{server-number}.timelog.com/{account}/api/v2/employee-expense/1"
}

DELETE

/v1/employee-expense/{employeeExpenseID}

DELETE

Base URLstring

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

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

employeeExpenseIDinteger

Required

The expense's integer ID.

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

employeeExpenseIDinteger

Required

The expense's integer ID.

Responses

*Success without content: HTTP 200 with the literal JSON body null. Body is the JSON literal null.

Order: none

Empty result: none*

Was this page helpful?