Custom OAuth applications
Register your own OAuth application, get a client id and secret, and manage its access.
Last updated 15 August 2026
A custom OAuth application is how your own code gets access to the Temponia API. It has a client id and secret, and people connect it to their account through the standard OAuth consent screen, without ever giving your code their password.
Creating one
Only the company owner and admins can manage OAuth applications.
- Go to Integrations in Temponia.
- In the API access section, choose New API application.
- Give it a name. This is what people see on the authorization screen.
- Enter the redirect URI where users should land after authorising. It must
be HTTPS. For a script without a web server, use
urn:ietf:wg:oauth:2.0:oob. - Pick the access level: read only, or read and write.
After saving you land on the credentials page showing the client id and client secret, each with a copy button. You can return to this page at any time from the Integrations page.
Handling the secret
Treat the client secret like a password. It proves to Temponia that a token request really comes from your application, so keep it in your server's configuration or a secret manager, never in client-side code or a repository. If it leaks, delete the application and create a new one.
Changing and revoking access
Editing the application changes its name, redirect URI or access level. Narrowing the access level applies to new tokens; tokens that were already issued keep the scopes they were granted until they expire.
Deleting the application immediately invalidates every token issued through it. People can also revoke their own grant at any time, which stops your tokens working for just that person.
What your users see
When you send someone to the authorization URL, they sign in to Temponia if needed and see a consent screen naming your application and what it may do, for example "View your Temponia data" or "Edit time entries on your behalf". Nothing happens to their account until they approve. The tokens you receive act as that person, with exactly the access they approved. The full flow is described in Authenticating with the API.