Atera API

Name: Atera API API
Brand: Atera API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring ObservabilityapiKey138 EndpointsREST

For Agents

Manage Atera agents, alerts, customers, contracts, tickets, and patches programmatically — the building blocks of an MSP back office.

Quickstart

Get started with Atera API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list open Atera alerts"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Atera API API.

List, retrieve, and remove monitored Atera agents (endpoints) across customers via /api/v3/agents

Raise and resolve infrastructure alerts using /api/v3/alerts and inspect alert detail by id

Read installed and available patches per agent through /api/v3/agents/{deviceGuid}/installed-patches and /available-patches

Find agents that belong to a specific machine name or customer for triage workflows

GET STARTED

Start building with Atera API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Atera API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Atera API, keeping it validated and agent-ready. Atera is an all-in-one remote monitoring and management platform built for managed service providers and internal IT teams, covering agents (endpoints), alerts, customers, contracts, tickets, billing, and patch management. The API exposes the full operational surface — registering and inspecting agents, raising and resolving alerts, managing customers and contracts, billing time entries, and orchestrating patches across managed devices. It is structured around long, paginated list endpoints under /api/v3 and is well suited to MSPs that need to lift Atera data into reporting, ticketing, or accounting systems.

Use Cases

Patterns agents use Atera API API for, with concrete tasks.

★ MSP Alert Triage Automation

Managed service providers run Atera as the central RMM and want alerts to flow into their ticketing tool with the right customer attribution. The Atera API's /api/v3/alerts and /api/v3/agents endpoints let a triage agent pull new alerts, resolve the affected agent and customer, and open a ticket in the MSP's helpdesk within seconds. This collapses the alert-to-ticket loop for high-volume MSP environments.

Poll GET /api/v3/alerts for new open alerts, fetch the parent agent via /api/v3/agents/{agentId}, and open a ticket in the MSP helpdesk

Patch Compliance Reporting

MSPs need patch compliance reports per customer for monthly client reviews. The /api/v3/agents/{deviceGuid}/installed-patches and /available-patches endpoints expose per-device patch state, so a reporting agent can roll up coverage per customer and surface devices missing critical patches. The output drives both client-facing reports and internal remediation backlogs.

For customer 4210, list each agent and call /api/v3/agents/{deviceGuid}/available-patches; flag devices with more than 5 outstanding critical patches

Agent Inventory Sync

Operations teams maintain a master inventory in a CMDB or asset register and need it to reflect Atera reality. The /api/v3/agents endpoints, including filters by customer and machine name, let a sync agent reconcile the CMDB with the live Atera agent list, removing decommissioned endpoints and adding new ones. The flow runs on a daily schedule against the Atera tenant.

List all agents for each customer, diff against the CMDB asset register, and create or remove records to match

Atera Operations via Jentic

Through Jentic, an AI agent fielding 'how many open alerts does customer X have?' searches by intent and Jentic returns the matching Atera operation with its parameters. The Atera api-key credential is held in the Jentic vault, so the agent never sees the raw key. This makes MSP operational questions answerable inside any LLM chat or runbook.

Use Jentic to search 'list open alerts for customer', load GET /api/v3/alerts, filter by customerId, and return the count by severity

Key Endpoints

138 endpoints — jentic publishes the only available openapi specification for atera api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/api/v3/account

Get tenant account info

GET

/api/v3/agents

List agents across customers

GET

/api/v3/agents/{agentId}

Get a specific agent

DELETE

/api/v3/agents/{agentId}

Delete a decommissioned agent

GET

/api/v3/agents/customer/{customerId}

List agents for a specific customer

GET

/api/v3/alerts

List alerts

POST

/api/v3/alerts

Create an alert

GET

/api/v3/agents/{deviceGuid}/installed-patches

Get installed patches for an agent

GET

/api/v3/account

Get tenant account info

GET

/api/v3/agents

List agents across customers

GET

/api/v3/agents/{agentId}

Get a specific agent

DELETE

/api/v3/agents/{agentId}

Delete a decommissioned agent

GET

/api/v3/agents/customer/{customerId}

List agents for a specific customer

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Atera api-key values are stored encrypted in the Jentic vault (MAXsystem). Jentic sets the auth header at call time, so the raw key never enters the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'list open Atera alerts for a customer') and Jentic returns the matching /api/v3/alerts or /api/v3/agents operation with its parameters, so the agent calls the right endpoint directly.

Time to first call

Direct integration: 1-2 days to map the 138 endpoints, set up auth, and handle pagination. Through Jentic: under an hour for the common alert-triage and patch-reporting flows.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

SyncroMSP

MSP platform combining RMM, PSA, and ticketing

Choose SyncroMSP when the MSP wants RMM and PSA integrated under one platform rather than RMM-led

Complementary

Freshdesk

Helpdesk platform commonly paired with Atera as the ticketing front end

Choose Freshdesk when the destination of an Atera alert should be a customer-facing helpdesk ticket

Alternative

New Relic

Full-stack observability platform with APM, logs, and infrastructure

Choose New Relic when the use case is application observability rather than MSP endpoint management

FAQs

Specific to using Atera API API through Jentic.

Why is there no official OpenAPI spec for Atera API?

Atera does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Atera API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Atera API use?

The Atera API uses an API key issued from the Atera admin console. Through Jentic, the key is held in the encrypted vault and the auth header is set at call time, so the agent never sees the raw key.

Can I list all agents for a specific customer?

Yes. GET /api/v3/agents/customer/{customerId} returns the agents linked to a single customer, paginated. This is the recommended path when scoping inventory or alert workflows to one tenant within an MSP.

What are the rate limits for the Atera API?

Atera throttles per API key with a published per-minute quota — back off on HTTP 429 responses and prefer paginated list reads (limit + page) over polling per agent or alert id.

How do I pull installed patches for a device through Jentic?

Search Jentic for 'get installed patches for an agent', load GET /api/v3/agents/{deviceGuid}/installed-patches, and execute with the device guid. Jentic injects the api-key header and validates the path parameter.

Can I create alerts through the Atera API?

Yes. POST /api/v3/alerts creates an alert against an agent. This is useful for piping alerts from a third-party monitor into Atera so the existing helpdesk workflow stays the single source of truth.

Is the Atera API limited to read operations?

No. Read endpoints dominate, but the API supports creating alerts, deleting agents, and other write operations across customers, contracts, and tickets — enough surface to drive day-to-day MSP automations.