Delete a competence group
Permanently deletes an empty competence group.
Hard delete. Refused (38011) while the group contains any competence — rated or not, active or not. Nothing is cascaded: empty the group first (move its competences with PUT /v2/competences, or delete them, which in turn requires that no employee has them). Do NOT rely on CompetenceGroupRead.CanBeDeleted: it is true whenever no employee is rated on the group, even if the group still contains competences.
Use it to:
- Remove an empty or mistakenly created group
Not for:
- Removing a group with its competences in one call — not supported
Behaviour:
- Not idempotent.
- Safe to retry only under a condition. A repeat after success answers 500 Code 100 (row gone).
- Side effect: No competences or ratings are touched — a group that has any is refused.
- Side effect: Raises CompetenceGroupDeleted.
- Changes are visible to the next read immediately.
Call first: GET /v2/competence-groups, GET /v2/competences
See also: DELETE /v2/competences/{id}, PUT /v2/competences
Not yet documented: examples.
curl -X DELETE "https://app3.timelog.com/your-account/api/v2/competence-groups/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/competence-groups/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/competence-groups/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/competence-groups/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/competence-groups/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
{}
{
"error": "Bad Request",
"message": "The request contains invalid parameters or malformed data",
"code": 400,
"details": [
{
"field": "email",
"message": "Invalid email format"
}
]
}
{
"error": "Unauthorized",
"message": "Authentication required. Please provide a valid API token",
"code": 401
}
{
"Code": 102,
"Details": [
{
"Message": "Unable to Delete competence group with ID ='1', because one or more competence are attached to it",
"ErrorCode": 38011
}
],
"Message": "Business rules exception.",
"Parameters": "id: 1",
"Url": "https://app{server-number}.timelog.com/{account}/api/v2/competence-groups/1"
}
/v2/competence-groups/{id}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.CompetenceGroupRead.GroupId.
Refers to CompetenceGroupRead.GroupId. Look up valid values with GET /v2/competence-groups.
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.
Path Parameters
CompetenceGroupRead.GroupId.
Refers to CompetenceGroupRead.GroupId. Look up valid values with GET /v2/competence-groups.