Skip to main content

​
Overview

The Atera integration enables ThreatAware to collect read-only data from your Atera platform, providing visibility into managed devices, security configurations, and customer information.
Connection Method: API Setup Time: 10 minutes Access Required: Atera Administrator account

​
Data collected

The Atera integration provides:
  • Managed device inventory
  • Device security status
  • Customer account information
  • Integration metadata

​
Use cases

Device Inventory

Monitor all devices managed through Atera

Security Status

Track security configurations across managed systems

Account Visibility

Understand customer distribution and device allocation

Compliance Tracking

Generate reports on managed device coverage

​
Setup instructions

1

Log in to Atera Dashboard

Access your Atera dashboard with an administrator account that has permissions to generate API keys.
2

Generate API Key

Navigate to Admin > API in the settings.
  • Click Generate API Key and copy the key displayed.
  • Store this key securely for use in ThreatAware.
Note: Ensure your account has administrator privileges to generate API keys.
3

Retrieve Customer ID

Open the Atera API Documentation.
  • Under the Customer section, locate the GET /api/v3/customers endpoint.
  • Use this endpoint to retrieve customer information.
  • Copy the Customer ID for the account you are integrating.
4

Configure in ThreatAware

Complete the integration setup in ThreatAware:
  • Navigate to Settings > Integrations
  • Search for and select Atera
  • Enter the required credentials:
    • API Key: The API key generated in Atera
    • Customer ID: The customer ID retrieved from the API
  • Click Connect to establish the integration
5

Verify Connection

After connecting, verify the integration is working:
  • Check that the Integration Status shows as Active
  • Confirm that device data is appearing in ThreatAware

​
Required credentials

Field Name: Atera API Key Type: Password (encrypted) Description: The API key generated in Atera’s API settings
Keep this credential secure. The API key allows access to customer data in Atera.
Field Name: Atera Customer ID Type: String Description: The unique identifier for your customer account in AteraThis ID is retrieved using the Atera API GET request for customers.

​
Verification and testing

After setup, verify the integration is working correctly:
  1. Check Integration Status
    • Navigate to Settings > Integrations in ThreatAware
    • Confirm the Atera integration shows Active status
    • Check the last sync timestamp
  2. Verify Data Collection
    • Wait 5-10 minutes for the initial data sync
    • Search for a known device in ThreatAware
    • Confirm Atera device data is visible
  3. Test Queries
    • Create a test query to filter devices from Atera
    • Verify the data matches your expectations

​
Troubleshooting

Symptoms: Integration status shows authentication failureSolutions:
  • Verify the API Key is exactly as displayed in Atera (no extra spaces)
  • Ensure the API key has not expired
  • Regenerate a new API key in Atera if the current one is suspect
  • Confirm your Atera account has administrator privileges
Symptoms: Integration connects but fails to retrieve dataSolutions:
  • Verify the Customer ID is correct using the Atera API
  • Ensure the customer account is active in Atera
  • Check that the API key has access to the specified customer
  • Review the Atera API Documentation for customer endpoint details
Symptoms: Integration fails to connect or times outSolutions:
  • Verify your Atera account is accessible and online
  • Check firewall rules allow outbound HTTPS (443) to Atera
  • Test the Atera dashboard URL in a browser to ensure connectivity
  • Contact Atera support if their platform is experiencing issues
Symptoms: Integration shows active but no device data appearsSolutions:
  • Verify you have devices managed in Atera under your customer account
  • Confirm the API key has read permissions to device data
  • Wait up to 15 minutes for the initial sync to complete
  • Check that the Customer ID corresponds to an active customer with managed devices

​
Additional resources

Atera API Documentation

Official Atera API documentation for detailed permissions and configuration

ThreatAware Support

Contact ThreatAware support for integration assistance

​
Best practices

Credential Management
  • Store your API key securely in your organisation’s password manager
  • Rotate API keys annually or per your security policy
  • Monitor integration logs in ThreatAware for authentication failures
  • Document the Customer ID for future reference
Security Considerations
  • API keys provide access to your Atera account data
  • Only share API keys with authorised personnel
  • Review your Atera API activity logs periodically
  • Regenerate API keys if they are exposed or compromised