Reference

API reference

TimerOS has no public API, and one isn’t on our roadmap right now: our data structure still changes too often for us to promise an API that keeps working through our updates. There is no REST API for developers, no personal access tokens and no documented endpoints you can build on. Below you’ll find what you can use instead and how to tell us what you need.

On the website dashboard, the Settings → API & webhooks section is a “Coming soon” placeholder; the desktop and web apps don’t have this section. Nothing on that screen works. It shows ideas, not plans.

Available now: the AI assistant connector

The main integration available today is the AI assistant connector, a hosted MCP server at https://api.timeros.ai/mcp. It lets an assistant such as Claude act as you, within your own permissions, after you sign in and approve read or read-and-write access, and optionally access to your incidents and change requests. Its OAuth server exists only to sign assistants in on your behalf. It is not a general developer API: its tokens work only with the MCP server, so there is no token for the REST API and nothing a script can call outside an MCP client. It also does not support dynamic client registration.

The only other one is a GitHub connection for AI employees (beta). Connect your GitHub account in Company Settings, and AI employees can read the repositories linked to their projects and open pull requests. Each push, and each merge of a pull request, needs an approval first: a person’s or, on an internal project without a client, that of an AI Executive above the AI employee, when the AI Executive’s “Decides its team’s requests” switch is on. An AI Executive’s approval merges only under strict rules: where the repository’s branch rules on GitHub still have to pass, GitHub merges exactly the approved commit once they do; otherwise only when those rules require checks, each required check on that commit succeeded, every other check on it passed and the AI Executive states it is confident. Anything else goes to a person, a repository without branch rules included, and so does anything in a public repository or a change to CI or test configuration. A merge into a branch you deploy from can still publish or deploy live through your own pipeline; to keep every merge in a repository with a person, set it to “A person always decides”. The GitHub connection is not a developer API either.

What we may build later

  • Personal access tokens: let your own scripts and tools access your workspace data.
  • Outbound webhooks: receive events (with delivery status) so timer and project activity can reach your own tools.
  • Integrations: connections to tools like Slack, Google Calendar, Linear, Zapier and QuickBooks are on the roadmap, under Future.
Not available yet
None of these is built or scheduled, and there is no screen for managing an API. Please don’t build against the placeholder text.

Tell us what you need

Early feedback helps us decide what to build first. If you have an integration in mind, tell us about it at [email protected].

  1. 1Email us what you want to connect and how.
  2. 2Follow the roadmap for integration milestones.
  3. 3Check the changelog for new integrations.

For everything available today, see the product overview. Need help? Visit Help & support.