Salary and absenceList the caller's recently used absence codes

List the caller's recently used absence codes

Lists every absence code the calling user has ever registered absence on, most recently used first.

Returns the distinct absence codes found on the caller's own absence registrations, ordered by the newest registration on each (highest TimeRegistrationID, i.e. most recently CREATED — not latest absence date). There is no time window, no active filter and no salary-group scope: inactive codes, and codes the caller can no longer register on, are included. Limited-licence users, the Time product and PSA Starter plans get an empty list.

Use it to:

  • Show 'recently used' absence codes at the top of a self-service picker.

Not for:

  • Codes the caller may register on — use GET /v1/absence-code/{status} (and check IsActive).

Behaviour:

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

Next: POST /v1/absence-code/registration-by-hours, POST /v1/absence-code/registration-by-half-day, POST /v1/absence-code/registration-by-full-day

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

curl -X GET "https://app3.timelog.com/your-account/api/v1/absence-code/get-recently-registered?includeFavouriteOnly=false&$page=1&$pagesize=10" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "Properties": {
    "TotalRecord": "12",
    "TotalPage": "2",
    "PageNumber": "1"
  },
  "Entities": [
    {
      "Properties": {
        "AbsenceCodeID": 3,
        "AbsenceCode": "20",
        "Name": "Vacation",
        "Description": "Registration of vacation",
        "IsActive": true,
        "FlexPositiveFactor": 1,
        "SalaryAccountFactor": 1,
        "SalaryAccountFactorEffect": -1,
        "SalaryAccountID": 5,
        "AbsenceCodeTypeID": 2,
        "DeductCapacity": false,
        "TimeTrackingFormat": 2,
        "RequireApproval": true,
        "IsPublicVisible": true,
        "IsFavourite": true,
        "ID": "b0f671b5-81b8-46d5-adeb-d7ab064a2adc"
      },
      "Actions": [
        {
          "Name": "add-registration",
          "Title": "Add Registration",
          "Method": "Post",
          "Href": "https://app{server-number}.timelog.com/{account}/api/v1/absence-code/registration-by-half-day",
          "Type": "application/json",
          "Fields": [
            {
              "Name": "Type",
              "Type": "AbsenceCodeHalfDayValueTypes",
              "Enums": [
                "HalfDay",
                "FullDay"
              ]
            },
            {
              "Name": "AbsenceID",
              "Type": "Number"
            },
            {
              "Name": "Date",
              "Type": "DateTime"
            },
            {
              "Name": "Comment",
              "Type": "Text"
            }
          ]
        }
      ]
    },
    "… 9 more"
  ],
  "Links": [
    {
      "Href": "https://app{server-number}.timelog.com/{account}/api/v1/absence-code/get-recently-registered",
      "Rel": "self"
    }
  ]
}
GET
/v1/absence-code/get-recently-registered
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
includeFavouriteOnlyboolean

true → only the caller's favourite codes. Filters on AbsenceCodeRead.IsFavourite (eq).

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

includeFavouriteOnlyboolean

true → only the caller's favourite codes.

Filters on AbsenceCodeRead.IsFavourite (eq).

$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