Get started: your first time registration

Generate a personal access token and build your site's base URL as described in Authentication. This guide uses v1 throughout.

export TIMELOG_TOKEN='<your-personal-access-token>'
export TIMELOG_BASE='https://app{server-number}.timelog.com/{account}/api/v1'

Every request below sends the token as Authorization: Bearer <token>.

GET /v1/user/me returns the user the token acts as. It changes nothing.

curl "$TIMELOG_BASE/user/me" \
  -H "Authorization: Bearer $TIMELOG_TOKEN" \
  -H "Accept: application/json"

A 200 response (abbreviated, e-mail redacted):

{
  "Properties": {
    "UserID": 1,
    "ID": "1b9afd4f-5ea9-4447-94bf-2bfd7ce96a25",
    "FirstName": "FirstName_Admin1",
    "LastName": "LastName",
    "IsActive": true,
    "UserType": "Employee",
    "Email": "<redacted>"
  },
  "Links": [
    { "Href": "https://app{server-number}.timelog.com/{account}/api/v1/user/me", "Rel": "self" }
  ]
}

Keep Properties.UserID (the integer). It is the UserID of your time registration in step 4. Do not use ID: that is the user's GUID.

A 401 means the token was not accepted. See Troubleshooting 401 responses.

GET /v1/task/search-for-time-tracking searches the tasks you are allocated to, by task name or task number. Without searchAll, it needs no extra privilege. See Permissions and data scope.

curl -G "$TIMELOG_BASE/task/search-for-time-tracking" \
  --data-urlencode "searchText=<part-of-a-task-name-or-number>" \
  -H "Authorization: Bearer $TIMELOG_TOKEN" \
  -H "Accept: application/json"

Results are ordered by TaskID, newest task first. A 200 response (one of ten entities shown, Actions removed):

{
  "Properties": { "TotalRecord": "1488", "TotalPage": "149", "PageNumber": "1" },
  "Entities": [
    {
      "Properties": {
        "TaskID": 4335,
        "ID": "57ebf93f-79a6-44d1-be44-a11803e90391",
        "Name": "TMSA006111",
        "No": "4303",
        "IsFixedPrice": false,
        "IsDefaultBillable": true,
        "AdditionalTextIsRequired": false,
        "ParentFullName": "TMSA006 » TMSA0061 » TMSA00611",
        "ProjectID": 450,
        "Project": null,
        "ParentTaskID": 4334,
        "IsTravelTimeTask": false,
        "IsFavourite": true
      },
      "Links": [
        { "Href": "https://app{server-number}.timelog.com/{account}/api/v1/task/4335", "Rel": "self" }
      ]
    }
  ]
}

Keep the task's TaskID (the integer, not the GUID ID). Also note IsFixedPrice: you need it in step 4.

No results is not an error: you get 200 with TotalRecord "0". It means no task you are allocated to matches searchText.

POST /v1/time-registration creates the registration. You choose its ID: generate a GUID on the client and send it as ID.

REGISTRATION_GUID=$(uuidgen)

curl -X POST "$TIMELOG_BASE/time-registration" \
  -H "Authorization: Bearer $TIMELOG_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -d '{
    "ID": "'"$REGISTRATION_GUID"'",
    "UserID": <user-id-from-step-2>,
    "TaskID": <task-id-from-step-3>,
    "GroupType": 1,
    "Date": "2026-10-14T00:00:00",
    "Hours": 1.5
  }'

These are the fields a project-time registration needs:

A few things to get right:

• Date: send the local date you want stored. No timezone conversion is applied. See Dates and times.
• Hours, not Minutes: for project time, Hours always wins and Minutes is ignored. See Numbers and units.
• Fixed-price tasks: Billable defaults to false, and a registration on a fixed-price task cannot be non-billable (ErrorCode 37620). If the task's IsFixedPrice is true, add "Billable": true.
• Account settings: some sites require a Comment or an AdditionalComment. The create then fails with ErrorCode 300116 or 30048 until you send it.

The other body fields (Billable, BillableHours, Comment, StartTime and more) are optional and described in the operation reference.

Response. A 200 returns the created registration under Properties, in the single-object envelope. Keep two values from it:

Retrying safely. Create is not idempotent, but the GUID makes it safe to retry. If the call times out, send it again with the same ID. A 422 with ErrorCode 38030 (duplicate ID) means the first attempt succeeded: treat it as "already created". A new GUID would create a second registration. See Data types and Safe retries.

To migrate historical hours with their original hourly rates, see the POST /v1/time-registration/import reference. It also creates one registration per call, but the server generates the GUID, so it is not safe to retry.

GET /v1/time-registration/{timeRegistrationID} returns one registration by its integer ID.

curl "$TIMELOG_BASE/time-registration/<time-registration-id-from-step-4>" \
  -H "Authorization: Bearer $TIMELOG_TOKEN" \
  -H "Accept: application/json"

The 200 response has the same properties as the create response. Check that UserID, Date and Hours are what you sent, and that TimeRegistrationGUID is your GUID. InterfaceCreated is 50 for registrations created through this API.

Things to know:

• Use the integer ID. A GUID does not match the route and returns 404.
• An unknown ID returns 500 with Code 100, not 404.
• Some values can differ from what you sent. For example, IsBillable can be set from the task, depending on account settings.

If this was a test, delete the registration. DELETE /v1/time-registration/{id} takes the integer TimeRegistrationID or the GUID you chose.

curl -X DELETE "$TIMELOG_BASE/time-registration/$REGISTRATION_GUID" \
  -H "Authorization: Bearer $TIMELOG_TOKEN" \
  -H "Accept: application/json"

A 200 response has the literal JSON body null. The delete is permanent.

Do not blindly retry a delete. A second delete returns 500 with Code 100, the same as an unknown ID. If a delete times out, check with step 5: a 500 with Code 100 there means the registration is gone.