Ringover Contacts API

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.

GitHub OpenAPI

Operations 13

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 /contacts List contacts · List your contacts #
Ask an LLM
“How do I list all my contacts and the ones shared with me?”
“Can I search my contacts by name or company?”
Tell an agent
List my contacts.
Find contacts matching {search}.
POST /contacts Retrieve or create contacts · Retrieve or create contacts #
Ask an LLM
“How do I create new contacts in one request?”
“Can I retrieve contacts using a filter object instead of listing them all?”
Tell an agent
Create these new contacts.
Retrieve contacts matching a filter.
GET /contacts/{contactId} Get a contact · Get a specific contact #
Ask an LLM
“How do I look up one contact's full details and phone numbers?”
“What data is returned for a single contact?”
Tell an agent
Get contact {contactId}.
Show me the phone numbers of contact {contactId}.
PUT /contacts/{contactId} Update a contact · Update a contact #
Ask an LLM
“How do I change a contact's first name or company?”
“Does updating a contact replace its phone numbers?”
Tell an agent
Update contact {contactId} with first name {firstname}.
Replace the phone numbers of contact {contactId} with {numbers}.
DELETE /contacts/{contactId} Delete a contact · Delete a contact #
Ask an LLM
“How do I permanently delete a contact?”
“Can I remove a contact from my address book?”
Tell an agent destructive · confirm first
Delete contact {contactId}.
Remove the contact {contactId} from my address book.
PATCH /contacts/{contactId}/shared/toggle Share or unshare a contact · Toggle shared status of a contact #
Ask an LLM
“How do I make a contact visible to my team?”
“Can I stop sharing a contact with others?”
Tell an agent
Toggle the shared status of contact {contactId}.
Make contact {contactId} visible to my team members.
PATCH /contacts/{contactId}/firstname/{firstname} Rename a contact's first name · Update a contact's first name #
Ask an LLM
“How do I change just a contact's first name?”
“Can I update a contact's first name in the URL path?”
Tell an agent
Set the first name of contact {contactId} to {firstname}.
Rename contact {contactId} to {firstname}.
PATCH /contacts/{contactId}/lastname/{lastname} Rename a contact's last name · Update a contact's last name #
Ask an LLM
“How do I change a contact's last name?”
“Can I update a contact's surname in the path?”
Tell an agent
Set the last name of contact {contactId} to {lastname}.
Rename contact {contactId}'s surname to {lastname}.
PATCH /contacts/{contactId}/company/{company} Rename a contact's company · Update a contact's company #
Ask an LLM
“How do I change the company name on a contact?”
“Can I update a contact's company in the URL path?”
Tell an agent
Set the company of contact {contactId} to {company}.
Rename contact {contactId}'s company to {company}.
POST /contacts/{contactId}/numbers Add phone numbers to a contact · Add phone number(s) to a contact #
Ask an LLM
“How do I add a new phone number to a contact?”
“Can I add several numbers to a contact at once?”
Tell an agent
Add these numbers to contact {contactId}.
Append new phone numbers to contact {contactId}.
DELETE /contacts/{contactId}/numbers Delete all phone numbers of a contact · Delete all phone numbers of a contact #
Ask an LLM
“How do I remove every phone number from a contact?”
“Can I clear all numbers on a contact?”
Tell an agent destructive · confirm first
Delete all phone numbers of contact {contactId}.
Clear every number on contact {contactId}.
PUT /contacts/{contactId}/numbers/{number} Replace a contact's phone number · Update a contact's phone number #
Ask an LLM
“How do I replace an existing phone number on a contact?”
“Can I change a contact's number to a new E.164 number?”
Tell an agent
Replace number {number} on contact {contactId} with {new_number}.
Update contact {contactId}'s existing number {number} to {new_number}.
DELETE /contacts/{contactId}/numbers/{number} Delete one phone number from a contact · Delete a specific phone number from a contact #
Ask an LLM
“How do I remove a single phone number from a contact?”
“Can I delete one specific number from a contact?”
Tell an agent destructive · confirm first
Delete number {number} from contact {contactId}.
Remove the {number} number on contact {contactId}.

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-contacts-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-contacts-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 Contacts 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 (34 KB total) ---
# Full source: https://artifacts.apis.io/ringover/openapi/ringover-contacts-api-openapi.yml