Deletes a time entry.
The entry is addressed by its id alone; the authenticated service provider is what scopes the lookup, so an entry belonging to another service provider is reported as not found.
Only a time entry that is still open can be deleted. One that has been approved, completed or invoiced is rejected with 409, as is one that is void — deleting a settled entry would return it to the open pipeline while an invoice still bills the same hours. Reversing an approved or invoiced entry is a separate, explicit flow: delete the invoice item, then unapprove. An entry logged against a ticket that is closed is rejected with 409 as well, whatever its own billing state — reopen the ticket first.
For an entry that is still open, this behaves exactly as the app’s delete does, which is a
two-step: an entry waiting for approval is returned to unclosed and stays where it is, and
deleting it again deactivates it and reverts its billing ledger. The response’s
outcome says which happened — Reopened or Deleted. Deleting an entry that
is already deleted is accepted and reports Deleted without touching the ledger again.
Autorizações
Your Gorelo API key. See Generate API key. If your data is hosted in Australia, click the base URL at the top of this page and select https://api.aue.gorelo.io.
Parâmetros de caminho
Time entry to delete.
Resposta
OK
100, 101, 102, 103, 200, 201, 202, 203, 204, 205, 206, 207, 208, 226, 300, 301, 302, 303, 304, 305, 306, 307, 308, 400, 401, 402, 403, 404, 405, 406, 407, 408, 409, 410, 411, 412, 413, 414, 415, 416, 417, 421, 422, 423, 424, 426, 428, 429, 431, 451, 500, 501, 502, 503, 504, 505, 506, 507, 508, 510, 511 null