Open API and integrations
Hours are input for other systems: payroll, invoicing, planning, reporting. TimeTracking is built to be connected: the REST API, webhooks, the CLI, the MCP server and the Claude Skill are live today, with more ready-made connectors on the way.
How to connect TimeTracking
Create an API key
Admins create API keys per organisation with the scopes they need. Keys can be revoked at any time.
Read, write and listen
Use the REST API to read approved hours, create entries in batches, upsert people and placements by your own external IDs, or trigger exports. Subscribe to webhooks to hear about changes as they happen.
Use what is ready
Live today: configurable CSV, XLSX and JSON exports, an SD Worx-format concept preset, webhooks, the tt CLI, the MCP server and the Claude Skill. Native apps for Zapier and Make, Slack and Teams, calendars and more payroll presets are coming soon.
What is live and what is coming
We mark integration status honestly. Live today: the REST API with an OpenAPI 1.1 description, signed webhooks with retries and replay, the tt command-line tool, the MCP server with a Claude Skill, configurable CSV, XLSX and JSON exports and an SD Worx-format concept preset. Coming soon: presets for Loket, Nmbrs, AFAS and DATEV, Google Calendar and Outlook sync for predictive tracking, Slack and Microsoft Teams, native Zapier and Make apps, and SSO with SCIM.
Each integration has its own page with its current status, so you know exactly what you can use today.
- Live: REST API, webhooks and the tt CLI
- Live: MCP server and Claude Skill
- Live: configurable CSV, XLSX and JSON exports, SD Worx-format preset
- Coming soon: payroll presets, calendars, Slack, Teams, Zapier and Make apps, SSO and SCIM
Your data stays open
TimeTracking does not lock your data in. Every plan can export to CSV, XLSX and JSON, and a full account export is available at any time. If you ever leave, you take everything with you.
That openness also makes switching in easier: the API's batch endpoints and external-ID upserts let you load people, clients and placements from another system without creating duplicates.
Built for AI agents too
The MCP server lets assistants like Claude read and update time data with the same permissions as the user who connects it, and the Claude Skill teaches Claude the common TimeTracking tasks. Ask for last week's overtime per client, or prepare a payroll check, in plain language. Both are live today.
Common integration patterns
Most connections follow a few patterns. A nightly job reads approved hours into a data warehouse or reporting tool. A back office or applicant tracking system pushes people, clients and placements into TimeTracking, so nobody enters them twice. And a payroll or invoicing process listens for a webhook and fetches an export as soon as a period is approved.
Until the native Zapier and Make apps arrive, the same automations work today with a webhook trigger and an HTTP step that calls the API. The OpenAPI description makes it straightforward to generate a client in the language your team uses, list endpoints are paginated, and requests are rate limited to keep the platform fast for everyone.
- Read approved hours into reporting
- Sync people, clients and placements by external ID
- React to webhooks after approval
Frequently asked questions
Is there a public API?
Yes. A REST API with an OpenAPI 1.1 description is available today, with pagination, batch endpoints and external-ID upserts. Higher rate limits are part of the Pro plan.
Which integrations are live today?
The REST API, webhooks, the tt CLI, the MCP server and Claude Skill, configurable CSV, XLSX and JSON exports and an SD Worx-format concept preset. Other connectors are marked as coming soon.
Can I export all my data?
Yes. Every plan includes CSV, XLSX and JSON exports, and you can request a full account export at any time.
Are there webhooks?
Yes. Webhooks are live. Every delivery is signed, failed deliveries are retried, and you can replay past events.
Related pages
Payroll exports
Approved hours out in the format payroll expects. SD Worx-format and configurable CSV/XLSX today.
Claude (MCP and Skill)
Ask Claude about hours and approvals through the TimeTracking MCP server and Claude Skill. Live.
SD Worx
Approved hours exported in SD Worx format. Live today.
See pricing
Free for up to 5 users. Core from €1 per user per month, everything included.
Try TimeTracking free
Free for up to 5 users. Core from €1 per user per month, everything included.