VoixCall

VoixCall for developers

Build with VoixCall

Connect an AI assistant or your own code to a VoixCall account. Phase 1 is live on api.voixcall.com; the rest of the surface ships in dated, additive steps.

VoixCall lets people call phone numbers in 160+ countries from a browser or app at published per-minute rates, with their own verified number as caller ID, virtual numbers in 60 countries, an SMS inbox for receiving codes, and AI call summaries. Most paying users are abroad, calling US toll-free lines, banks and government offices that block foreign SIMs. The public API and the MCP server expose the user's own account to the assistants and apps they choose to connect: first who they are, then rates, balance, calls, contacts and numbers, later summaries, verification codes and hands-free calling where VoixCall rings the user's phone and bridges them abroad.

Connect an AI assistant

Add VoixCall to Claude Code, claude.ai or any MCP client. One URL, OAuth handled by the client, approve once on app.voixcall.com.

MCP setup โ†’

Use the REST API

Get an access token with the standard OAuth 2.1 flow, or an API key, and call /v1 from curl or your own code.

Quickstart โ†’

Read the reference

Every endpoint, parameter and response, rendered from the live OpenAPI document so it always matches what is deployed.

API reference โ†’

Live today production

  • OAuth 2.1 with PKCE (S256) at https://api.voixcall.com/oauth/authorize and /oauth/token, with refresh-token rotation and revocation. Clients register by Client ID Metadata Document or Dynamic Client Registration. Discovery at /.well-known/oauth-authorization-server.
  • GET /v1/me: the account the token or key acts for. OpenAPI 3.1 at api.voixcall.com/v1/openapi.json.
  • MCP server at https://api.voixcall.com/mcp with one tool, voixcall_whoami. Verified against production with Claude Code; claude.ai custom connectors are expected to work through the same standard flow but have not yet been exercised end to end.
  • API keys (vc_live_ / vc_test_): the management endpoints exist, but the screen to create a key in Settings ships later, so there is no self-serve way to get one yet. Use OAuth in the meantime.
  • Rate limiting with RateLimit, RateLimit-Policy, X-RateLimit-* and Retry-After headers. See rate limits.

Coming next planned

Phase 2, in progress: read endpoints and matching MCP tools for

  • rates (GET /v1/rates?to=)
  • credits: balance and transactions
  • calls: history and status, with transcript expansion
  • contacts search
  • numbers and caller ID

After that, in order: messages (receive-only inbox reads), transcripts, callback calls that ring your phone first, and webhooks. Each lands as an additive changelog entry.

What a connected app can see

Tokens act on the user's personal account only. Organization (team) calls, numbers and transcripts are never reachable through the public API or MCP, even for organization admins. Today the only data an app can read is what /v1/me and voixcall_whoami return: account id, email and display name. Each additional scope becomes meaningful as its endpoints ship. Details in privacy for connected apps.

Support and availability

Write to support@voixcall.com. Every response from api.voixcall.com carries a Request-Id header, and every error body repeats it as request_id. Include the Request-Id header value when you write: it is how we find your request in the logs.

Availability target: 99.9 % monthly availability for the API and the MCP server. This is a service-level objective, not a contractual guarantee; see the terms.

Security reports: /.well-known/security.txt.