Delete images from a project expense

Removes one or more attachments from a project expense and deletes the files from storage (same behaviour as deletefile).

Pass each attachment to remove as an imageUrl query parameter (repeat it for several). Every URL must be absolute and belong to the expense, otherwise 400 and nothing is deleted; then the URLs are deleted one at a time. Practical limit: the API never returns the URL of an IMAGE attached to a project expense, so the only URLs a pure API client can pass here are PDF URLs from FileUrls — which this route deletes too. Image URLs reach a client only from the TimeLog UI.

Use it to:

Removing an attachment whose URL the caller already holds (e.g. from the TimeLog UI)

Behaviour:

Not idempotent.
Repeating a successful call answers 400; nothing changes.
Safe to retry only under a condition. A retry of an already-applied call is harmless (400, nothing deleted).
Duplicates: Duplicate URLs in one call are collapsed.
On failure: A foreign or malformed URL: nothing is deleted.
Changes are visible to the next read immediately.

Call first: GET /v1/project-expense/{expenseID}

See also: DELETE /v1/project-expense/{expenseID}/file, POST /v1/project-expense/{expenseID}/image

Not yet documented: examples.

curl -X DELETE "https://app3.timelog.com/your-account/api/v1/project-expense/123/image?imageUrl=%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/v1/project-expense/123/image?imageUrl=%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/v1/project-expense/123/image?imageUrl=%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/v1/project-expense/123/image?imageUrl=%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/v1/project-expense/123/image?imageUrl=%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"

{
  "error": "Bad Request",
  "message": "The request contains invalid parameters or malformed data",
  "code": 400,
  "details": [
    {
      "field": "email",
      "message": "Invalid email format"
    }
  ]
}

DELETE

/v1/project-expense/{expenseID}/image

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

expenseIDinteger

Required

The project expense. Loaded after the URL check.

Format: int32

query

imageUrlarray

Required

An attachment URL of this expense (image or PDF), absolute and URL-encoded. Repeat the parameter for several.

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.