EmployeesList employee types

List employee types

Lists all employee types of the account (HR classifications such as full time / part time), by name.

The value set for EmployeeTypeID on user create. Returns every employee type, active or not, in one response (no paging).

Use it to:

  • Map an HR system's employment categories to TimeLog EmployeeTypeIDs before creating users.

Behaviour:

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

Next: POST /v1/user/create

See also: GET /v1/normal-working-time

curl -X GET "https://app3.timelog.com/your-account/api/v1/employee-type" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "Entities": [
    {
      "Properties": {
        "EmployeeTypeID": 1,
        "ID": "77182991-ddaa-4339-9267-ea938073baca",
        "IsActive": true,
        "Name": "Full time employee"
      }
    },
    {
      "Properties": {
        "EmployeeTypeID": 3,
        "ID": "49fc3f62-cd04-4467-830b-fb259c5a472b",
        "IsActive": true,
        "Name": "Part time employee"
      }
    },
    {
      "Properties": {
        "EmployeeTypeID": 2,
        "ID": "1db73cbe-e1f0-4c48-ae9f-449fa2f12069",
        "IsActive": true,
        "Name": "Student assistant"
      }
    }
  ],
  "Links": [
    {
      "Href": "https://app{server-number}.timelog.com/{account}/api/v1/employee-type",
      "Rel": "self"
    }
  ]
}
GET
/v1/employee-type
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