List an employee's competences
Returns one employee's competences and the value (rating) of each, grouped by competence group.
The read behind an employee's competence (skills) profile. Each item carries the employee-competence ID that PUT and DELETE /v2/employee-competences need, the competence and the value. isActive filters on the COMPETENCE's active state (not the employee's). An employee without competences — or an unknown userId — gives a response with no Properties at all, only the self link.
Use it to:
- Export employees' skills to an HR or resource-planning system
- Read the employee-competence IDs before changing or deleting a rating
Not for:
- The competence catalogue itself —
GET /v2/competences
Behaviour:
- Idempotent.
- Safe to retry.
- Changes are visible to the next read immediately.
Call first: GET /v1/user
Next: PUT /v2/employee-competences, DELETE /v2/employee-competences/{id}
See also: GET /v2/employee-competences/available, GET /v2/competences
Not yet documented: errors; examples; response → default ordering.
curl -X GET "https://app3.timelog.com/your-account/api/v2/employee-competences?userId=123&isActive=true" \
-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?userId=123&isActive=true"
headers = {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN"
}
response = requests.get(url, headers=headers)
print(response.json())
const response = await fetch("https://app3.timelog.com/your-account/api/v2/employee-competences?userId=123&isActive=true", {
method: "GET",
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("GET", "https://app3.timelog.com/your-account/api/v2/employee-competences?userId=123&isActive=true", 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?userId=123&isActive=true')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
request = Net::HTTP::Get.new(uri)
request['Content-Type'] = 'application/json'
request['Authorization'] = 'Bearer YOUR_API_TOKEN'
response = http.request(request)
puts response.body
{
"Properties": {
"UserId": 123,
"CompetenceList": [
{
"GroupId": 123,
"GroupName": "John Doe",
"Items": [
{
"Id": 123,
"CompetenceId": 123,
"Name": "John Doe",
"Value": 42
}
]
}
]
},
"Links": [
{
"Href": "example_string",
"Rel": "example_string"
}
],
"Actions": [
{}
]
}
{
"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": "UnsupportedApiVersion",
"error": "No route providing a controller name with API version '2' was found to match HTTP method 'GET' and request URI 'https://app{server-number}.timelog.com/{account}/api/v2/employee-competences'.",
"type": "https://docs.api-versioning.org/problems#unsupported",
"title": "Unsupported API version",
"status": 405,
"detail": "The requested resource with API version '2' does not support HTTP method 'GET'."
}
{
"error": "Internal Server Error",
"message": "An unexpected error occurred on the server",
"code": 500,
"requestId": "req_1234567890"
}
/v2/employee-competences
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. Missing → 405 'Unsupported API version' (captured) — a missing-parameter error, not a version problem.
Filters on EmployeeCompetenceRead.UserId (eq).
true = only active competences, false = only deactivated ones, omitted = all.
Filters on CompetenceRead.IsActive (eq).
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. Missing → 405 'Unsupported API version' (captured) — a missing-parameter error, not a version problem.
Filters on EmployeeCompetenceRead.UserId (eq).
true = only active competences, false = only deactivated ones, omitted = all.
Filters on CompetenceRead.IsActive (eq).
Responses
One employee's competences (skills), grouped by competence group. Each item carries the employee-competence ID (needed to change or delete that rating), the competence and the employee's value (rating) for it.