You moved your Notion workspace or transferred content to a different account, and now your integrations show the error “API Integration Token Invalid.” This happens because API tokens are tied to a specific workspace. When the workspace changes, the old token no longer works. This article explains why the token becomes invalid, how to generate a new one, and how to reconnect your integrations.
Key Takeaways: Fixing the Invalid API Token After a Workspace Move
- Integration settings > Internal Integration Token: Generate a new token in the new workspace to replace the old one.
- Notion API > Authorization header: Update your code or tool with the new token value.
- Notion > Connections: Remove and re-add the integration in the new workspace to restore access.
Why the API Token Becomes Invalid After a Workspace Move
Every Notion API integration token is generated for a specific workspace. The token contains an encrypted reference to that workspace’s ID. When you move pages or databases to a new workspace, the old token still points to the original workspace. The new workspace rejects the token because it does not match the expected workspace ID. Additionally, if you transfer ownership of pages, the integration must be reauthorized in the destination workspace. Notion does not automatically migrate integration permissions during a workspace transfer. You must manually create a new integration token in the target workspace and update every external tool or script that uses the API.
Steps to Generate a New Integration Token and Reconnect
- Create a new internal integration in the new workspace
Open the new Notion workspace in a browser. Go to Settings & Members > My connections > Develop or manage integrations. Click New integration. Give it a name and select the new workspace from the dropdown. Click Submit. Copy the generated Internal Integration Token shown on the next screen. - Add the integration to the target database or page
Open the page or database you moved to the new workspace. Click the three-dot menu in the top-right corner. Select Add connections. Find your integration in the list and click it. The page now grants permission to that integration. - Update your code or third-party tool with the new token
Locate where your original token is stored. This could be in a script, environment variable, or a tool like Zapier, Make, or Automate.io. Replace the old token string with the new one from step 1. - Test the connection
Run a simple API call, such as listing the pages in the database. If you use a tool, trigger a test action. Confirm that the response no longer shows the “API Integration Token Invalid” error. - Remove the old integration from the original workspace (optional)
In the original workspace, go to Settings & Members > My connections. Find the integration you created earlier and click Remove. This prevents confusion if you ever return to the old workspace.
If Notion Still Shows the Token Error After Reconnecting
Integration is not connected to the correct database
The integration token works only if the integration has been added to the specific page or database. A common mistake is generating a new token but forgetting to add the integration to the moved database. Open the database, click the three-dot menu, choose Add connections, and select your integration. If the integration is already listed, remove it and add it again to refresh the permission.
Token was copied incorrectly
The token string is case-sensitive and includes hyphens. A missing character or extra space causes the error. Go back to the integration settings page in the new workspace and copy the token again. Paste it directly into your code or tool without manual editing. If you store the token in an environment variable, verify there are no surrounding quotes or whitespace.
Third-party tool still uses cached credentials
Some services like Zapier or Make cache the connection details. Even after you update the token, the tool might still send the old one. In Zapier, disconnect the Notion app connection entirely and create a new one using the new token. In Make, delete the old Notion module and add a fresh one with the updated token. After reconnecting, run a test operation.
Old Workspace Token vs New Workspace Token: Key Differences
| Item | Old Workspace Token | New Workspace Token |
|---|---|---|
| Workspace ID | References original workspace | References target workspace |
| Integration name | May be reused but token is different | Must be generated fresh |
| Connected pages | Pages in old workspace only | Pages in new workspace only |
| Permission status | Integration not added to moved pages | Integration must be added manually |
| Validity after workspace move | Invalid for new workspace | Valid only for new workspace |
You now know why the API token becomes invalid after a workspace move and how to fix it. Generate a new token in the target workspace, add the integration to your moved pages, and update every external tool that uses the Notion API. As an advanced tip, store the token in a secure environment variable or a secrets manager so you can update it in one place instead of editing every script.