List time entries with the Clockify API

Lists the time entries of a user in a workspace, 50 per page. A page with fewer than 50 entries is the last one. With hydrated true, each entry brings its project, task and tags instead of only their ids.

Identifier
clockify_list_time_entries

The request

POST https://connect.reportei.com/api/tools/clockify_list_time_entries/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "workspaceId": "<workspaceId>",
    "userId": "<userId>"
  }
}

Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.

Parameters

ParameterTypeRequiredDescription
workspaceIdstringYesId of the workspace, from List workspaces or the activeWorkspace of Get current user.
userIdstringYesId of the user, from Get current user for the connected user or from List users for someone else.
startstringNoOnly entries from this moment on, as UTC in yyyy-MM-ddTHH:mm:ssZ, such as 2026-10-26T13:00:00Z.
endstringNoOnly entries up to this moment, as UTC in yyyy-MM-ddTHH:mm:ssZ, such as 2026-10-26T13:00:00Z.
descriptionstringNoOnly entries whose description contains this text.
projectstringNoOnly the entries of this project, by id from List projects.
taskstringNoOnly the entries of this task, by id from List tasks.
hydratedbooleanNoTrue to bring the project, task and tags of each entry.
pageintegerNoPage to fetch, starting at 1. Pages have 50 items, and a page with fewer is the last one.

Supported connections

Your customer connects their Clockify account once, with one of the modes below. The same connection serves every tool of the toolkit.

API key

Your customer pastes the app's key on a Connect screen, or your system sends the key with POST /api/customer-toolkits, with no screen.

When connecting, your customer also enters {region}: the address of their account on the app's API.

The response

On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.

Ready for AI agents

This tool's input is a JSON Schema, available at GET /api/tools/clockify_list_time_entries. It becomes your agent's tool definition with no conversion.

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.