For developers

TimeHunter API + integrations — REST API, webhook, CSV and PREMIER export

Your TimeHunter data doesn’t have to stay in TimeHunter. A documented REST API, API keys, an event webhook, plus CSV and PREMIER exports for payroll.

REST API and API keys

The API documentation covers the app’s endpoints: login, time tracking, attendance and reports. For server-to-server integrations an admin generates API keys in the panel. With a key (X-Api-Key header) you can read attendance, i.e. employees’ work sessions for a chosen day or date range. Any key can be revoked in one click without affecting the others.

API keys

Name, permissions, optional expiry date and last-used date. You see the full key only once; we store only its hash.

API documentation

A list of endpoints with descriptions on the public docs page.

Event webhook

Employee clocked in or out? Submitted a leave request? We POST to your URL.

Exports for payroll

Instead of retyping hours from a spreadsheet, you download a ready monthly file and hand it to your accountant or load it into your payroll software.

CSV export (PL and CZ)

Per employee: days and hours worked, overtime, breaks, leave and sick days. Open it in Excel or import it into any software that accepts CSV.

PREMIER export (CZ)

A file for the Czech PREMIER payroll software. You set the pay-component codes for your company and see a preview with warnings before downloading.

XLSX and PDF reports

A period report in XLSX and a monthly PDF with each employee’s working-time records.

Webhook — a notification when something happens

Instead of polling the API, you can enter your system’s HTTPS address in the settings. TimeHunter sends it a POST request with JSON data when an employee clocks in or out, starts or ends a break, submits a leave request, or when a request is decided. Each event is sent once, so if your system must not miss any, pair the webhook with periodic reads through the API.

6 event types

work_start, work_stop, break_start, break_end, leave_request_created, leave_request_status.

HTTPS only

The URL must use HTTPS, and internal network addresses are blocked.

Test from the panel

Send a test event from the settings and check that your server receives it.

Example use cases

Attendance in your own system

Work sessions for a chosen period, read with an API key, feed your payroll system or ERP.

Office attendance board

Clock-in and clock-out events from the webhook update a screen at reception or on the shop floor.

Reacting to events

A webhook about a new leave request triggers a process in your system, no polling needed.

Frequently asked questions

Are API keys included in every plan?
API key access depends on the plan — see the plan comparison in the pricing section. The webhook and exports are set up by an admin in settings and reports.
Is the webhook retried if my server doesn’t respond?
No. Each event is sent once, with a 10-second response timeout. If you can’t afford to miss an event, pair the webhook with periodic reads through the API.
Can I build a custom export for a niche payroll program?
Yes, in two ways: download the generic CSV and convert it to your program’s format, or read attendance through the API and process the data on your side.

Try 14 days free

Start a 14-day trial. No card required, full functionality.

Related pages

This website uses cookies

We use cookies to ensure proper functioning of the service, analyze traffic and personalize content. Learn more in our Privacy Policy