Skip to main content
All Take Time API requests are authenticated with an API key passed as a Bearer token in the Authorization header. Generate your key in the app under Settings → Developer, then include it with every request.

​
API keys

Pass your key in the Authorization header on every request: 
Authorization: Bearer tt_live_your_key_here

​
Key types

PrefixEnvironmentDescription
tt_live_ProductionFull access to your real data
tt_test_SandboxTest mode — no real data is affected

​
Generate a key

1

Open Settings

In the Take Time app, navigate to the Settings tab (gear icon).
2

Go to the Developer section

Scroll to Developer and tap Generate API Key.
3

Copy and save your key

Copy the key immediately — it is only shown once. Store it in a secure location such as a password manager or secrets vault.
Never expose your API key in client-side code, public repositories, or browser requests. Always use it server-side or in a secure environment such as an MCP server config or environment variable.

​
Rate limits

PlanRequests / minRequests / day
Free301,000
Pro12010,000
When you exceed a rate limit, the API returns 429 Too Many Requests with a Retry-After header indicating how many seconds to wait before retrying.

​
Permissions

Each API key has full access to the owning account’s data. There are no granular permission scopes at this time.
Scoped permissions — such as read-only keys or per-resource access — are planned for a future release.

​
Using with the MCP Server

When configuring the Take Time MCP Server, pass your API key as an environment variable. The server reads TAKETIME_API_KEY and authenticates all requests automatically — you never need to handle the header yourself. 
{
  "mcpServers": {
    "taketime": {
      "command": "npx",
      "args": ["@taketime/mcp-server"],
      "env": {
        "TAKETIME_API_KEY": "tt_live_your_key_here"
      }
    }
  }
}
Use a tt_test_ key while setting up your MCP integration so no real data is modified during testing.