Retrieve your API token from the Toggl Track web app under Profile Settings; this token is used as the username in HTTP Basic Auth with the literal string api_token as the password.
Make authenticated requests to the Toggl Track API v9 base URL https://api.track.toggl.com/api/v9 using HTTP Basic Auth with Content-Type: application/json.
GET /me/time_entries with start_date and end_date query parameters (ISO 8601) to retrieve time entries for the authenticated user.
For workspace-wide data across all users, use the Reports API at https://reports.api.track.toggl.com/reports/api/v3; authenticate with the same API token via Basic Auth.
POST to the desired Reports API endpoint (e.g., /workspace/{workspace_id}/search/time_entries) with a JSON filter body to query entries by user, project, client, tag, or date range.
Handle pagination using the X-Next-Row-Number response header returned by the Reports API to fetch subsequent pages of large result sets.
Known gotchas
The Reports API and the main Track API have different base URLs and different endpoint structures; documentation for v3 of the Reports API is at engineering.toggl.com while v9 of the Track API is at developers.track.toggl.com.
Rate limits vary by subscription tier: free accounts have lower per-hour quotas; always check the current limits in the Toggl developer documentation rather than assuming a fixed number.
Time entries created via the API are workspace-scoped; you must use a workspace admin's API token to read or write entries for other users in that workspace.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp