Delete receipt files from an employee expense (v2)

Removes one or more PDF (or other) receipt attachments from an employee expense and deletes the files from storage (v2 route).

Use it to:

Integration replacing a PDF receipt: delete the old URL, then attach the new PDF

Not for:

Deleting the whole expense — DELETE /v2/employee-expense/{employeeExpenseID}

Behaviour:

Not idempotent.
Repeating a successful call fails with 37684.
Safe to retry only under a condition. After a lost response, GET the expense: a URL that is gone was deleted.
Duplicates: A URL repeated in one call fails on its second occurrence (37684).
Changes are visible to the next read immediately.
Batch: partial

Call first: GET /v2/employee-expense/{employeeExpenseID}

Next: POST /v2/employee-expense/{employeeExpenseID}/file

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

curl -X DELETE "https://app3.timelog.com/your-account/api/v2/employee-expense/123/file?fileUrl=%5B%22example_string%22%5D" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"

import requests
import json

url = "https://app3.timelog.com/your-account/api/v2/employee-expense/123/file?fileUrl=%5B%22example_string%22%5D"
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/v2/employee-expense/123/file?fileUrl=%5B%22example_string%22%5D", {
  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/v2/employee-expense/123/file?fileUrl=%5B%22example_string%22%5D", 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/v2/employee-expense/123/file?fileUrl=%5B%22example_string%22%5D')
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": 100,
  "Message": "Unknown error occur in system, please contact system administrator.",
  "Details": [],
  "Parameters": "…",
  "Url": "https://app{server-number}.timelog.com/{account}/api/v2/employee-expense/{employeeExpenseID}/file"
}

DELETE

/v2/employee-expense/{employeeExpenseID}/file

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.

path

employeeExpenseIDinteger

Required

The expense.

Format: int32

query

fileUrlarray

An attachment URL of this expense, URL-encoded. Repeat for several. Matched on scheme + host + path; the query string is ignored. Default: none — the call then does nothing and returns 200

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.