To keep your scripts, integrations, and third-party tools connected to Atera, update every API request in two ways: replace the legacy API key with an API token, and send the request to https://api.atera.com. With an API token, the request uses the Authorization: Bearer {token} header instead of the X-API-KEY header. API requests used to go to https://app.atera.com.
Important: Legacy API keys stop working on January 26, 2027. Since November 10, 2026, the legacy API key page is no longer available in Atera and new legacy keys can't be created. Existing legacy keys keep working until January 26, 2027.
Make both changes in the same update, so you edit each script and integration once.
Notes:
- Only admins can create API tokens. If you're a technician without admin permissions, ask an admin on your account to create the token.
- Already using an API token? You don’t need a new one. Check the address your requests are sent to. If it’s https://app.atera.com, change it to https://api.atera.com and test each integration.
What This Migration Includes and Why
This article explains how to move your scripts, integrations, and third-party tools from a legacy API key to an API token. It covers what changes in your requests, the steps to follow, code examples, and how to fix common errors.
This migration includes two changes: replacing your legacy API key with an API token, and sending all API requests to https://api.atera.com.
Important: Only API requests are moving. https://app.atera.com remains the address for signing in to Atera in your browser.
Why we’re making these changes: to keep your account and your data more secure. With API tokens, you decide what each integration can do. Give each token only the permissions it needs, limit it to specific IP addresses, set an expiration date, and revoke it without affecting your other integrations. Moving API requests to a dedicated address, https://api.atera.com, also lets us apply stronger security protection to the Atera web app you sign in to.
Before You Migrate to an API Token
- Only admins can create API tokens. If you're a technician without admin permissions, ask an admin on your account to create the token.
- Make a list of every script, integration, and third-party tool that connects to Atera with your legacy API key. Atera can’t list these for you, because they run outside Atera. A good way to find them: if another tool shows information from Atera, such as tickets, devices, or alerts, it most likely uses the Atera API. Each one needs to be updated before January 26, 2027.
- Go through each item on your list and search its code or connection settings for “app.atera.com”. Every API request that uses it needs the new address, https://api.atera.com, including requests that already use an API token.
Tip: To find it quickly, press Ctrl+F (Cmd+F on a Mac) in each script or settings page and search for app.atera.com. In code editors such as Visual Studio Code, Ctrl+Shift+F (Cmd+Shift+F on a Mac) searches every file in a folder at once. - Third-party tools usually set the Atera API address themselves, so you may not see it, or be able to change it, in their settings. If a tool still sends requests to https://app.atera.com, the vendor needs to update it. Contact the vendor to check.
- Already using an API token? You don't need a new one. Check the address your requests are sent to. If it's https://app.atera.com, change it to https://api.atera.com and test the integration.
What Changes Between a Legacy API Key and an API Token
An API token goes in the Authorization header as Authorization: Bearer {token}, instead of the X-API-KEY header used by the legacy API key, and requests go to https://api.atera.com. You can create multiple tokens, and we recommend one per integration so you can revoke one without affecting the others. Each token has full access, or custom Read, Write, and Delete permissions per domain. Each token expires up to one year from creation, and can allow all IP addresses or only specific ones.
Important: A token is shown only once, when you create it, so copy and store it before you close the panel. You can't edit a token after you create it. To change anything about it, revoke it and create a new one.
| Item | Legacy API key | API token |
|---|---|---|
| Request header | X-API-KEY: {key} | Authorization: Bearer {token} |
| Base URL | https://app.atera.com | https://api.atera.com |
| Number of credentials | One key per account | Multiple tokens. We recommend one per integration, so you can revoke one without affecting the others |
| Permissions | Full access | Full access, or custom Read, Write, and Delete permissions per domain |
| Expiration | Stops working on January 26, 2027 | Up to one year from creation. Admins get a notification 7 days and 1 day before a token expires. Plan to replace the token before then. |
| IP restriction | None | Allow all, or specific IP addresses |
| Viewing the credential | Not available. The legacy API key page was removed on November 10, 2026 | Shown once, when created. Copy and store it before you close the panel |
| Editing after creation | Not applicable | Not possible. Revoke the token and create a new one |
Migrate to an API Token Step by Step
-
Create an API token. Go to Admin > Data management > API and click New token. Create a separate token for each script, integration, and third-party tool, so you can revoke one without affecting the others. Name each token after the tool that uses it, so you can tell them apart later. Enter a name, an expiration date, the allowed IP addresses, and the API permissions. For the full steps, see Create an API token.
- Choose the permissions the integration needs. A token can only call the domains it has permission for. For example, a script that reads devices needs Read permission for Agents. You can't edit a token after you create it. To change its permissions, revoke it and create a new token.
-
Copy and store the token. It's shown only once.
- Replace the header in every request. Remove the X-API-KEY header and add Authorization: Bearer {token}. For examples in curl, PowerShell, and Python, see Update the Request Header and API Address in Your Code.
- Update the base URL and endpoints. In every request, replace https://app.atera.com with https://api.atera.com.
- Test each integration. Run a read request first and confirm a successful response before you run requests that create, change, or delete data.
- Note the expiration date. Admins get a notification 7 days and 1 day before a token expires.
Update the Request Header and API Address in Your Code
Each example changes two things: the header and the API address. Replace the X-API-KEY header with Authorization: Bearer {token}, and replace https://app.atera.com with https://api.atera.com.
Note: Don't hard-code tokens in shared scripts or public-facing applications, and don't send them by email. Store them in a secrets manager or an environment variable.
curl Example: Legacy API Key to API Token
Before:
curl -H "X-API-KEY: YOUR_LEGACY_KEY" "https://app.atera.com/api/v3/agents"
After:
curl -H "Authorization: Bearer YOUR_API_TOKEN" "https://api.atera.com/api/v3/agents"
PowerShell Example: Legacy API Key to API Token
Before:
$headers = @{ "X-API-KEY" = "YOUR_LEGACY_KEY" }
Invoke-RestMethod -Uri "https://app.atera.com/api/v3/agents" -Headers $headersAfter:
$headers = @{ "Authorization" = "Bearer YOUR_API_TOKEN" }
Invoke-RestMethod -Uri "https://api.atera.com/api/v3/agents" -Headers $headersPython Example: Legacy API Key to API Token
Before:
import requests
headers = {"X-API-KEY": "YOUR_LEGACY_KEY"}
response = requests.get("https://app.atera.com/api/v3/agents", headers=headers)After:
import requests
headers = {"Authorization": "Bearer YOUR_API_TOKEN"}
response = requests.get("https://api.atera.com/api/v3/agents", headers=headers)Postman Example: API Token and the New API Address
To send a request to the Atera API from Postman with an API token:
- Select the HTTP method, such as GET, POST, PUT, or DELETE.
- Set the request URL to https://api.atera.com followed by the endpoint path, in place of https://app.atera.com.
- Add an Authorization header with the value Bearer {token}, using your API token.
Troubleshoot API Errors After Migrating to an API Token
| What you see | Likely cause | What to do |
|---|---|---|
| 401 Unauthorized | The token is missing, expired, or pasted wrongly | Send the token as Authorization: Bearer {token} and check its expiration date under Admin > Data management > API |
| 403 | The token doesn't have permission for the domain, or the request came from an IP address that isn't allowed | Check the token's permissions and allowed IP addresses. A token can't be edited, so if it needs different permissions or IP addresses, revoke it and create a new one |
| 404 Not Found | The request is to an unknown resource | Verify that the resource is found in the API documentation |
| 429 Too Many Requests | You've exceeded your account's rate limit | Wait the number of seconds in the Retry-After header before retrying |