# Atera

> Atera Networks Ltd. operates an all-in-one IT management platform for managed service
> providers and internal IT departments: remote monitoring and management (RMM),
> professional services automation (PSA), helpdesk and ticketing, patch management,
> network discovery, remote access, reporting and billing, with an AI layer (Action AI,
> AI Copilot, and Robin, the IT Autopilot). Atera exposes a versioned REST API at
> https://app.atera.com/api/v3 covering twelve data domains, authenticated with an
> account token in the X-API-KEY header, plus outbound webhooks bound to ticket
> automation rules.

Generated by the API Evangelist enrichment pipeline on 2026-08-06. Atera does not
publish an llms.txt of its own; /llms.txt returns 404 on app.atera.com and 403 on
www.atera.com.

## What an agent needs to know first

- The API contract is NOT publicly readable. Atera states it uses OpenAPI 3.0, but the
  interactive reference at https://app.atera.com/apidocs returns HTTP 401 with an empty
  body to any unauthenticated client, and no specification is served at a public URL.
- Authentication is a single account token in the `X-API-KEY` request header. There is
  no OAuth, no OIDC and no scope strings; permissions are set per data domain
  (Read/Write/Delete) when the token is created.
- API access is disabled during the free trial and included in every paid subscription.
- All requests must use HTTPS.
- 4xx responses observed on the live API carry an empty body — a missing key and an
  invalid key are indistinguishable to the caller.
- There is no idempotency key, no documented rate limit, no 429 contract and no
  rate-limit response headers.
- There is no sandbox. Every call runs against production tenant data.
- Atera support explicitly does not troubleshoot API integrations.

## APIs

- [Atera API v3](https://app.atera.com/apidocs): REST API over twelve data domains —
  Agents, Alerts, Billing, Contacts, Contracts, Customers, CustomValues, Departments,
  Devices, KnowledgeBase, Rates, Tickets. Base URL https://app.atera.com/api/v3.

## Documented endpoints (from Atera's own support articles)

- `GET /api/v3/agents` — list agents
- `GET /api/v3/agents/machine/{machineName}` — agents for a specified machine
- `GET /api/v3/devices` — list monitored devices
- `GET /api/v3/tickets` — list tickets
- `GET /api/v3/contacts` — list contacts
- `GET /api/v3/alerts` — list alerts
- `POST /api/v3/alerts` — create an alert
- `DELETE /api/v3/agents/{agentId}` — delete a specified agent
- CustomValues endpoints — read/write tenant custom fields

Note: this list is what Atera shows in public support articles and sample scripts. It is
not the complete operation set; the full reference is behind the tenant login.

## Docs

- [Using the Atera API](https://support.atera.com/hc/en-us/articles/219083397-Using-the-Atera-API)
- [API FAQ](https://support.atera.com/hc/en-us/articles/11071761826844-API-FAQ)
- [Webhooks](https://support.atera.com/hc/en-us/articles/13688068743964-Webhooks)
- [Atera Data Export FAQ](https://support.atera.com/hc/en-us/articles/23356740871836-Atera-Data-Export-FAQ)
- [AI Center: MCP integrations](https://support.atera.com/hc/en-us/articles/24164010860700-AI-Center-Model-Context-Protocol-MCP-integrations)
- [Getting started](https://support.atera.com/hc/en-us/articles/360019612194-Getting-started)
- [Release Notes](https://support.atera.com/hc/en-us/sections/201896227-Release-Notes)
- [Help Center](https://support.atera.com/hc/en-us)
- [Community](https://community.atera.com/)
- [Status](https://status.atera.com)
- [Trust Center](https://trust.atera.com/)

## Events

- Webhooks fire on three ticket triggers only: new ticket created, ticket
  closed/resolved, ticket status changed. They must be attached to a ticket automation
  rule as a "Trigger webhook" action. Enterprise / Superpower tiers only. No payload
  schema, signature scheme or AsyncAPI document is published.

## Agent surfaces

- MCP: Atera is an MCP **host**, not an MCP server publisher. Its AI Center installs MCP
  integrations from a catalog and accepts custom MCP server registrations so Robin and
  AI Copilot can reach outside systems. Atera publishes no MCP server for third parties
  to call.
- A2A: no agent card at /.well-known/agent-card.json or /.well-known/agent.json.
- No /.well-known/ documents of any kind were reachable on any Atera host.

## Client libraries

Atera publishes no first-party SDKs. Its own documentation points readers at the
community PowerShell module PSAtera (https://www.powershellgallery.com/packages/PSAtera),
which Atera does not maintain.

## Profile

- [API Evangelist profile](https://github.com/api-evangelist/atera)
- [apis.yml](https://raw.githubusercontent.com/api-evangelist/atera/refs/heads/main/apis.yml)