Ringover Empower API

Access Ringover [Empower](https://www.ringover.com/sales-enablement-tool) AI features: call transcriptions, AI-generated summaries, key moments detection, mood analysis, and analytics. CDN URLs on a call (`transcription_url`, `recap_url`, `audio_url`, `video_url`) cannot be opened with a public API token. Download those files with `POST /cdn/download`. **Permissions required:** - **Read** (`Empower R`): Access call data, summaries, moments, analytics, flags, chat with AI. - **Write** (`Empower W`): Manage call tags, delete calls/media, manage flags. **Monitoring impact:** None — visibility is controlled by your **Empower role**: - *Empower Admin*: See all team calls. - *Empower Supervisor*: See calls from supervised users. - *Standard User*: See only your own calls.

GitHub OpenAPI

Operations 14

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /empower/calls List calls analyzed by Empower · List analyzed calls #
Ask an LLM
“Which calls has Empower analyzed for a given date range?”
“Can I filter Empower-analyzed calls by mood or language?”
Tell an agent
List Empower-analyzed calls from {call_date_from} to {call_date_to}.
Show calls with mood {mood_label} in language {language}.
DELETE /empower/calls Delete Empower-analyzed calls or their media · Delete analyzed calls or their media #
Ask an LLM
“Can I remove only the audio from Empower-analyzed calls and keep the call records?”
“How do I delete several Empower calls at once?”
Tell an agent destructive · confirm first
Delete media only from Empower calls {call_uuids}.
Delete Empower calls {call_uuids} entirely.
POST /empower/logs/calls Get Empower call logs · Get Empower call logs #
Ask an LLM
“Can I get the call detail records (CDR) for a date range?”
“Which calls were flagged with a specific transcription state?”
Tell an agent
Get Empower call logs from {start_date} to {end_date}.
List Empower call logs with transcription state {transcription_state}.
GET /empower/platform/{platformName}/channel/{channelID} Get an Empower call UUID from a platform channel · Get call UUID from platform and channel #
Ask an LLM
“How do I find the Empower call UUID for a call on a specific platform channel?”
“Can I cross-reference a Ringover call with a call on another platform?”
Tell an agent
Get the Empower call UUID for channel {channelID} on {platformName}.
Look up the call on {platformName} channel {channelID} in Empower.
POST /empower/chat Ask Empower AI a question about a call · Send a message to Empower AI chat #
Ask an LLM
“Can I ask Empower AI to summarize a call's conversation history?”
“How do I send a chat message to Empower AI for a specific call?”
Tell an agent
Ask Empower AI on call {call_id}: {message}.
Chat with Empower AI about call {call_id} using transcription {transcription}.
GET /empower/call/{callUUID} Get full details of an Empower-analyzed call · Get call details by UUID #
Ask an LLM
“What scores and metadata does Empower give a specific call?”
“Can I see the full transcription of one Empower-analyzed call?”
Tell an agent
Get full details of Empower call {callUUID}.
Show scores and metadata for Empower-analyzed call {callUUID}.
GET /empower/call/{callUUID}/moments Get key moments detected in a call · Get key moments detected in a call #
Ask an LLM
“Which objections, commitments or questions did Empower detect in a call?”
“What key moments were flagged in a specific Empower-analyzed call?”
Tell an agent
Get key moments detected in call {callUUID}.
List the objections and commitments found in Empower call {callUUID}.
GET /empower/call/{callUUID}/summary Get the AI-generated summary of a call · Get AI-generated call summary #
Ask an LLM
“What does Empower's AI summary say about a call?”
“Can I get a recap of a call's key topics and action items?”
Tell an agent
Get the AI summary of call {callUUID}.
Show the recap for Empower-analyzed call {callUUID}.
POST /empower/call Get call summaries for a user in a date range · Retrieve call summaries by date range or user #
Ask an LLM
“Can I get Empower call summaries for one user over a date range?”
“How do I get recap, moments and scores for a user's calls?”
Tell an agent
Get call summaries for user {user_id} from {start_date} to {end_date}.
Summarize {limit} calls for user {user_id} in {start_date} to {end_date}.
POST /empower/analytics Download Empower analytics and statistics · Download Empower analytics and statistics #
Ask an LLM
“Can I download Empower analytics as a CSV file?”
“Which Empower stats types can I request?”
Tell an agent
Download Empower analytics as {output}.
Get Empower {type} stats for user {user_id} in {time_frame}.
POST /empower/upload/call Upload an external call or video for Empower analysis · Upload an external call or video for analysis #
Ask an LLM
“How do I upload an external call recording for Empower AI analysis?”
“Can I upload a video call and have Empower analyze it?”
Tell an agent
Upload an external call {file} for analysis with direction {call_direction}.
Upload video call {file} with {speaker_count} speakers for Empower analysis.
GET /empower/flags List flags configured for the team · List team flags #
Ask an LLM
“What flags are available to tag calls with?”
“Which call flags have been set up for my team?”
Tell an agent
List all team flags.
Show the flags I can use to tag calls.
POST /empower/flag/{flag_id}/call/{call_uuid} Tag a call with a flag · Associate a flag with a call #
Ask an LLM
“Can I tag a call with a flag so I can review it later?”
“How do I associate a flag with a specific call?”
Tell an agent
Tag call {call_uuid} with flag {flag_id}.
Add flag {flag_id} to call {call_uuid}.
DELETE /empower/flag/{flag_id}/call/{call_uuid} Remove a flag from a call · Disassociate a flag from a call #
Ask an LLM
“Can I untag a call by removing its flag?”
“How do I take a flag off a call I already tagged?”
Tell an agent destructive · confirm first
Remove flag {flag_id} from call {call_uuid}.
Untag call {call_uuid} by deleting flag {flag_id}.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/ringover:ringover-empower-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

ringover-empower-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  license:
    name: Proprietary – Contact us for usage terms
    url: https://www.ringover.com/contact
  description: '# Ringover Public API


    Welcome to the Ringover Public API. This RESTful API lets you integrate Ringover telephony, messaging, contacts, and AI analytics into your applications. ## Base URL


    | Region | Base URL |

    |--------|----------|

    | Europe | `https://public-api.ringover.com/v2` |

    | United States | `https://public-api-us.ringover.com/v2` |


    ## Authentication


    All requests must include your API key in the `Authorization` header:


    ```

    Authorization: your-api-key-here

    ```


    To create an API key:

    1. Open the Ringover Dashboard. 2. Navigate to **Developer > API Keys**. 3. Click **Create an API key**, select a user, and set a label. 4. Configure the permissions for this key (see Permissions below). ## Permissions


    Each API key is associated with **7 permission categories**, each configurable as **None**, **Read**, **Write**, or **Read+Write**:


    | Category | Controls access to |

    |----------|-------------------|

    | **Calls** | Call history, archives, live call controls, callbacks |

    | **Contacts** | Contact CRUD and phone number management |

    | **Users** | User listing, plannings, presences, groups, user blacklists |

    | **Numbers** | Phone number listing, team blacklist |

    | **IVRs** | IVR/scenario listing, tag management |

    | **Conversations** | SMS/Chat conversations, messages, SMS sending |

    | **Empower** | AI call analysis, summaries, moments, analytics |


    ### The Monitoring flag (Supervision)


    In addition to R/W permissions, each API key has a **Monitoring** toggle that controls the **scope** of data returned:


    | Monitoring | Effect |

    |------------|--------|

    | **OFF** | Your permissions give access to **your own data only** (your calls, your numbers, your conversations…) |

    | **ON** | Your permissions give access to **the entire team''s data** (all users, all calls, all conversations…) |


    Monitoring does **not** grant additional permissions — it widens the scope of existing ones. Some routes **require** Monitoring to be enabled and will return `401` without it. Conversely, some routes may ignore the Monitoring flag entirely or apply it differently — unless stated otherwise in the endpoint documentation, the default behavior described above applies. > Each endpoint in this documentation specifies its exact permission and monitoring requirements. ### Special cases


    - **Campaigns, Tasks, WhatsApp**: These routes do not require specific token permissions. A valid API key is sufficient. - **Empower**: Uses its own role system (Admin / Supervisor / User) in addition to the Empower R/W permission. - **Transcriptions**: Access is controlled by a team-level setting, not by the token permissions. - **Conferences**: All conference routes require Monitoring enabled. ## Rate Limiting


    A **2-request-per-second** rate limit is applied per API key. Exceeding this limit returns `429 Too Many Requests`. ## Pagination


    List endpoints support offset-based pagination with two parameters:

    - `limit_count`: Maximum number of items to return (default: 100, max varies by endpoint). - `limit_offset`: Number of items to skip (default: 0). Some call-related endpoints also support cursor-based pagination via `last_id_returned`. ## Error Responses


    | HTTP Code | Meaning |

    |-----------|---------|

    | `400` | Bad request — invalid parameters or body |

    | `401` | Unauthorized — invalid/expired API key, or access denied by permission/monitoring checks on most endpoints |

    | `403` | Forbidden — authenticated request refused by specific endpoint logic (notably some Empower routes) or upstream forwarded services |

    | `402` | Payment required — feature not available on your plan |

    | `404` | Resource not found |

    | `429` | Rate limit exceeded |

    | `500` | Internal server error |


    ## SCIM 2.0 Provisioning


    Ringover exposes a **SCIM 2.0** server (RFC 7643 / RFC 7644) for automated user and group provisioning from your identity provider (Okta, Microsoft Entra ID, …). It reuses the **same API key** as the REST API (`Authorization` header).'
  version: 2.1.0
  title: Ringover Public Empower API
  x-logo:
    url: https://webcdn.ringover.com/app/img/misc/logo_app_redoc.png
    backgroundColor: '#FAFAFA'
    altText: Ringover Logo
  termsOfService: https://ringover.com/terms/
  contact:
    email: support@ringover.com
servers:
- url: https://public-api.ringover.com/v2
  description: Production server (Europe)
- url: https://public-api-us.ringover.com/v2
  description: Production server (United States)
security:
- Authorization: []
tags:


# --- truncated at 32 KB (80 KB total) ---
# Full source: https://artifacts.apis.io/ringover/openapi/ringover-empower-api-openapi.yml