All Collections
awork switches to .com
awork switches to .com

The switch to .com requires a few changes to be done by workspace admins and integration developers.

Max Raschke avatar
Written by Max Raschke
Updated over a week ago

In early September awork is switching the website, web app and emails from to .

☝️Hint: All existing links that use continued to work until mid-February 2024, thanks to automatic redirects. Since mid-February 2024, the redirect from to has been discontinued, see below.

There are, however, two changes that need to be done by workspace admins and integration developers:

These changes can be done immediately from now on and need to be done until October 15, 2023/December 31, 2023.

Single-Sign-On (SSO) users need to add "" to the allowed redirect URLs

🚨 Due date for this change: October 15, 2023

In order for SSO to continue working, admins will have to update the redirect URLs of their SSO provider. During the login flow, users will be redirected back to awork. For security reasons, this is only allowed for a list of configured URLs.

πŸ‘‰ Please add the variants while keeping the URLs in place for now.

Depending on the provider and other integrations used, there can multiple URLs that are required. For more details and provider-specific configuration, please refer to the SSO Help Center article.

In most cases, the following URL has to be added to the allowed redirect URLs:

If the provider offers a field for an Application Login URL or similar, please also update this to use instead of .

Please make this change by October 15, 2023. After that, awork will redirect back to and the login flow will fail if this has not been allowed.

Integration developers need to switch to ""

🚨 Due date for this change: December 31, 2023

While the awork API is currently available at both and , from January 2024 onwards, this will no longer be the case, where we will only provide the API at .

πŸ‘‰ Integration developers therefore need to update the awork API base URL to:

For more details about the awork API, please refer to the Developer Docs.

If you are using awork's OAuth 2.0 flow to authenticate your users, no further steps are required. If you, however, are using an admin token that was generated in awork's Integrations page, you will need to generate a new token. Please refer to the Client Applications and API Keys article in the Help Center.

And, of course if you need any help, please contact our support anytime. πŸ’œ

Redirection from .io to .com discontinued

Since mid-February 2024, existing links that use are no longer redirected.

Please make sure that you call up your awork workspace with your URL and .com at the end. It depends on the .com. If you still have old bookmarks with the domain, please change them accordingly.

☝️Hint: In the course of the domain change, the endings of the project email addresses, which are used to create tasks via email, have also changed. You should update the vCards accordingly. Nevertheless, e-mails that are still sent to the old project e-mail address (.io) will still arrive successfully as tasks in the corresponding project.

Did this answer your question?