An Open API, company webhooks, and single sign-on that plug straight into the tools your team already runs — no separate integration platform to buy.
Pull activity data into your own systems with the Open API, push project events out with webhooks, and let your team sign in with the account they already have.
Four ways ThirdEyee connects outward — pick the ones your stack actually needs.
A company-scoped API key unlocks two read endpoints — enough to feed your own BI tool, data warehouse, or internal dashboard without screen-scraping anything.
GET /api/v1/telemetry — activity logs for a given date: status, app, project, and activity %GET /api/v1/employees — your roster, with role and reporting linePoint a webhook URL at a project's completion event, and ThirdEyee posts to it automatically — no polling the API on a schedule.
project_complete, with more events plannedGoogle Workspace and Microsoft 365 / Azure AD login sit right alongside email and password — no separate ThirdEyee password for anyone to forget.
The desktop agent reads the active window title, not any calendar API, to tell when someone's on a call — so there's no OAuth grant to a meeting provider required.
No separate integration platform to buy or maintain
Generate or rotate a company API key from Settings — scoped to your workspace, nobody else's.
The Open API only reads data out; nothing about your workspace can be modified through it.
Tag each app your company uses with its monthly cost, and see spend sit right alongside actual usage.
Export audit logs and payroll to CSV directly, for the moments a spreadsheet is simpler than an API call.
Every webhook payload includes your company name, so one shared endpoint can still tell workspaces apart.
API access, webhooks, and SSO all come with the one plan — none of them are sold as a separate add-on.
Convenience that doesn't skip the checks
Only Admins and Super Admins can generate API keys or set a webhook URL — nobody else sees that screen.
An account created through Google or Microsoft still waits in the same sign-up approval queue as any other.
Regenerating an API key or updating a webhook URL shows up in the audit trail like any other admin action.
Webhook destinations are expected to be secure endpoints, not plain HTTP addresses.
Office IP allow-listing keeps working alongside SSO — one doesn't replace the other.
Data only ever goes to the API keys, webhook URLs, and SSO providers you've explicitly set up.