Ringover API

Quick Start

First calls against the real Ringover Public API (v2)

1. Get your API key

  1. Open the Ringover Dashboard
  2. Go to Developer → API Keys
  3. Create a key, set permissions per category (see Authentication)
  4. Copy the key

No Bearer prefix

The header is Authorization: your-api-key-here — the raw key, not Bearer <key>.

2. Get your team

curl --header "Authorization: your-api-key-here" \
  https://public-api.ringover.com/v2/teams

No specific permission is required for this call; a valid key is enough. With Monitoring OFF you get a team object scoped to your own data; with Monitoring ON you get the full team (all numbers, users, IVRs, conferences, tags, groups).

3. List users

curl --header "Authorization: your-api-key-here" \
  https://public-api.ringover.com/v2/users

Requires Users Read.

4. List terminated calls (paginated)

curl --get "https://public-api.ringover.com/v2/calls" \
  --header "Authorization: your-api-key-here" \
  --data-urlencode "limit_count=50" \
  --data-urlencode "limit_offset=0"

Requires Calls Read. See Pagination for limit_count / limit_offset and the last_id_returned cursor variant.

5. Send an SMS

curl -X POST "https://public-api.ringover.com/v2/push/sms" \
  --header "Authorization: your-api-key-here" \
  --header "Content-Type: application/json" \
  -d '{
    "from_number": "+33123456789",
    "to_number": "+33612345678",
    "content": "Hello"
  }'

Requires Conversations Write. Phone numbers must be E.164.

6. Query the MCP endpoint (AI tools)

The docs show the MCP endpoint as POST /mcp (relative path — they don't show its full URL alongside a host). Using the same host as the REST API:

curl -X POST "https://public-api.ringover.com/mcp" \
  --header "Authorization: your-api-key-here" \
  --header "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Confirm the exact MCP host/path

Verify the exact MCP URL (with or without /v2) against your Dashboard or developer.ringover.com before relying on it — the published docs only show the relative path /mcp.

MCP has its own rate limits (1 req/s, burst 10) separate from the REST API, and exposes 36 read-only tools.

Rate limits & errors

  • 2 requests/second per key → 429 if exceeded.
  • See Errors for the full status-code table.

Next

On this page