Create a competence group

Creates a competence group in the account's competence catalogue.

Adds a group under which competences are then created (POST /v2/competences with GroupId). The response is a literal null with no ID: read the new GroupId back with GET /v2/competence-groups. Names are not unique. Every new group gets the five-point rating scale; the scale is not settable over the API.

Use it to:

Set up a skills taxonomy from an external HR system

Behaviour:

Not idempotent.
Not safe to retry blindly. Names are not unique: a retry after a lost response creates a duplicate group. List first.
Duplicates: Not deduplicated — no uniqueness on Name.
Changes are visible to the next read immediately.

Next: GET /v2/competence-groups, POST /v2/competences

See also: PUT /v2/competence-groups

Not yet documented: examples.

curl -X POST "https://app3.timelog.com/your-account/api/v2/competence-groups" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -d '{
  "Name": "John Doe"
}'

import requests
import json

url = "https://app3.timelog.com/your-account/api/v2/competence-groups"
headers = {
  "Content-Type": "application/json",
  "Authorization": "Bearer YOUR_API_TOKEN"
}
data = {
  "Name": "John Doe"
}

response = requests.post(url, headers=headers, json=data)
print(response.json())

const response = await fetch("https://app3.timelog.com/your-account/api/v2/competence-groups", {
  method: "POST",
  headers: {
  "Content-Type": "application/json",
  "Authorization": "Bearer YOUR_API_TOKEN"
},
  body: JSON.stringify({
  "Name": "John Doe"
})
});

const data = await response.json();
console.log(data);

package main

import (
    "fmt"
    "net/http"
    "bytes"
    "encoding/json"
)

func main() {
    data := []byte(`{
  "Name": "John Doe"
}`)

    req, err := http.NewRequest("POST", "https://app3.timelog.com/your-account/api/v2/competence-groups", bytes.NewBuffer(data))
    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')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true

request = Net::HTTP::Post.new(uri)
request['Content-Type'] = 'application/json'
request['Authorization'] = 'Bearer YOUR_API_TOKEN'
request.body = '{
  "Name": "John Doe"
}'

response = http.request(request)
puts response.body

"null"

{
  "Code": 102,
  "Details": [
    {
      "Message": "Name must be set on CompetenceGroup",
      "ErrorCode": 60015
    }
  ],
  "Message": "Business rules exception.",
  "Parameters": "model: {"Name":null}",
  "Url": "https://app{server-number}.timelog.com/{account}/api/v2/competence-groups"
}

POST

/v2/competence-groups

POST

Base URLstring

Target server for requests. Edit to use your own host.

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.

Content-Typestring

Required

The media type of the request body

Options: application/json

Namestring

Required

Group name. Duplicates are allowed. Can be set on create only. - Missing, empty or whitespace — 500 Code 102 / 60015 'Name must be set on CompetenceGroup' (captured). > Not yet documented: behaviour.

Min length: 1 • Max length: 255

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.

Body

application/json

Namestring

Required

Group name. Duplicates are allowed.

Can be set on create only.

Missing, empty or whitespace — 500 Code 102 / 60015 'Name must be set on CompetenceGroup' (captured).

Not yet documented: behaviour.

Responses

*Success without content: HTTP 200 with the literal JSON body null. Literal JSON null (TafSuccessResult).

Order: none

Empty result: none*

Was this page helpful?