Atendlly API and MCP server

Works with the ERP and the AI you already use. Atendlly exposes your account's contacts, conversations, CRM, knowledge and reports through two doors with one access model:

MCP server at https://atende.suporteja.com.br/mcp, for AI assistants: Claude, Claude Code, Cursor, VS Code and any MCP client. See MCP: connect your AI.
REST API v1 at https://atende.suporteja.com.br/v1, for ERPs, management systems and automations (n8n, Make, Zapier). See the reference and the ERP guide.

Available on the Pro and Business plans. The CRM (deals and tasks) is on Business.

First steps

An administrator opens Settings → Integrations → API keys and MCP and creates a key from a template ("AI assistant", "ERP", "Automation" or "Custom").
Copy the key right away: it starts with atl_live_ and will not be shown again.
Send it on every request as Authorization: Bearer atl_live_….

curl https://atende.suporteja.com.br/v1/me -H "Authorization: Bearer $ATENDLLY_API_KEY"

Good to know

The key is the account: there is no account_id in the paths.
Each key has permissions (scopes) per area; sending messages to customers is a separate permission that, by default, waits for a person's approval in Atendlly. See scopes.
Personal data (e-mail, phone, documents) is masked without the contacts:pii scope.
Errors follow RFC 9457 (application/problem+json). See errors.
Lists use cursors (next_cursor, has_more). See pagination.
Times are ISO 8601 UTC (2026-10-21T13:45:00Z).
The OpenAPI 3.1 document is at /v1/openapi.json.

Privacy (LGPD)

The data a key reads leaves Atendlly for the system or assistant you connect, which then processes your customers' personal data on behalf of your company (possibly outside Brazil). Connect only vendors your company has a legal basis and a contract with. Data already delivered to an external system cannot be erased by Atendlly.