Time registrationsDelete a time registration

Delete a time registration

Permanently deletes a time registration, by integer ID or by GUID.

Behaviour:

  • Not idempotent.
  • Safe to retry only under a condition. A retry after a lost response returns 500 Code 100 — the same as an unknown ID. Confirm with GET /{id} (also 500 Code 100 when gone) or your own records before treating it as success.
  • Side effect: Hard delete (row removed).
  • Side effect: Removes approval items; deletes work unit; updates invoicing/salary; recalculates financials.
  • Side effect: External keys of the registration are NOT removed (orphaned).

Not yet documented: examples.

curl -X DELETE "https://app3.timelog.com/your-account/api/v1/time-registration/123" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
"null"
DELETE
/v1/time-registration/{id}
DELETE
Base URLstring

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

Bearer Token
Bearer Tokenstring
Required

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.

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
idinteger
Required

TimeRegistrationID (integer) or TimeRegistrationGUID.

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

idinteger
Required

TimeRegistrationID (integer) or TimeRegistrationGUID.

Responses

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