---
title: "Get time entry categories"
method: GET
path: "/1.0/time-entries/categories"
tags: ["Time Tracking"]
---

# Get time entry categories

`GET /1.0/time-entries/categories`

This endpoint can be used to fetch the time entry categories. This API returns a paginated object containing the various time entry categories present.

## Query parameters

- `pageSize` number
- `pageToken` string

## Response `200`

The requested action was successfully executed.

- ExampleAPIResponseTimeEntryCategories
  - `data` TimeEntryCategoryPublicForExample[] — Reflects all the default and custom fields and their values for the object searched, in an array format. If the includeFields param is utilised in the request body, it will return a customised response.
    - `categoryName` string — The name of the category.
    - `categoryId` integer — The unique identifier for the category.
  - `pagination` ExamplePaginationTimeEntryCategories — Responses that return multiple objects will be paginated. The pagination params define how pages are structured and how to traverse through pages.
    - `pageSize` integer — Denotes the page size mentioned in the current request (limit). It defaults to 100 if left blank.
    - `hasMore` boolean — Tells us if there is more content.
    - `totalRecordCount` integer — Denotes the total resources matching the filters.
    - `nextPage` string — Denotes an API URL, which can be conveniently called to perform the subsequent search call to get to the next page.
    - `nextPageToken` string — Denotes a unique token that points to the next page of resources. To get results from subsequent pages, you can use the nextPageToken available in the response under pagination. This token is valid for 15 minutes.

## Other responses

- `400` — This error typically happens when the request payload contains an error. If you want to make sure that the request's parameters are named correctly and are the right data types, you can examine the request's syntax.
- `401` — You see this error when trying to access this resource without being authenticated. Check the API request header to make sure it is not empty and has a valid api-key that you acquired from the Rocketlane API Settings tab.

---

[API](https://skmtc.net/rocketlane/apis/rocketlane-api.md) · [All operations](https://skmtc.net/rocketlane/apis/rocketlane-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/rocketlane/rocketlane-api/versions/1e8ba619e741/schema)