Toggl Track
Toggl Track is a time-tracking and productivity platform for freelancers, teams, and agencies that captures billable hours, project time, and team capacity across web, desktop, mobile, and browser extension clients. The product offers automated tracking, calendar integration, custom reporting, 100+ integrations (Jira, Salesforce, Asana, GitHub), and supports billing, payroll, and project profitability use cases. The Toggl Track API v9 is a REST interface for time entries, workspaces, projects, clients, users, and reports using HTTP Basic Authentication with an API token.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Toggl Track the way a machine reads it — 10 machine-readable artifacts across 6 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Toggl Track scores 37.3/100 (thin), with a separate agent-readiness read of 41/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Toggl Track
Each block below is one kind of artifact we hold for Toggl Track. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Toggl Track API v9
Current REST API for managing time entries, workspaces, projects, clients, tags, tasks, users, and organizations in Toggl Track. Authentication uses HTTP Basic Auth with the API...
Toggl Track Reports API v3
Reporting API for generating detailed, summary, and weekly reports across time entries, with support for filtering, grouping, and export formats (JSON, CSV, PDF).
Toggl Track Webhooks API
Webhooks API for subscribing to events such as time entry creation, updates, deletions, and project changes within a workspace.
Toggl Track Me API
The Me API from Toggl Track — 1 operation(s) for me.
Toggl Track Reports API
The Reports API from Toggl Track — 3 operation(s) for reports.
Toggl Track Time Entries API
The Time Entries API from Toggl Track — 5 operation(s) for time entries.
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Toggl Track API
OPEN COLLECTIONSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Toggl Track — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/toggl · machine-readable index on apis.io