Remove all of an employee's competences
Permanently deletes every competence of one employee, or every competence of one competence group.
Hard delete of the employee's competence rows — all of them, or with groupId > 0 only those whose competence belongs to that group. The call reaches this action only with userId in the query: without it the request falls through to DELETE /employee-competences/{id} and is rejected as "The value 'bulk' is not valid for Int32.".
Use it to:
- Reset an employee's skills profile before a full re-import
- Clear one competence group for an employee (groupId)
Not for:
- Removing one competence —
DELETE /v2/employee-competences/{id}
Behaviour:
- Idempotent.
- A repeat deletes nothing more and answers 204.
- Safe to retry.
- Side effect: Raises CompetenceValueBatchDeleted once, with no domain object (description 'CompetenceValueBatchDeletedForUser<userId>').
- On failure: 403: nothing deleted (the check runs first).
- Changes are visible to the next read immediately.
- Batch: One DELETE statement.
Call first: GET /v1/user
Next: POST /v2/employee-competences/bulk
See also: DELETE /v2/employee-competences/{id}
Not yet documented: examples.
curl -X DELETE "https://app3.timelog.com/your-account/api/v2/employee-competences/bulk?userId=123&groupId=123" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_TOKEN"
import requests
import json
url = "https://app3.timelog.com/your-account/api/v2/employee-competences/bulk?userId=123&groupId=123"
headers = {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN"
}
response = requests.delete(url, headers=headers)
print(response.json())
const response = await fetch("https://app3.timelog.com/your-account/api/v2/employee-competences/bulk?userId=123&groupId=123", {
method: "DELETE",
headers: {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN"
}
});
const data = await response.json();
console.log(data);
package main
import (
"fmt"
"net/http"
)
func main() {
req, err := http.NewRequest("DELETE", "https://app3.timelog.com/your-account/api/v2/employee-competences/bulk?userId=123&groupId=123", nil)
if err != nil {
panic(err)
}
req.Header.Set("Content-Type", "application/json")
req.Header.Set("Authorization", "Bearer YOUR_API_TOKEN")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
fmt.Println("Response Status:", resp.Status)
}
require 'net/http'
require 'json'
uri = URI('https://app3.timelog.com/your-account/api/v2/employee-competences/bulk?userId=123&groupId=123')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
request = Net::HTTP::Delete.new(uri)
request['Content-Type'] = 'application/json'
request['Authorization'] = 'Bearer YOUR_API_TOKEN'
response = http.request(request)
puts response.body
{}
{
"Code": 200,
"Details": [
"The value 'bulk' is not valid for Int32."
],
"Message": "Invalid model state error.",
"Parameters": "id: null",
"Url": "https://app{server-number}.timelog.com/{account}/api/v2/employee-competences/bulk"
}
{
"error": "Unauthorized",
"message": "Authentication required. Please provide a valid API token",
"code": 401
}
{
"error": "Forbidden",
"message": "You don't have permission to access this resource",
"code": 403
}
{
"error": "Internal Server Error",
"message": "An unexpected error occurred on the server",
"code": 500,
"requestId": "req_1234567890"
}
/v2/employee-competences/bulk
Target server for requests. Edit to use your own host.
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.
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.UserID of the employee.
Refers to UserRead.UserID. Look up valid values with GET /v1/user.
Limit the delete to competences of this group. Omitted, 0 or negative = ALL the employee's competences. An unknown group deletes nothing.
Filters on EmployeeCompetenceGroupRead.GroupId (eq).
Refers to CompetenceGroupDetailRead.GroupId. Look up valid values with GET /v2/competences/by-group.
Request Preview
Response
Response will appear here after sending the request
Authentication
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.
Query Parameters
UserID of the employee.
Refers to UserRead.UserID. Look up valid values with GET /v1/user.
Limit the delete to competences of this group. Omitted, 0 or negative = ALL the employee's competences. An unknown group deletes nothing.
Filters on EmployeeCompetenceGroupRead.GroupId (eq).
Refers to CompetenceGroupDetailRead.GroupId. Look up valid values with GET /v2/competences/by-group.