Temponia API overview
What the JSON API can do, where it lives, and how to get access to it.
Last updated 15 August 2026
Temponia has a JSON API. Everything the mobile apps do goes through it, and you can use it too: log time from your own scripts, pull entries into a data warehouse, or wire Temponia into a tool we do not integrate with yet.
Where it lives
The API is served under /api/v1 on your workspace domain:
https://yourworkspace.temponia.com/api/v1
https://app.temponia.com/api/v1 works as well. The token you send decides
which account the request acts on, not the domain.
Requests and responses are JSON. Every request needs a bearer token in the
Authorization header; see Authenticating with the API.
What you can do
| Resource | Operations |
|---|---|
| Time entries | List, fetch, create, update, delete |
| Expenses | List, create, update, delete |
| Projects, clients, tasks, task links, assignments | List |
| Expense types | List |
| Company | Fetch |
Tokens act on behalf of the person who authorised them. Time entries and expenses are that person's own, and projects and clients are the ones they can see inside Temponia.
Getting access
Create a custom OAuth application from Integrations in Temponia. You get a client id and secret, and users grant your app access through the standard OAuth 2.0 authorization code flow.
Machine-readable description
The full API is described in an OpenAPI 3 document at /docs/api/openapi.yaml. You can browse it, and try requests with your own token, in the API explorer.