A Public API for Your Time Data

Your time data has only ever lived in one place: the app you tracked it in. Getting it anywhere else, into a finance spreadsheet, a dashboard, or whatever system your client insists on, meant exporting a CSV and hoping the columns had not moved since last month.

Quanta now has a public API. It is available on every paid plan, starting today.

What you can do with it

Read and write time. List entries with date filters, create them, edit them, delete them. Start and stop the timer, and ask what is currently running.

Pull reports. Grouped totals by client, project, user or task, and the individual entries behind them. The same filters you use in the app are all there: project, client, user, task, tag, billable, invoiced.

Read your workspace. Projects with their tasks, clients, and tags, so an integration can resolve names to records instead of you hard-coding ids.

The things people have asked for already: a weekly summary posted into Slack, hours pulled into a finance spreadsheet, a check that the numbers on a report match the ones about to go onto an invoice, and syncing entries into a client's own system.

Getting started

Create a key under Settings → API Keys, then send it as a header:

curl https://api.quanta.is/api/v1/time-entries \
  -H "X-Api-Key: qta_live_..."

That is the whole setup. Nothing to request, nobody to email.

The full reference, with every endpoint and its parameters, lives at api.quanta.is/docs.

A note on access

A key acts as the person who created it. It sees exactly what you see, changes exactly what you can change, and time logged through it is attributed to you, the same as if you had used the app.

That applies to reports too. If someone cannot open the summary report in Quanta, a key they created cannot pull it through the API either. Nobody gets more access through an integration than they had to begin with.

Keys are shown once, at creation. Revoke one from the same screen and anything using it stops working immediately.

What's next

The surface is deliberately narrow for a first release. Time entries are the only records you can create and change; projects, clients and tags are read-only. That covers tracking and reporting, which is where the value is today.

Write access to projects and clients is the obvious next step, and webhooks after that so integrations stop polling.

There is also an MCP server, which lets Claude start your timer, log your work, and tell you where the hours went without leaving the conversation. That gets its own post in a few days.

If you have a strong opinion about what should come first, we would like to hear it before we build it. Write to support@quanta.is.