Salary and absenceList salary accounts

List salary accounts

Lists every salary account of the account, active or not, newest first.

The value set for salaryAccountId on the posting and aggregation operations and for SalaryAccountID on absence codes. Returns account definitions only — no balances and no BalanceFormat (the unit of the account's balance).

Use it to:

  • Map payroll balance types (flex, vacation, supplements) to TimeLog SalaryAccountIDs before reading balances.

Behaviour:

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

Next: GET /v1/salary-account/{salaryAccountId}/aggregation, POST /v1/salary-account/{salaryAccountId}/posting

See also: GET /v1/absence-code/{status}

curl -X GET "https://app3.timelog.com/your-account/api/v1/salary-account?$page=1&$pagesize=10" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "Properties": {
    "TotalRecord": "12",
    "TotalPage": "2",
    "PageNumber": "1"
  },
  "Entities": [
    {
      "Properties": {
        "SalaryAccountID": 18,
        "Name": "Addtional absence full day",
        "SalaryAccountGUID": "6471db1c-928c-4e23-a607-7f46fb8db0d6",
        "Description": "Addtional absence full day",
        "IsActive": true,
        "IsSystemSalaryAccount": false
      }
    },
    "… 9 more"
  ],
  "Links": [
    {
      "Href": "https://app{server-number}.timelog.com/{account}/api/v1/salary-account",
      "Rel": "self"
    }
  ]
}
GET
/v1/salary-account
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.
query
$pageinteger

Page number.

query
$pagesizeinteger

Page size. No maximum enforced in the API layer.

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.

Query Parameters

$pageinteger

Page number.

$pagesizeinteger

Page size. No maximum enforced in the API layer.

Responses

Propertiesobject

Paging values. They are returned as STRINGS, for example "TotalRecord": "12".

Entitiesarray

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

Linksarray