Introduction
An overview of the Voisnap platform — architecture, services, supported channels, and API base URLs.
Introduction
Voisnap is a voice AI agent platform that provides everything you need to deploy intelligent, production-grade voice agents at scale. It abstracts away the complexity of telephony providers, speech-to-text (STT), text-to-speech (TTS), and large language model (LLM) orchestration behind a single unified API.
Architecture overview
The Voisnap platform is composed of three distinct API services:
1. Main API
Base URL: https://api.voisnap.ai/api/v1
The primary REST API for managing all resources: agents, conversations, telephony numbers, knowledge bases, webhooks, analytics, and billing. This is the API you'll use most frequently. All endpoints require authentication via API key or JWT.
2. Runtime API
Base URL: https://api.voisnap.ai (real-time WebSocket hubs)
The runtime layer handles live call sessions. It exposes three SignalR hubs:
- VoiceHub (
/hubs/voice) — bidirectional PCM audio streaming for phone/WebRTC calls - ChatHub (
/hubs/chat) — real-time text message exchange for web chat - WebRtcHub (
/hubs/webrtc) — WebRTC signaling (SDP offer/answer, ICE candidates)
3. Admin API
Base URL: https://api.voisnap.ai/api/v1/admin
Restricted to platform administrators and agency accounts. Provides tenant management, global configuration, usage monitoring, and partner program endpoints. Agency accounts use a subset of the Admin API for client management.
Supported channels
Voisnap agents can communicate across a wide range of channels:
| Channel | Description |
|---|---|
| Phone (Twilio) | Inbound and outbound calls via Twilio voice numbers |
| Phone (Vonage) | Inbound and outbound calls via Vonage (Nexmo) voice numbers |
| Phone (Telnyx) | Inbound and outbound calls via Telnyx voice numbers |
| WebRTC | Browser-based voice calls using the WebRTC protocol |
| WebChat | Embedded text chat widget on any website |
| SMS | Two-way SMS messaging via Twilio/Vonage/Telnyx |
| WhatsApp Business API messaging | |
| Telegram | Telegram Bot API messaging |
Each channel has its own configuration section within an agent's settings. A single agent can serve multiple channels simultaneously with channel-specific greeting messages and behavior overrides.
Environments
| Environment | API Base URL | Console URL | Purpose |
|---|---|---|---|
| Production | https://api.voisnap.ai | https://console.voisnap.ai | Live traffic |
| Sandbox | https://sandbox.api.voisnap.ai | https://console.voisnap.ai (toggle env) | Testing, no real calls or billing |
:::note Sandbox environment calls do not connect to real telephony carriers. Test calls play a simulated audio response using your agent's voice and LLM configuration. API keys issued in production do not work in sandbox; generate separate sandbox keys from the Console. :::
All API keys are prefixed with vsnp_ for production and vsnp_sb_ for sandbox.
API versioning
The current API version is v1. All Main API endpoints are prefixed /api/v1/.
Voisnap follows a non-breaking change policy: new optional fields and new endpoints may be added at any time without a version bump. Breaking changes (field removal, response restructuring, endpoint removal) will be announced with a minimum 90-day deprecation window before a new version is introduced.
The API version is included in the X-Api-Version response header:
X-Api-Version: 1
X-Request-Id: req_01HXK8Z...Data residency
By default, all data is processed and stored in the US East region. Enterprise plans can request EU or APAC data residency. The region is reflected in your API base URL:
| Region | API Base URL |
|---|---|
| US East (default) | https://api.voisnap.ai |
| EU West | https://eu.api.voisnap.ai |
| APAC Southeast | https://ap.api.voisnap.ai |