Get summary report with the Toggl Track API

Returns the tracked time of a workspace in a period, in seconds, grouped by project, client or user and sub-grouped, for everyone the user can see. Requires start_date. The groups and sub-groups bring ids, whose names come from List projects and List clients.

Identifier
toggl_get_summary_report

The request

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

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "workspace_id": 1,
    "start_date": "<start_date>"
  }
}

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
workspace_idintegerYesId of the workspace: the default_workspace_id from Get me, the workspace_id of a project from List projects, or the wid of a client from List clients.
start_datestringYesFirst day of the period, as yyyy-MM-dd.
end_datestringNoLast day of the period, as yyyy-MM-dd, included.
groupingstringNoWhat the groups are: projects (the default), clients or users.
sub_groupingstringNoWhat each group is split by: time_entries (the default), tasks, projects, clients or users, never the same as grouping.
project_idsarrayNoOnly these projects, by id from List projects.
client_idsarrayNoOnly these clients, by id from List clients.
descriptionstringNoOnly entries whose description matches this text.
billablebooleanNoTrue for billable time only, false for non-billable only. Paid plans only.

Supported connections

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

Username and password

Your customer enters the app credentials on a Connect screen, or your system sends them with POST /api/customer-toolkits, with no screen.

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/toggl_get_summary_report. It becomes your agent's tool definition with no conversion.

Other Toggl Track tools

See all 13 tools

Toolkits in the same category

See all 100 toolkits

See Connect applied to your product.

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