EmployeeList competence groups

List competence groups

Lists all competence groups of the account, ordered by name.

The group level of System administration > Employee competencies. Flat: ID, name and a CanBeDeleted flag — the flag only says that no employee is rated on the group's competences, not that DELETE will succeed. Unpaged and unfiltered. For groups with their competences use GET /v2/competences/by-group.

Use it to:

  • Look up GroupId values for creating or moving competences
  • Map TimeLog competence groups to an external skills taxonomy

Not for:

  • Groups together with their competences — GET /v2/competences/by-group

Behaviour:

  • Idempotent.
  • Safe to retry.
  • Changes are visible to the next read immediately.

Next: PUT /v2/competence-groups, DELETE /v2/competence-groups/{id}, POST /v2/competences

See also: GET /v2/competences/by-group

curl -X GET "https://app3.timelog.com/your-account/api/v2/competence-groups" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "Entities": [
    {
      "Properties": {
        "GroupId": 1,
        "GroupName": "Skills",
        "CanBeDeleted": true
      }
    }
  ],
  "Links": [
    {
      "Href": "https://app{server-number}.timelog.com/{account}/api/v2/competence-groups",
      "Rel": "self"
    }
  ]
}
GET
/v2/competence-groups
GET
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.
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.

Responses

Entitiesarray

Omitted (not []) when the list is empty.

Linksarray