Programmable telephony for developers
Initiate and receive calls, return XML call instructions, play or generate prompts, gather input, route calls, receive events, and stream audio to external services.
Official SDKs
Use maintained helpers for authentication, call control, escaped Voice XML, errors, recordings, streaming, and documented callbacks.
composer require nextgenswitch/nextgenswitch-php Open repository Python 3.9+ Install from GitHub before the first PyPI release Open repository Node.js 18+ Install from GitHub before the first npm release Open repository Developer controls
<SAY>Send text to the configured text-to-speech service and play it into the call.
<PLAY>Play an approved audio resource as part of a call flow.
<GATHER>Collect supported keypad or speech input and return it to the application.
<STREAM>Open supported bidirectional WebSocket audio for AI or specialized real-time processing.
Start outbound calls through the API using configured numbers, carriers, and destinations.
Handle call status and workflow callbacks using application endpoints.
Application patterns
Stream audio to an AI stack, execute tool actions, and transfer calls to human operations.
Explore AI agentsTrigger calls from application events and capture confirmation or response.
Explore automated callingDeliver supported codes or collect input according to the authentication and security design.
Use live application data to decide prompts, menus, routes, and destinations.
Connect voice interactions to calendars, appointment services, and confirmation workflows.
Connect calls to product, order, delivery, ticket, or custom business APIs.
Real-time AI integration
Use NextGenSwitch for SIP and call control while connecting the speech, language model, tools, and agent framework selected for the application.
Review Streaming DocsProduction responsibilities
Protect API credentials, validate requests and callbacks, rotate secrets, and restrict access.
Handle repeated events, network failures, timeouts, partial completion, and safe retry behavior.
Plan numbers, carriers, SIP routes, caller ID, codecs, destinations, concurrency, and regulatory obligations.
Log request IDs, call IDs, events, latency, errors, transfers, provider failures, and application outcomes.
Available endpoints, verbs, events, media formats, limits, and provider compatibility should be confirmed against the current documentation and deployment configuration.
Design the integration
Share your inbound/outbound flows, SIP setup, API actions, events, AI stack, concurrency, and failure requirements.
Start with Documentation Discuss Technical Scope