Time Trakkr webhooks
Time Trakkr sends signed webhooks to your own systems when time entries and invoices change.
What it does
Six eventsTime entries created, updated or deleted; invoices created, sent or paid.
Signed payloadsAn X-TT-Signature header carries an HMAC-SHA256 of the raw body, checked against your signing secret.
Test before you rely on itEach endpoint sends a sample delivery on demand, and failures are recorded in its deliveries list.
How to set it up
- A manager or admin opens the Developer page and adds an endpoint URL.
- Tick the events it should receive.
- Copy the signing secret. It is shown once.
- Select Test and check that your receiver verifies the signature.
What it won’t do
- Retry a failed delivery. Each is attempted once; poll the API for anything you must not miss.
- Deliver to a private or internal address. That is checked again on every delivery.
- Block the action that triggered it. A rejected webhook never stops someone’s time entry.
Questions about Webhooks
What does a payload look like?
Always { "event": ..., "data": ..., "sentAt": ... }, with the event name repeated in an X-TT-Event header so you can route without parsing the body.
Does invoice.created mean the client has the invoice?
No. It means a draft was created. invoice.sent fires when it is sent to the client.
Works well with
REST APIRead and write every part of the workspace with scoped tokens and an OpenAPI document.MCP serverPoint an MCP client such as Claude Code or Cursor straight at your workspace.SlackLog time with /track, and get reminders and approval notices as Slack DMs.
Every integration →
Connect Webhooks to your own workspace
Free for unlimited people. One paid plan, $10 per member per month, when you want HR, scheduling, timesheet approvals, scheduled backups, email from your own domain and scheduled reports.
Start free