EmployeeRemove a competence from an employee

Remove a competence from an employee

Permanently removes one competence (and its value) from an employee.

Addressed by the employee-competence ID (EmployeeCompetenceItemRead.Id). Hard delete — no history is kept and there is no restore. Unlike create and update, deleting works for a deactivated employee.

Use it to:

  • Remove a skill recorded by mistake

Not for:

  • Removing all of an employee's competences — DELETE /v2/employee-competences/bulk

Behaviour:

  • Not idempotent.
  • Safe to retry only under a condition. A repeat after success answers 500 Code 100 (row gone) — treat that as 'already deleted' only after checking with GET.
  • Side effect: Raises CompetenceValueDeleted.
  • Changes are visible to the next read immediately.

Call first: GET /v2/employee-competences

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

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

EmployeeCompetenceItemRead.Id — the employee-competence ID, not the CompetenceId. Refers to EmployeeCompetenceItemRead.Id. Look up valid values with GET /v2/employee-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

EmployeeCompetenceItemRead.Id — the employee-competence ID, not the CompetenceId.

Refers to EmployeeCompetenceItemRead.Id. Look up valid values with GET /v2/employee-competences.

Responses