> ## Documentation Index > Fetch the complete documentation index at: https://docs.atako.ai/llms.txt > Use this file to discover all available pages before exploring further. # Ringover > Connect Ringover to your Atako agents — 13 read and 3 write actions. Let your agents read calls, users, groups, numbers, tags, presences and SMS conversations, search and manage contacts, and send SMS through the Ringover Public API. ## Connection * **Authentication**: API key. Ringover Dashboard → Developer → API Keys → Create an API key: pick the user the key acts as, give it a label, then set its permissions — Read on Calls, Users, Numbers and IVRs (call tags), Read+Write on Contacts and Conversations (SMS). Turn Monitoring on to reach the whole team (all calls, users, conversations, presences) instead of that user alone. Copy the key and paste it as-is. See [Ringover's documentation](https://developer.ringover.com/). ## Read actions (13) | Action | Description | | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `get_call` | Get one terminated call: every log entry (CDR) it produced, with numbers, user, duration, tags, notes and scenario. | | `get_contact` | Get one contact with all its data and phone numbers. | | `get_team` | Get the Ringover team: its numbers, users, IVRs, conferences, tags and groups. Without Monitoring on the key, only the key owner's own data is returned. | | `get_user` | Get one user: profile, assigned numbers, status and configuration. | | `list_calls` | List terminated calls of the whole team, most recent first. start\_date and end\_date go together and span at most 15 days (default: the last 15 days). Paginate with limit\_count (≤ 1000) and limit\_offset (≤ 9000), or last\_id\_returned beyond that. The same call\_id may appear several times (transfer, IVR). | | `list_contacts` | List or search the contacts of the key owner (own and shared). search matches first name, last name, company and phone numbers, sorted by relevance. limit\_count ≤ 500. | | `list_conversations` | List SMS/chat conversations (100 by default). Without Monitoring, only the key owner's conversations. Paginate with limit\_count (≤ 1000) and limit\_offset. | | `list_groups` | List the ring groups (call distribution groups) with their members and ring strategy. Without Monitoring, only the groups the key owner belongs to. | | `list_messages` | List the messages of one conversation (100 by default). Paginate with limit\_count (≤ 1000) and last\_id\_returned. | | `list_numbers` | List the phone numbers of the team with their assignment (user, IVR, conference, fax or available) and country. The filters only apply with Monitoring on; by default only available numbers are included — set is\_user etc. to true to include the others. | | `list_presences` | Get the current presence of every user of the team: available, on call, in snooze or offline, with the active snooze and connected device. Requires Monitoring on the key (401 otherwise). | | `list_tags` | List the call tags of the team (id, name, color, description). Needs IVRs Read. | | `list_users` | List the users of the team with their profile, numbers and status (needs Users Read; without Monitoring, only the key owner is returned). Total in list\_count. | ## Write actions (3) | Action | Description | | ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `create_contact` | Create one contact in the address book of the key owner. numbers is a list of \{ number (E.164), type: home\|office\|mobile\|fax\|other }; is\_shared makes it visible to the team. Posting twice creates a duplicate — list\_contacts with search first. | | `send_sms` | Send an SMS from one of the key owner's Ringover numbers (from\_number) to to\_number, both in E.164. scheduled\_at (UTC) defers it. Needs Conversations Write; sending from a colleague's number needs Monitoring and user\_id\_forced. The SMS really leaves — confirm the recipient and the text first. | | `update_contact` | Replace a contact: firstname, lastname, company and is\_shared are all required (send the current values for the fields you keep — get\_contact first). numbers, when given, REPLACES every existing number; omit it to keep them. | ## Permissions Every action above must be explicitly granted to an agent before it can be used. See [Permissions](/integrations/permissions) for the grant model and [Security](/integrations/security) for how credentials are protected. *** *Last reviewed against the provider API: September 2026.*