We’re excited to introduce a long‑awaited improvement: you can now convert an existing Operator account directly into an API account. This enhancement has been one of the most frequently requested additions from customers, especially since the introduction of the new API account card.

Why this matters
Before this update, the only way to create an API account was through the newly introduced API account card in the Supporting Files module. However, many organizations already had Operator accounts that were originally set up solely for integrations or automated processes. These accounts couldn’t be conveniently converted under the new model... until now.
With this release, you can seamlessly transition those existing Operator accounts into proper API accounts, ensuring your environment stays clean, compliant, and easier to manage.
What are the benefits?
Switching an Operator to an API account comes with several advantages:
- API accounts are free and don’t consume an Operator license.
- No Person link required. API accounts are designed for system‑to‑system interactions, so linking them to a Person card is unnecessary.
- Cleaner user management. Converting legacy non‑human Operator accounts keeps your environment structured and avoids unnecessary overhead.
- Supports customers who previously used non‑standard setups. Some environments did not mark system accounts with the former API checkbox. With this new option, they can now bring those accounts into the new API account structure with ease.
Where to find it
You can access the conversion option directly from the Operator card:
More (⋯) → Convert to API account
The account will be instantly transformed into an API account card, automatically inheriting the correct configuration for authentication and licensing.
Part of the One TOPdesk User vision
This feature is a key step in our ongoing effort to create a clear distinction between human users and system accounts. By providing the ability to convert existing Operator accounts, we support customers in transitioning smoothly to the improved, future‑ready setup for API and system integrations.
