Clockify

1. Sign in at clockify.me.
2. Open your Profile Settings (avatar menu, top right) and scroll to the API section.
3. Click Generate to create a personal API key.
4. Copy the key value — Clockify shows it once on creation, but you can regenerate later if needed.

In the Ingest UI under Connectors → Clockify, paste the key. Ingest stores it in AWS Secrets Manager under the key api_key. The runtime sends it as the X-Api-Key request header on every call.

Clockify publishes a 10 req/sec per-API-key cap. The Ingest runtime dispatches conservatively at 5 req/sec by default and uses AIMD backoff on 429s. Errors with status 401 (bad key) or 403 (paid-plan endpoint on a free workspace) are treated as fatal — the request stops without retry.

The connector currently fetches up to 5,000 records per endpoint per parent in a single request (Clockify's API maximum for a single page). Workspaces with more than 5,000 records in any one endpoint will miss the overflow until the runtime gains a 1-indexed page-pagination type — flag this with your Ingest contact if it affects you.

The Clockify cascade is rooted at workspaces. Most customers want workspaces, projects, tasks, time_entries, and clients — the core time-tracking dataset. The full set:

• workspaces, user, workspace_users, groups — identity and structure
• projects, clients, tags, tasks — work-tracking taxonomy
• time_entries, time_entries_in_progress — the actual recorded work
• expenses, expense_categories, invoices — the billing surface
• approval_requests, holidays — workflow features
• custom_fields, policies — paid-plan only (403 on free workspaces)