EmployeeDelete a competence

Delete a competence

Permanently deletes a competence that no employee has.

Hard delete from the catalogue. Refused (38008) as soon as any employee has the competence — deactivate it with PUT instead, or remove the employee competences first. CompetenceRead.CanBeDeleted predicts the outcome.

Use it to:

  • Remove a competence created by mistake

Not for:

  • Retiring a competence employees have — PUT /v2/competences with IsActive false

Behaviour:

  • Not idempotent.
  • Safe to retry only under a condition. A repeat after success answers 500 Code 100 (row gone).
  • Side effect: Raises CompetenceDeleted.
  • Changes are visible to the next read immediately.

Call first: GET /v2/competences

See also: PUT /v2/competences, DELETE /v2/employee-competences/bulk

Not yet documented: examples.

curl -X DELETE "https://app3.timelog.com/your-account/api/v2/competences/123" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{}
DELETE
/v2/competences/{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

CompetenceRead.Id. Refers to CompetenceRead.Id. Look up valid values with GET /v2/competences.

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

idinteger
Required

CompetenceRead.Id.

Refers to CompetenceRead.Id. Look up valid values with GET /v2/competences.

Responses