Ringover provides a cloud‑based business phone system that unifies voice calling, messaging, and collaboration tools into a single platform. It offers features such as AI‑enhanced call handling, virtual numbers, call routing, analytics, and integrations with CRM and productivity applications, targeting enterprises and remote teams. The service is delivered via a web app and mobile apps, with a focus on scalability, security, and AI‑driven assistance for agents.
Ringover publishes 28 API contracts indexed on the APIs.io network, including Blacklist API, Callbacks API, Calls API, and 25 more. Tagged areas include Communications, Cloud, VoIP, Collaboration, and AI.
The Ringover catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 1 Spectral governance ruleset.
Ringover’s developer surface includes authentication, API reference, documentation, support, engineering blog, pricing, signup flow, and 29 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Horizontal (data, software, accessibility, platform) regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/ringover/"><img src="https://apis.io/badge/ringover/card.svg" alt="Ringover on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
MCP Server+12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card+8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Documented Reversibility+6 pts — a reversal operation in the contract, graded up when a window is documented too
Pagination+5 pts — share of collection GETs (an array, or one wrapped in data/items/results ...) that declare a page/limit/offset/cursor parameter, a Link header or a next/cursor field; na with no collection GETs
3 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Manage blacklisted phone numbers. There are two levels of blacklist: - **Team blacklist** (`/blacklists/numbers`): Blocks numbers for the entire team. Requires `Numbers R/W` + M...
Initiate phone calls between a Ringover user and an external recipient. The system calls the user first on their chosen device, then connects them to the recipient. **Permission...
Manage your Ringover call history. Retrieve terminated and current calls, apply filters (by date, type, tags, users, IVRs…), archive calls, and access survey results. **Permissi...
Manage your outbound call campaigns (Call Lists). This section provides a comprehensive overview of how to manage your campaign workflows: - Retrieve the list of campaigns, filt...
Private CDN URLs (`transcription_url`, `recap_url`, `audio_url`, `video_url`, and other Ringover CDN download links) cannot be opened with a public API token. Use `POST /cdn/dow...
Control live calls in real time. A channel represents an audio stream during a call. You can mute, hold, record, hangup, transfer, or send DTMF tones on active channels. **Permi...
Manage conference rooms. List conferences and update access PIN codes. **Permissions required:** No specific permission category, but **Monitoring must be ON** for all conferenc...
Manage your Ringover contacts. Full CRUD operations on contacts and their phone numbers. **Permissions required:** - **Read** (`Contacts R`): List and get contacts. - **Write** ...
Manage SMS and Chat conversations. List conversations and their messages, archive/unarchive, rename, and manage conversation metadata. **Permissions required:** - **Read** (`Con...
Manage your Ringover groups. Groups organize users for call distribution (ring groups). You can list groups, manage members, configure ring duration, and toggle free access. **P...
Retrieve your IVRs (Interactive Voice Response) and their scenarios. IVRs are the automated call routing systems configured on your Ringover account. **Permissions required:** -...
## Model Context Protocol The MCP endpoint exposes a **curated** set of Ringover operations to AI assistants (Claude, ChatGPT, Cursor, etc.) via the [Model Context Protocol](htt...
Manage messages within conversations. List messages, archive and unarchive individual messages. **Permissions required:** - **Read** (`Conversations R`): List messages in a conv...
Retrieve information about phone numbers assigned to your Ringover account. **Permissions required:** - **Read** (`Numbers R`): List and get number details. - **Write** (`Number...
Retrieve real-time presence information about users: planning status, snooze status, connected device, and whether they are currently in a call. **Permissions required:** - `Use...
Retrieve user profiles defined on your Ringover account. Each profile has an ID and a name. **Permissions required:** `Users Read` required. **Monitoring impact:** None — profil...
Ringover exposes a **SCIM 2.0** server (RFC 7643 / RFC 7644) so your identity provider (Okta, Microsoft Entra ID, OneLogin, …) can automatically provision, update and deprovisio...
Send SMS messages to phone numbers. Phone numbers must be in E.164 format. **Permissions required:** `Conversations Write` required. **Monitoring impact:** - *OFF*: You can send...
Retrieve the list of available snooze statuses and manage user snooze settings. Snooze temporarily changes a user's availability status. **Permissions required:** - No specific ...
Manage call tags. Tags are labels you can assign to calls for categorization and reporting. Each tag has an ID, name, color, description, and creation date. **Permissions requir...
Manage team tasks. Create, list, and manage tasks associated with your team. **Permissions:** No specific permission required. A valid API key is sufficient.
The team object is a model of your Ringover team. It contains a list of related objects: - `numbers` and related information such as their type, country and prefix according to ...
Retrieve call transcriptions. Access is controlled by a team-level setting — your team must have the transcription feature enabled. **Permissions required:** Transcription acces...
Manage your Ringover team members. Retrieve user information, manage plannings, check availability (presences/snooze), and organize user blacklists. **Permissions required:** - ...
Ringover uses webhooks to notify you any time that an event associated with your team occurs (ex: a new voicemail, the reception of a new message, a missed call...). A webhook i...
Manage WhatsApp Business messaging. Send template messages, manage templates, and handle WhatsApp conversations. **Permissions:** No specific permission required. A valid API ke...
Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.
aid: ringover
name: Ringover
description: Ringover provides a cloud‑based business phone system that unifies voice calling, messaging, and collaboration
tools into a single platform. It offers features such as AI‑enhanced call handling, virtual numbers, call routing, analytics,
and integrations with CRM and productivity applications, targeting enterprises and remote teams. The service is delivered
via a web app and mobile apps, with a focus on scalability, security, and AI‑driven assistance for agents.
url: https://artifacts.apis.io/ringover/apis.yml
image: https://www.ringover.com/favicon.ico
x-type: company
x-source: harvest:new-submission
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-28 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-28'
modified: '2026-10-28'
tags:
- Communications
- Cloud
- VoIP
- Collaboration
- AI
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
common:
- type: CapabilityMap
url: capabilities/ringover-capability-edges.yml
name: Ringover Business Capability Map
- type: AgenticAccess
url: agentic-access/ringover-agentic-access.yml
- type: RateLimits
url: rate-limits/ringover-rate-limits.yml
- type: Plans
url: plans/ringover-plans-pricing.yml
- type: Spectral
url: rules/ringover-rules.yml
- type: JSONLD
url: json-ld/ringover-context.jsonld
- type: Vocabulary
url: vocabulary/ringover-vocabulary.yml
- type: AgentSkill
url: skills/_index.yml
- type: Webhooks
url: asyncapi/ringover-webhooks.yml
- type: DataModel
url: data-model/ringover-data-model.yml
- type: Conventions
url: conventions/ringover-conventions.yml
- type: Authentication
url: authentication/ringover-authentication.yml
- type: Lifecycle
url: lifecycle/ringover-lifecycle.yml
- type: ErrorCatalog
url: errors/ringover-problem-types.yml
- type: Conformance
url: conformance/ringover-conformance.yml
- type: Overlay
url: overlays/ringover-openapi-overlay.yaml
- type: LLMsTxt
url: llms/ringover-llms.txt
- type: WellKnown
url: well-known/ringover-well-known.yml
- type: Hosts
url: hosts/ringover-hosts.yml
- type: Vendors
url: vendors/ringover-vendors.yml
- type: SDKs
url: packages/ringover-packages.yml
- type: Packages
url: packages/ringover-packages.yml
- type: Webhooks
url: https://www.ringover.com/webhooks
- type: Security
url: https://www.ringover.com/security
- type: APIReference
url: https://developer.ringover.com/
- type: GitHubOrganization
url: https://github.com/ringover
- type: DomainSecurity
url: security/ringover-domain-security.yml
- type: Website
url: https://ringover.com/
- type: Documentation
url: https://www.ringover.com/features
- type: Support
url: https://www.ringover.com/contact
- type: Blog
url: https://www.ringover.com/news
- type: Pricing
url: https://www.ringover.com/pricing
- type: SignUp
url: https://www.ringover.com/free-trial
- type: TermsOfService
url: https://www.ringover.com/terms
- type: PrivacyPolicy
url: https://www.ringover.com/privacy
- type: StatusPage
url: https://www.ringover.com/status
apis:
- aid: ringover:ringover-blacklist-api
name: Ringover Blacklist API
description: 'Manage blacklisted phone numbers. There are two levels of blacklist:
- **Team blacklist** (`/blacklists/numbers`): Blocks numbers for the entire team. Requires `Numbers R/W` + Monitoring
ON.
- **User blacklist** (`/users/{userId}/blacklists/numbers`): Blocks numbers for a specific user. Requires `Users R/W`.
**Monitoring impact:**
- *OFF*: Team blacklist routes are **blocked** (`401`). User blacklist routes work only for your own blacklist.
- *ON*: Full team blacklist management. User blacklist routes can target any team member.'
humanURL: https://developer.ringover.com/
baseURL: https://public-api.ringover.com/v2
tags:
- blacklist
properties:
- type: OpenAPI
url: openapi/ringover-blacklist-api-openapi.yml
- type: JSONSchema
url: json-schema/ringover-calls-filter-schema.json
- type: JSONSchema
url: json-schema/ringover-empower-logs-calls-response-schema.json
- type: JSONSchema
url: json-schema/ringover-empower-logs-calls-request-schema.json
- type: JSONSchema
url: json-schema/ringover-call-empower-schema.json
- type: JSONSchema
url: json-schema/ringover-conversation-light-schema.json
- type: JSONSchema
url: json-schema/ringover-get-call-empower-res-body-schema.json
- aid: ringover:ringover-callbacks-api
name: Ringover Callbacks API
description: 'Initiate phone calls between a Ringover user and an external recipient. The system calls the user first on
their chosen device, then connects them to the recipient.
**Permissions required:** `Calls Write` required.
**Monitoring impact:**
- *OFF*: You can only initiate a callback from your own number.
- *ON*: You can initiate a callback from any team member''s number using the `from_number` parameter.'
humanURL: https://developer.ringover.com/
baseURL: https://public-api.ringover.com/v2
tags:
- callbacks
properties:
- type: OpenAPI
url: openapi/ringover-callbacks-api-openapi.yml
- type: JSONSchema
url: json-schema/ringover-calls-filter-schema.json
- type: JSONSchema
url: json-schema/ringover-empower-logs-calls-response-schema.json
- type: JSONSchema
url: json-schema/ringover-empower-logs-calls-request-schema.json
- type: JSONSchema
url: json-schema/ringover-call-empower-schema.json
- type: JSONSchema
url: json-schema/ringover-conversation-light-schema.json
- type: JSONSchema
url: json-schema/ringover-get-call-empower-res-body-schema.json
- aid: ringover:ringover-calls-api
name: Ringover Calls API
description: 'Manage your Ringover call history. Retrieve terminated and current calls, apply filters (by date, type, tags,
users, IVRs…), archive calls, and access survey results.
**Permissions required:**
- **Read** (`Calls R`): List and retrieve calls, get current calls, get survey answers.
- **Write** (`Calls W`): Archive calls, initiate callbacks, control live calls (mute, hold, transfer, hangup, record,
DTMF).
**Monitoring impact — Read operations (listing):**
> **Important:** Call listing routes (`GET /calls`, `POST /calls`, `GET /calls/{callId}`) always return **all team calls**
regardless of the Monitoring flag. The Monitoring setting is not applied to call listing — these routes behave identically
whether Monitoring is ON or OFF.
**Monitoring impact — Write operations:**
- *OFF*: Archive operations apply only to **your own calls**. Live call controls (`/channels/*/events/*`) and call recording
access are **blocked** (`401`).
- *ON*: Archive operations can target **any team call**. Live call controls and call recording access are unlocked.
**Limitations:**
- Date range is limited to **15 days** maximum per request.
- `limit_count` maximum is **1000**, `limit_offset` maximum is **9000**.
- Multiple items in the call list may share the same `call_id` (occurs with transfers or IVR routing).
**Summary and transcription:**
`summary` is the Ringover summary stored for the call (plain text). `transcription` is the call transcription (speeches
and words). These are not Empower recaps. Download URLs are never returned.
A field is in one of three states:
- **omitted** — not requested
- **`null`** — requested, and the call has no summary or transcription row
- **object** — the row exists. If the file cannot be downloaded, the HTTP status stays `200` and the object sets `error.code`
(`unavailable` when the download fails, `error` or `invalid` when the provider status is not usable). `summary.text` is
then `null`.
Where they are included:
- `GET /calls` and `POST /calls` — only when the query parameter `expand` is `summary` and/or `transcription`. Repeat
it to ask for both (`expand=summary&expand=transcription`). Each value downloads a file and adds latency. `contact` is
always returned and is not an `expand` value.
- `GET /calls/{callId}` — `summary`, `transcription` and `contact` are included on every log. There is no `expand` parameter.
- MCP `calls.search` and `calls.get` — only the values passed in `expand` (`summary`, `transcription`, `contact`). Nothing
is included by default, including `contact`.'
humanURL: https://developer.ringover.com/
baseURL: https://public-api.ringover.com/v2
tags:
- calls
properties:
- type: OpenAPI
url: openapi/ringover-calls-api-openapi.yml
- type: JSONSchema
url: json-schema/ringover-calls-filter-schema.json
- type: JSONSchema
url: json-schema/ringover-empower-logs-calls-response-schema.json
- type: JSONSchema
url: json-schema/ringover-empower-logs-calls-request-schema.json
- type: JSONSchema
url: json-schema/ringover-call-empower-schema.json
- type: JSONSchema
url: json-schema/ringover-conversation-light-schema.json
- type: JSONSchema
url: json-schema/ringover-get-call-empower-res-body-schema.json
- aid: ringover:ringover-campaigns-api
name: Ringover Campaigns API
description: 'Manage your outbound call campaigns (Call Lists). This section provides a comprehensive overview of how to
manage your campaign workflows:
- Retrieve the list of campaigns, filterable by various parameters.
- Assign Ringover users to specific campaigns.
- Add or manage contacts associated with a campaign.
- Start, stop, or reset campaigns dynamically.
- Update campaign scripts to ensure consistent messaging.
- Adjust the number of allowed call retries for specific campaigns.
- Modify tags assigned to campaigns to enhance your tracking.
- Manage numbers associated with campaigns, including: adding, updating, or removing them.
- Extend the capabilities of your campaigns by adding custom columns (enriched data).
**Permissions:** No specific permission required. A valid API key is sufficient to access all campaign routes.
**Monitoring impact:** None.'
humanURL: https://developer.ringover.com/
baseURL: https://public-api.ringover.com/v2
tags:
- campaigns
properties:
- type: OpenAPI
url: openapi/ringover-campaigns-api-openapi.yml
- type: JSONSchema
url: json-schema/ringover-calls-filter-schema.json
- type: JSONSchema
url: json-schema/ringover-empower-logs-calls-response-schema.json
- type: JSONSchema
url: json-schema/ringover-empower-logs-calls-request-schema.json
- type: JSONSchema
url: json-schema/ringover-call-empower-schema.json
- type: JSONSchema
url: json-schema/ringover-conversation-light-schema.json
- type: JSONSchema
url: json-schema/ringover-get-call-empower-res-body-schema.json
- aid: ringover:ringover-cdn-api
name: Ringover Cdn API
description: 'Private CDN URLs (`transcription_url`, `recap_url`, `audio_url`, `video_url`, and other Ringover CDN download
links) cannot be opened with a public API token.
Use `POST /cdn/download` to proxy the file. Any authenticated token can call this route: the team id in the URL must match
the token''s team. Empower READ is not required.'
humanURL: https://developer.ringover.com/
baseURL: https://public-api.ringover.com/v2
tags:
- cdn
properties:
- type: OpenAPI
url: openapi/ringover-cdn-api-openapi.yml
- type: JSONSchema
url: json-schema/ringover-calls-filter-schema.json
- type: JSONSchema
url: json-schema/ringover-empower-logs-calls-response-schema.json
- type: JSONSchema
url: json-schema/ringover-empower-logs-calls-request-schema.json
- type: JSONSchema
url: json-schema/ringover-call-empower-schema.json
- type: JSONSchema
url: json-schema/ringover-conversation-light-schema.json
- type: JSONSchema
url: json-schema/ringover-get-call-empower-res-body-schema.json
- aid: ringover:ringover-channels-api
name: Ringover Channels API
description: 'Control live calls in real time. A channel represents an audio stream during a call. You can mute, hold, record,
hangup, transfer, or send DTMF tones on active channels.
**Permissions required:** `Calls Write` required for all channel operations.
**Monitoring:** **Required** for all channel control routes. Returns `401` if Monitoring is OFF. Live call control is
a supervisory feature.'
humanURL: https://developer.ringover.com/
baseURL: https://public-api.ringover.com/v2
tags:
- channels
properties:
- type: OpenAPI
url: openapi/ringover-channels-api-openapi.yml
- type: JSONSchema
url: json-schema/ringover-calls-filter-schema.json
- type: JSONSchema
url: json-schema/ringover-empower-logs-calls-response-schema.json
- type: JSONSchema
url: json-schema/ringover-empower-logs-calls-request-schema.json
- type: JSONSchema
url: json-schema/ringover-call-empower-schema.json
- type: JSONSchema
url: json-schema/ringover-conversation-light-schema.json
- type: JSONSchema
url: json-schema/ringover-get-call-empower-res-body-schema.json
- aid: ringover:ringover-conferences-api
name: Ringover Conferences API
description: 'Manage conference rooms. List conferences and update access PIN codes.
**Permissions required:** No specific permission category, but **Monitoring must be ON** for all conference routes. Returns
`401` if Monitoring is OFF.'
humanURL: https://developer.ringover.com/
baseURL: https://public-api.ringover.com/v2
tags:
- conferences
properties:
- type: OpenAPI
url: openapi/ringover-conferences-api-openapi.yml
- type: JSONSchema
url: json-schema/ringover-calls-filter-schema.json
- type: JSONSchema
url: json-schema/ringover-empower-logs-calls-response-schema.json
- type: JSONSchema
url: json-schema/ringover-empower-logs-calls-request-schema.json
- type: JSONSchema
url: json-schema/ringover-call-empower-schema.json
- type: JSONSchema
url: json-schema/ringover-conversation-light-schema.json
- type: JSONSchema
url: json-schema/ringover-get-call-empower-res-body-schema.json
- aid: ringover:ringover-contacts-api
name: Ringover Contacts API
description: 'Manage your Ringover contacts. Full CRUD operations on contacts and their phone numbers.
**Permissions required:**
- **Read** (`Contacts R`): List and get contacts.
- **Write** (`Contacts W`): Create, update, delete contacts and their numbers, toggle sharing.
**Monitoring impact:** None — contacts are always scoped to your own address book regardless of the Monitoring flag.'
humanURL: https://developer.ringover.com/
baseURL: https://public-api.ringover.com/v2
tags:
- contacts
properties:
- type: OpenAPI
url: openapi/ringover-contacts-api-openapi.yml
- type: JSONSchema
url: json-schema/ringover-calls-filter-schema.json
- type: JSONSchema
url: json-schema/ringover-empower-logs-calls-response-schema.json
- type: JSONSchema
url: json-schema/ringover-empower-logs-calls-request-schema.json
- type: JSONSchema
url: json-schema/ringover-call-empower-schema.json
- type: JSONSchema
url: json-schema/ringover-conversation-light-schema.json
- type: JSONSchema
url: json-schema/ringover-get-call-empower-res-body-schema.json
- aid: ringover:ringover-conversations-api
name: Ringover Conversations API
description: 'Manage SMS and Chat conversations. List conversations and their messages, archive/unarchive, rename, and manage
conversation metadata.
**Permissions required:**
- **Read** (`Conversations R`): List conversations and messages.
- **Write** (`Conversations W`): Archive/unarchive, rename, set purpose, send SMS.
**Monitoring impact:**
- *OFF*: Returns only **your own** conversations and non-archived messages.
- *ON*: Returns **all team** conversations including archived messages. Enables level-2 archiving (permanent) and sending
SMS on behalf of another user.'
humanURL: https://developer.ringover.com/
baseURL: https://public-api.ringover.com/v2
tags:
- conversations
properties:
- type: OpenAPI
url: openapi/ringover-conversations-api-openapi.yml
- type: JSONSchema
url: json-schema/ringover-calls-filter-schema.json
- type: JSONSchema
url: json-schema/ringover-empower-logs-calls-response-schema.json
- type: JSONSchema
url: json-schema/ringover-empower-logs-calls-request-schema.json
- type: JSONSchema
url: json-schema/ringover-call-empower-schema.json
- type: JSONSchema
url: json-schema/ringover-conversation-light-schema.json
- type: JSONSchema
url: json-schema/ringover-get-call-empower-res-body-schema.json
- aid: ringover:ringover-empower-api
name: Ringover Empower API
description: '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.'
humanURL: https://developer.ringover.com/
baseURL: https://public-api.ringover.com/v2
tags:
- empower
properties:
- type: OpenAPI
url: openapi/ringover-empower-api-openapi.yml
- type: JSONSchema
url: json-schema/ringover-calls-filter-schema.json
- type: JSONSchema
url: json-schema/ringover-empower-logs-calls-response-schema.json
- type: JSONSchema
url: json-schema/ringover-empower-logs-calls-request-schema.json
- type: JSONSchema
url: json-schema/ringover-call-empower-schema.json
- type: JSONSchema
url: json-schema/ringover-conversation-light-schema.json
- type: JSONSchema
url: json-schema/ringover-get-call-empower-res-body-schema.json
- aid: ringover:ringover-groups-api
name: Ringover Groups API
description: 'Manage your Ringover groups. Groups organize users for call distribution (ring groups). You can list groups,
manage members, configure ring duration, and toggle free access.
**Permissions required:**
- No specific permission is required to **list** groups.
- `Users Write` is required to **add or remove** members.
**Monitoring impact:**
- *OFF*: Returns only groups you belong to.
- *ON*: Returns all team groups. Unlocks group membership management, ring duration changes, and free-access toggling.
> Some group management routes **require** Monitoring ON and will return `401` without it.'
humanURL: https://developer.ringover.com/
baseURL: https://public-api.ringover.com/v2
tags:
- groups
properties:
- type: OpenAPI
url: openapi/ringover-groups-api-openapi.yml
- type: JSONSchema
url: json-schema/ringover-calls-filter-schema.json
- type: JSONSchema
url: json-schema/ringover-empower-logs-calls-response-schema.json
- type: JSONSchema
url: json-schema/ringover-empower-logs-calls-request-schema.json
- type: JSONSchema
url: json-schema/ringover-call-empower-schema.json
- type: JSONSchema
url: json-schema/ringover-conversation-light-schema.json
- type: JSONSchema
url: json-schema/ringover-get-call-empower-res-body-schema.json
- aid: ringover:ringover-ivrs-api
name: Ringover Ivrs API
description: 'Retrieve your IVRs (Interactive Voice Response) and their scenarios. IVRs are the automated call routing systems
configured on your Ringover account.
**Permissions required:**
- **Read** (`IVRs R`): List IVRs and scenarios.
- **Write** (`IVRs W`): Create tags.
**Monitoring impact:**
- *OFF*: Returns only **your own** IVRs and scenarios.
- *ON*: Returns **all team** IVRs and scenarios.'
humanURL: https://developer.ringover.com/
baseURL: https://public-api.ringover.com/v2
tags:
- ivrs
properties:
- type: OpenAPI
url: openapi/ringover-ivrs-api-openapi.yml
- type: JSONSchema
url: json-schema/ringover-calls-filter-schema.json
- type: JSONSchema
url: json-schema/ringover-empower-logs-calls-response-schema.json
- type: JSONSchema
url: json-schema/ringover-empower-logs-calls-request-schema.json
- type: JSONSchema
url: json-schema/ringover-call-empower-schema.json
- type: JSONSchema
url: json-schema/ringover-conversation-light-schema.json
- type: JSONSchema
url: json-schema/ringover-get-call-empower-res-body-schema.json
# --- truncated at 32 KB (81 KB total) ---
# Full source: https://artifacts.apis.io/ringover/apis.yml
Ringover API — frequently asked questions
Does Ringover have an API?
Yes. APIs.io lists 28 APIs from Ringover, including Ringover Blacklist API, Ringover Callbacks API and Ringover Calls API, and 25 more.
Is there an OpenAPI specification for the Ringover API?
Yes. APIs.io indexes 28 OpenAPI specifications for Ringover, each linked for download from this page.
How do I authenticate with the Ringover API?
Ringover documents its authentication (1 scheme). The details are profiled on APIs.io as Ringover Authentication.
How much does the Ringover API cost?
APIs.io lists 4 pricing plans for Ringover, with each plan's price, limits and inclusions under Pricing Plans on this page.
Is the Ringover API ready for AI agents?
Ringover has a Kin Score of 60.6 out of 100 (strong) and an Agent Readiness score of 47.9 (agent-ready), scored by API Evangelist on 2026-10-31.
Discovery needs no key. Ratings and market analysis are Pro.
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. See our Privacy Policy and
Terms.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: