Change date: Tuesday 18 August 2026
Time: 23:00 CEST (21:00 UTC)
On Tuesday 18 August 2026 at 23:00 CEST, we will switch primaTime to a new sign-in system.
If you use primaTime in the browser, nothing changes for your day-to-day work. You will keep signing in with your email and password as usual.
The change mainly affects integrations that use the primaTime API. If you use the API, please check your integration and update it before the switch.
ℹ️ This change only applies to primaTime 2.0. The legacy version of primaTime is not affected.
Technical documentation is here:
1. 💡 Why we are making this change
We are moving sign-in to a dedicated identity management platform. This makes it safer, clearer, and better prepared for new types of integrations.
What you get:
🔒 Safer sign-in and better protection for company data
🍏 Apple sign-in
📱 Two-factor authentication for better account security
🔑 API keys that you can revoke at any time
🤖 Preparation for official MCP integrations with tools such as ChatGPT, Claude, and Gemini
2. 🎯 Who is affected
From 18 August 2026 at 23:00 CEST, older API integrations will stop working if they:
sign in through the API with an email and password,
call
requestAccessToken,send the
X-Tenant-IDheader,store and reuse access tokens from the current system.
⚠️ There will be no transition period after the switch.
Old access tokens will stop working after the change, even if they have not expired yet.
3. 🛠️ What you need to do
Choose the new access method based on how your integration works.
🔑 API key
An API key is best for scripts, scheduled jobs, internal automations, and server integrations.
How it works:
You can generate the key in your primaTime profile
Send it in each API request using the
X-Api-KeyheaderAPI keys do not expire automatically — they remain valid until you revoke them
🔐 OAuth 2.0
Use OAuth 2.0 for applications where users should sign in with their own primaTime account.
How it works:
This flow uses PKCE
It lets the app sign users in safely without handling their primaTime password
4. ⏰ Timeline
Date: Tuesday 18 August 2026
Time: 23:00 CEST
UTC: 21:00 UTC
Impact: old API sign-in stops working immediately
5. ✅ Checklist for API integrations
Before 18 August 2026:
☐ Review integrations connected to the primaTime API
☐ Check whether they use email and password,
requestAccessToken, orX-Tenant-ID☐ Switch them to an API key or OAuth 2.0
☐ Test them before the change
☐ Revoke access credentials you no longer need
💬 Need help?
If you need help with the migration, contact primaTime support or reply to the announcement email.