Remote Tracker API Status
Understand the supported import path for Harvest, Toggl, Clockify, and other external time trackers.
Now, Eigenn public API v1 does not connect directly to Harvest, Toggl, Clockify, or another standalone time tracker. There are no public credential, connection-status, preview, confirmation, scheduled-sync, or sync-history endpoints for those providers.
Supported Integration Path
Use a server-side integration. The integration must do these steps:
- Store the provider credential outside Eigenn and outside browser storage.
- Read the completed entries from the provider.
- Map the provider users and projects to team-owned Eigenn UUIDs.
- Convert the duration to whole seconds.
- Convert the dates to
YYYY-MM-DD. - Submit the normalized records through
POST /tracker-entries/bulk. - Record the provider IDs and the import checkpoints in your own integration store.
See Tracker Entries and Timers for the complete bulk request contract.
Duplicate Protection
The bulk tracker endpoint supports Eigenn idempotency keys. But the tracker-entry model does not show a provider source ID or a provider-specific uniqueness key. We recommend that your integration keeps a stable provider-entry ID. We also recommend that you do not send the same logical entry two times.
Use one Eigenn idempotency key for one HTTP request. If a request times out, query the imported date range before you send it again. Do not generate a new idempotency key. Do not replay the same provider page blindly.
Credential Boundary
Never send provider tokens to Eigenn tracker endpoints. Keep them in a server-side secret manager. Exclude them from URLs, logs, analytics, client bundles, browser storage, and error messages.
What Is Available
The native REST tracker supports:
- project CRUD and billing defaults
- completed entry CRUD and bulk import
- active timer start, stop, current, and status operations
- reusable tracker categories
- project, date, customer, status, and category filters where documented