ProjectsValidate an allocation delete (dry run)

Validate an allocation delete (dry run)

Checks whether an allocation could be deleted, without deleting it.

Runs the checks of DELETE /v1/allocation/{allocationID} before its first write — the allocation exists, the caller has project privileges, and it has no time registrations or running time tracker — and answers 200 with null.

Use it to:

  • Ask before offering 'remove from task' in a staffing UI

Not for:

  • Deleting → DELETE /v1/allocation/{allocationID}

Behaviour:

  • Idempotent.
  • Safe to retry.
  • Changes are visible to the next read immediately.

Call first: GET /v1/task/{taskID}/allocation

Next: DELETE /v1/allocation/{allocationID}

Not yet documented: examples.

curl -X POST "https://app3.timelog.com/your-account/api/v1/allocation/123/validate-delete" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
"null"
POST
/v1/allocation/{allocationID}/validate-delete
POST
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
allocationIDinteger
Required

The allocation to check. Route constraint :int.

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

allocationIDinteger
Required

The allocation to check. Route constraint :int.

Responses

Success without content: HTTP 200 with the literal JSON body null. The literal null: the delete rule passes.