Ringover integration
Ringover is a cloud phone system for teams. Read the team, its users, groups, phone numbers, IVRs and scenarios, conference rooms, tags, profiles and presences; list and search terminated and live calls, archive calls, control a live call (hang up, hold, mute, record, transfer, DTMF) and start a callback; read call transcriptions and Empower AI analyses (summaries, key moments, flags) and chat with Empower about a call; manage contacts, team and user blacklists, user plannings and snooze; send SMS and WhatsApp messages and templates and work with conversations; run outbound call campaigns (queue, users, groups, tags, script, start and stop); and manage tasks and webhooks. SCIM provisioning, the MCP endpoint, the deprecated user creation route, binary downloads (call recordings, the CDN download proxy, the Empower analytics export, external call upload), campaign custom-column management and subscription plan data are not exposed. Authentication is a Ringover API key created in the Developer section of the Ringover Dashboard, sent as is (no prefix) in the Authorization header; pick the region of your account: public-api (Europe) or public-api-us (United States). The rights of each key are selected in the Dashboard, and a route refuses a key that lacks its right.
Say what should happen.
The workflow builds itself.
What you can do with Ringover
Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.
Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.
Blacklisted number, 8 operations
add_team_blacklisted_numberAdd team blacklisted numberPOSTAdds a phone number to your team's shared blacklist. Once added, calls from this number are blocked for **all users** in the team.add_user_blacklisted_numberAdd user blacklisted numberPOSTAdds a phone number to a user's personal blacklist. Once blacklisted, calls from this number to the user are blocked.get_team_blacklisted_numberGet team blacklisted numberGETChecks whether a specific phone number is present in your team's shared blacklist.get_user_blacklisted_numberGet user blacklisted numberGETChecks whether a specific phone number is present in a user's personal blacklist.list_team_blacklisted_numbersList team blacklisted numbersGETRetrieves the phone numbers on your team's shared blacklist. The team blacklist applies to all users, calls from blacklisted numbers are blocked for the entire team.list_user_blacklisted_numbersList user blacklisted numbersGETRetrieves the phone numbers blacklisted by a specific user. A user's personal blacklist contains numbers that are blocked from calling or being called by this user specifically.remove_team_blacklisted_numberRemove team blacklisted numberDELETERemoves a phone number from your team's shared blacklist, allowing calls from this number to reach all team members again.remove_user_blacklisted_numberRemove user blacklisted numberDELETERemoves a phone number from a user's personal blacklist, allowing calls from this number to reach the user again.
Call, 7 operations
archive_callArchive callDELETEArchive a terminated call by its call ID. Archived calls are removed from the default call listing results but remain in the system.get_callGet callGETRetrieve detailed data about a specific terminated call by its ID.hang_up_callHang up callPOSTTerminates (hangs up) a live call on the specified channel. The call is immediately disconnected for the participant identified by this channel.list_callsList callsGETRetrieve a paginated list of terminated calls for your team, ordered by most recent first.list_current_callsList current callsPOSTRetrieve the currently active (in-progress) calls. This endpoint uses POST to accept optional filter criteria in the request body.search_callsSearch callsPOSTRetrieve a paginated list of terminated calls with advanced filtering capabilities.send_call_dtmfSend call dtmfPOSTSends DTMF (Dual-Tone Multi-Frequency) tones on the specified live call channel. DTMF tones are the signals produced by phone keypads (digits 0-9, *, #).
Campaign, 5 operations
get_campaignGet campaignGETRetrieves detailed information about a specific outbound call campaign, including its full configuration (name, max retry, start date, script), assigned users and groups.list_campaignsList campaignsGETRetrieves a paginated list of all outbound call campaigns configured for your team.list_my_active_campaignsList my active campaignsGETRetrieves campaigns that are currently running and assigned to the authenticated user (the API key owner).rename_campaignRename campaignPATCHUpdates the display name of a specific campaign. The new name is provided directly in the URL path as `newname`.reset_campaignReset campaignPOSTResets a campaign to its initial state, all contact call statuses are cleared, retry counts are set back to zero, and call statistics are erased.
Conversation, 5 operations
archive_conversationArchive conversationPOSTPerforms a **level-1 (soft) archive** on a conversation. This is a reversible operation, the conversation can be restored with `unarchive_conversation`.archive_conversation_permanentlyArchive conversation permanentlyDELETEPerforms a **level-2 (permanent) archive** on a conversation. This operation is **irreversible** and requires Monitoring to be enabled on your API key.get_conversationGet conversationGETRetrieves information about a specific conversation. Only the last message is included; use the messages endpoint to retrieve the full message history.list_conversationsList conversationsGETReturns the first 100 available conversations by default. Use `limit_offset` and `limit_count` to paginate: the first X conversations are skipped and the following Y are returned.rename_conversationRename conversationPOSTUpdates the display name of a specific conversation. The new name is passed directly in the URL path. **Permission:** `Conversations Write` required. **Monitoring:** No impact.
Contact, 4 operations
delete_contactDelete contactDELETEPermanently deletes a contact by their ID. **Permission:** `Contacts Write` required. **Monitoring:** No impact.get_contactGet contactGETRetrieves all data and phone numbers for a specific contact by their identifier. **Permission:** `Contacts Read` required. **Monitoring:** No impact.list_contactsList contactsGETRetrieves your list of contacts (yours and those shared with you). The maximum number of rows returned is set by the parameter limit_count (limited to 500 rows).search_or_create_contactsSearch or create contactsPOSTSearches or creates contacts: send search filters (search, limit_count, limit_offset) for yours and shared ones (by relevance with search, at most 500 per page), or contacts to create (at most 50, assigned to the API key's user). Never both.
Empower call, 4 operations
delete_empower_callsDelete empower callsDELETEDeletes Empower-analyzed calls entirely, or removes only their media (audio/video) while keeping call records. **Permission:** `Empower Write` required. **Monitoring:** No impact.get_empower_callGet empower callGETRetrieves the full details of an Empower-analyzed call by its UUID, including transcription, scores, and metadata. **Permission:** `Empower Read` required.list_empower_callsList empower callsGETRetrieves a list of calls analyzed by Empower, with optional filters (date range, direction, language, mood, etc.). **Permission:** `Empower Read` required.list_empower_call_summariesList empower call summariesPOSTRetrieves call summaries for a specified user within a given date range, including recap, moments, transcription, and scores. **Permission:** `Empower Read` required.
Scenario, 4 operations
get_ivr_scenarioGet ivr scenarioGETRetrieves detailed information about a specific scenario within an IVR.get_scenarioGet scenarioGETRetrieves a specific scenario by its unique ID, regardless of which IVR it belongs to.list_ivr_scenariosList ivr scenariosGETRetrieves all scenarios (call flow variants) attached to a specific IVR.list_scenariosList scenariosGETRetrieves all scenarios across all IVRs in a single request. This is a convenience alternative to calling `list_ivr_scenarios` for each IVR individually.
User, 4 operations
delete_userDelete userDELETEPermanently deletes or archives a user by their unique identifier. The `type` query parameter controls whether the user is fully deleted (`DELETED`) or archived (`ARCHIVED`).get_userGet userGETRetrieves detailed information about a specific user, including their profile, assigned phone numbers, status (active, archived), and configuration.invite_usersInvite usersPOSTInvites one or more users to the team and creates all associated resources (user accounts, phone numbers, voicemail, etc.). Each invited user receives an activation email.list_usersList usersGETRetrieves users from your team. Each user object includes the user's profile information, assigned phone numbers, status, and configuration.
Webhook, 4 operations
create_webhookCreate webhookPOSTSubscribes a `target_url` to one or more events. Ringover will `POST` the payload of each subscribed event to that URL.delete_webhookDelete webhookDELETEDeletes a webhook subscription. Its target URL is unsubscribed from **every** event and stops receiving deliveries. The other subscriptions of your configuration are untouched.get_webhookGet webhookGETRetrieves a single webhook subscription: its target URL and the events currently delivered to it. Use `list_webhooks` to discover the identifiers of your webhooks.list_webhooksList webhooksGETRetrieves every webhook subscription of your configuration: the target URLs Ringover delivers events to, and the events each one is subscribed to.
Whatsapp template, 4 operations
create_whatsapp_templateCreate whatsapp templatePOSTCreates a WhatsApp message template and returns the template UUID. The template name must not contain upper-case letters or special characters.delete_whatsapp_templateDelete whatsapp templateDELETEDeletes a WhatsApp message template by its UUID. **Permission:** Access is managed by the WhatsApp service. No specific API token permission is checked. **Monitoring:** No impact.list_whatsapp_templatesList whatsapp templatesGETRetrieves all WhatsApp message templates associated with the specified account. **Permission:** Access is managed by the WhatsApp service.send_whatsapp_templateSend whatsapp templatePOSTSends a WhatsApp template message to a specified external number.
Campaign group, 3 operations
add_campaign_groupsAdd campaign groupsPOSTAssigns one or more call groups to a campaign. All users belonging to these groups will be eligible to receive campaign calls when the campaign is running.list_campaign_groupsList campaign groupsGETRetrieves the list of call groups assigned to a specific campaign. When a campaign is running, contacts in the queue are distributed to agents who belong to these groups.remove_campaign_groupsRemove campaign groupsDELETERemoves one or more call groups from a campaign. The group IDs to remove are provided as a query parameter array (`to_groups`).
Campaign number, 3 operations
add_campaign_numbersAdd campaign numbersPOSTAdds one or more phone numbers (contacts) to a campaign's call queue.list_campaign_numbersList campaign numbersGETRetrieves the paginated list of phone numbers (contacts) in a campaign's call queue.remove_campaign_numbersRemove campaign numbersDELETERemoves one or more phone numbers from a campaign's call queue. The numbers to remove are specified as a query parameter array (`to_numbers`).
Campaign tag, 3 operations
remove_all_campaign_tagsRemove all campaign tagsDELETERemoves all tags currently associated with a campaign. After this operation, the campaign will have no tags. Returns `304` if the campaign already had no tags.remove_campaign_tagRemove campaign tagDELETERemoves a single tag from a campaign by its tag ID, while leaving all other tags in place.replace_campaign_tagsReplace campaign tagsPUTReplaces the entire set of tags associated with a campaign. The request body must contain a `tags` array of tag IDs (integers).
Campaign user, 3 operations
add_campaign_usersAdd campaign usersPOSTAssigns one or more individual users to a campaign. These users will be eligible to receive campaign calls when the campaign is running.list_campaign_usersList campaign usersGETRetrieves the list of individual users directly assigned to a specific campaign (in addition to users assigned via groups).remove_campaign_usersRemove campaign usersDELETERemoves one or more individual users from a campaign. The user IDs to remove are provided as a query parameter array (`to_Users`).
Contact number, 3 operations
add_contact_numbersAdd contact numbersPOSTAdds one or more phone numbers to the specified contact. Phone numbers must be in international (E.164) format. **Permission:** `Contacts Write` required.delete_all_contact_numbersDelete all contact numbersDELETEPermanently deletes all phone numbers associated with the specified contact. **Permission:** `Contacts Write` required. **Monitoring:** No impact.delete_contact_numberDelete contact numberDELETEPermanently deletes a specific phone number from the specified contact. **Permission:** `Contacts Write` required. **Monitoring:** No impact.
Empower flag, 3 operations
add_empower_call_flagAdd empower call flagPOSTAssociates an existing flag with a specific call. Use this to tag or categorize calls for review. **Permission:** `Empower Write` required. **Monitoring:** No impact.list_empower_flagsList empower flagsGETRetrieves all flags configured for your team. Flags are labels that can be associated with calls for categorization and tracking. **Permission:** `Empower Read` required.remove_empower_call_flagRemove empower call flagDELETERemoves the association between a flag and a call. **Permission:** `Empower Write` required. **Monitoring:** No impact.
Number, 3 operations
assign_numberAssign numberPATCHReassign a phone number to a different target: a user, an IVR, or a conference room.get_numberGet numberGETRetrieves detailed information about a specific phone number, including its assignment (user, IVR, conference), country, capabilities, and configuration.list_numbersList numbersGETRetrieves the list of phone numbers provisioned for your team. Each number includes its assignment (user, IVR, conference, fax, or unassigned), country, and configuration.
Planning, 3 operations
get_user_planningGet user planningGETRetrieves a user's weekly availability planning, the time slots during which the user is reachable via Ringover.replace_user_planningReplace user planningPUTReplaces a user's entire weekly availability planning with a new one. The request body must contain an array of time ranges for each day of the week (Monday through Sunday).replace_user_planning_dayReplace user planning dayPUTReplaces a user's availability planning for a single day of the week.
Tag, 3 operations
create_tagCreate tagPOSTCreates a new tag for your team. Tags are team-wide labels used to categorize calls.get_tagGet tagGETRetrieves detailed information about a specific call tag by its identifier, including its name, color, description, and creation metadata.list_tagsList tagsGETRetrieves all tags defined for your team. Tags are labels that can be attached to calls for categorization and reporting purposes (e.g., "support", "sales", "follow-up").
Callback, 2 operations
create_callbackCreate callbackPOSTInitiates a callback: your user receives an incoming call and, once they pick up, the system automatically dials the recipient. Caution: this feature adds call redirection fees.create_ivr_callbackCreate ivr callbackPOSTTriggers a callback through a specific IVR (Interactive Voice Response) queue.
Conference, 2 operations
get_conferenceGet conferenceGETRetrieves detailed information about a specific conference room by its identifier, including its assigned phone number, participant PIN code, admin PIN code, name.list_conferencesList conferencesGETRetrieves all conference rooms (audio bridges) configured for your team.
Conversation message, 2 operations
archive_conversation_messageArchive conversation messagePOSTPerforms a **level-1 (soft) archive** on a specific message within a conversation. This is a reversible operation, the message can be restored with `unarchive_conversation_message`.archive_conversation_message_permanentlyArchive conversation message permanentlyDELETEPerforms a **level-2 (permanent) archive** on a specific message within a conversation. This operation is **irreversible** and requires Monitoring to be enabled on your API key.
Group, 2 operations
get_groupGet groupGETRetrieves detailed information about a specific call group, including its members, ring strategy, ring durations, and IVR assignments.list_groupsList groupsGETRetrieves call groups (ring groups) configured for your team. Groups define how incoming calls are distributed among a set of users (simultaneous ring, round-robin, etc.).
Group user, 2 operations
add_group_userAdd group userPOSTAdds a user to a call group. Once added, the user will receive calls routed to this group according to the group's ring strategy (simultaneous, round-robin, etc.).remove_group_usersRemove group usersDELETERemoves one or more users from a call group. The request body is an array of user IDs to remove. Once removed, these users will no longer receive calls routed to this group.
Ivr, 2 operations
get_ivrGet ivrGETRetrieves detailed information about a specific IVR by its identifier, including its configuration, assigned numbers, scenarios, welcome message settings, business hours.list_ivrsList ivrsGETRetrieves all IVR (Interactive Voice Response) configurations for your team.
Presence, 2 operations
get_user_presenceGet user presenceGETRetrieves the current presence status for a specific user, whether they are available, on a call, in snooze mode, or offline.list_presencesList presencesGETRetrieves presence information for **all users** in your team in a single request.
Profile, 2 operations
get_profileGet profileGETRetrieves detailed information about a specific profile (permission template) by its ID. The response includes the profile's name, associated features, and configuration.list_profilesList profilesGETRetrieves all profiles (permission templates) defined for your team. A profile groups telephony features, call routing rules, and access levels that can be assigned to users.
Sms, 2 operations
send_one_way_smsSend one way smsPOSTSends a one-way (push) SMS. This endpoint is restricted to admin users with `Conversations Write` permission. Recipients cannot reply to one-way SMS.send_smsSend smsPOSTSends an SMS message. Phone numbers must be in E.164 format.
Task, 2 operations
create_tasks_batchCreate tasks batchPOSTCreates multiple tasks at once from a list of phone numbers. Returns the UUIDs of the created tasks. **Permission:** No specific permission required. A valid API key is sufficient.list_team_tasksList team tasksPOSTRetrieves tasks for your team based on the provided filters. **Permission:** No specific permission required. A valid API key is sufficient. **Monitoring:** No impact.
Transcription, 2 operations
get_transcriptionGet transcriptionGETRetrieves a single transcription by its Call ID. **Permission:** This endpoint is not governed by API token permissions.list_transcriptionsList transcriptionsGETRetrieves your team's call transcriptions with optional filters (date range, duration, pagination). **Permission:** This endpoint is not governed by API token permissions.
Webhook event, 2 operations
add_webhook_eventsAdd webhook eventsPATCHAdds events to a webhook, keeping the ones it is already subscribed to. The resulting set is the union of both, so re-sending an event that is already subscribed has no effect.replace_webhook_eventsReplace webhook eventsPUTReplaces the **whole** set of events delivered to a webhook.
Whatsapp message, 2 operations
list_whatsapp_messagesList whatsapp messagesGETRetrieves the message history of a WhatsApp conversation. Use `limit_count` and `last_message_uuid` for pagination; both are optional and `limit_count` defaults to 100.send_whatsapp_messageSend whatsapp messagePOSTSends a text message in an existing WhatsApp conversation. **Permission:** Access is managed by the WhatsApp service. No specific API token permission is checked.
Call channel, 1 operation
archive_call_channelArchive call channelDELETEArchive a single leg (channel) of a terminated call.
Call log, 1 operation
archive_call_logsArchive call logsDELETEArchives call logs associated with specified channels for the authenticated user's team. Optionally archives CDR (Call Detail Record) data as well.
Call survey answer, 1 operation
list_call_survey_answersList call survey answersGETRetrieve all survey (satisfaction questionnaire) answers associated with a specific call.
Campaign log, 1 operation
list_campaign_logsList campaign logsGETRetrieves the complete audit log for a specific campaign.
Conversation member, 1 operation
list_conversation_membersList conversation membersGETReturns all members of a specific conversation. **Permission:** `Conversations Read` required. **Monitoring:** Optional.
Empower call log, 1 operation
list_empower_call_logsList empower call logsPOSTReturns a list of Empower call records (CDR list).
Empower chat message, 1 operation
send_empower_chat_messageSend empower chat messagePOSTSends a chat message to the Empower AI assistant in the context of a specific call. The AI uses the call transcription and conversation history to generate a response.
Empower moment, 1 operation
list_empower_call_momentsList empower call momentsGETRetrieves the key moments detected by Empower AI during the specified call (e.g. objections, commitments, questions). **Permission:** `Empower Read` required.
Empower summary, 1 operation
get_empower_call_summaryGet empower call summaryGETRetrieves the AI-generated summary and recap for the specified call, including key topics, action items, and sentiment analysis.
Message, 1 operation
list_conversation_messagesList conversation messagesGETReturns the first 100 messages in a specific conversation by default. Use `limit_count` and `last_id_returned` to paginate through results.
Sms opt in, 1 operation
opt_in_sms_numberOpt in sms numberPOSTRemoves a phone number from your team's outbound SMS opt-out list, so SMS can be sent to it again. It is the exact reverse of `opt_out_sms_number`.
Sms opt out, 1 operation
opt_out_sms_numberOpt out sms numberPOSTAdds a phone number to your team's outbound SMS opt-out list. Any later attempt to send an SMS to that number is blocked, and nothing is charged.
Snooze label, 1 operation
list_snooze_labelsList snooze labelsGETRetrieves the list of predefined snooze labels available for your team (e.g., "meeting", "lunch", "break", "training").
Snooze log, 1 operation
list_user_snooze_logList user snooze logGETRetrieves the snooze activity log for a specific user. Each entry shows a past snooze event with the snooze type (reason), start/end timestamps, and duration.
Team, 1 operation
get_teamGet teamGETRetrieves a complete `team` object containing lists of `numbers`, `users`, `ivrs`, `conferences`, `tags` and `groups`. **Permission:** No specific permission required.
User profile, 1 operation
assign_user_profileAssign user profilePOSTReplaces the user's current profile with the one matching the given `profileId`.
Whatsapp account, 1 operation
list_whatsapp_accountsList whatsapp accountsGETRetrieves all WhatsApp accounts associated with your user. **Permission:** Access is managed by the WhatsApp service. No specific API token permission is checked.
Whatsapp conversation, 1 operation
list_whatsapp_conversationsList whatsapp conversationsPOSTRetrieves WhatsApp conversations, optionally filtered by account UUID, with pagination support. **Permission:** Access is managed by the WhatsApp service.
Showing the first 120 of 146 endpoints. The rest are in the product, searchable from the workflow builder and from chat.
Use Ringover from Claude Code, Cursor or Codex
Connect Ringover in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Ringover operations become tools the client can call, next to every other integration you connected.
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"
[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"{
"mcpServers": {
"livecontext": {
"type": "http",
"url": "https://livecontext.ai/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}How to connect Ringover
- Create your workspace
Sign up free. Nothing to install.
- Connect Ringover once
Add your Ringover connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
- Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.
Ringover integration FAQ
What can you do with the Ringover integration?
LiveContext exposes 146 operations on Ringover, covering blacklisted number, call, campaign and conversation.
