Voice tech,
made easy to build.

Bridge an agent and a customer with a single GET request — ideal for links and webhooks that can only fire a URL.

How it works: Pass your token, the did to show as caller ID, the agent's ext_no and the customer's phone as query parameters. The platform rings the agent first, then dials the customer and bridges both legs.

Use it for click-to-call links, no-code tools and webhook actions that can only call a URL.

Bridge an agent and a customer with a POST request — the standard way to trigger click-to-call from your backend.

How it works: Send the did (caller ID), the agent ext_no and the customer phone. The platform calls the agent, then the customer, and connects the two legs in about a second.

Use it for “call me” buttons, CRM click-to-dial, support callbacks and sales follow-ups.

Bridge two numbers with extra control — a spoken intro, scheduling and explicit first/second legs.

How it works: Pass the did, first_phone and second_phone (and optional body message, schedule_datetime/timezone). The platform calls the first leg, optionally plays the message, then dials and bridges the second.

Use it for scheduled callbacks, whisper announcements before connect and custom two-party bridges.

Retrieve recordings for click-to-call calls.

How it works: Call the endpoint to get recording references for bridged click-to-call calls.

Use it for QA, training and compliance review of callbacks.

Bridge two people through your DID without revealing either party's real phone number — the same call-masking pattern Uber and Ola use to connect riders and drivers.

How it works: you pass both real numbers and a did. The platform calls the first party, then the second, and connects the two legs. Each party sees only your DID on their handset — never the other person's number. The mapping lives only inside the session, so once the call (or job) is over the link is gone and the numbers can never be harvested.

Use it for marketplaces, ride-hailing and deliveries, classifieds, real estate and healthcare — anywhere a buyer and seller must talk while keeping personal numbers private. Manage a live session with /api/click_connect_update (e.g. cancel it) and pull per-session records with /api/click_connect_logs.

Update or cancel a live number-masking (Click-Connect) session.

How it works: Identify the session with did and first_number, then pass an action (e.g. cancel) and optional body message to change or drop the connection.

Use it for ending a masked call early or adjusting a session in flight.

Fetch logs for your number-masking (Click-Connect) sessions.

How it works: Pass an optional did and from_date/to_date range; the API returns who connected, when and for how long.

Use it for auditing privacy-masked conversations and reconciling marketplace calls.

List every call flow (IVR) configured in your account, with its ID and name.

How it works: Send your token; the API returns all saved call flows so you can pick a flow_id to play on outbound calls.

Use it for populating a flow picker, or looking up a flow_id before calling dial_by_flow.

Place an outbound call and play a pre-built IVR call flow to the customer.

How it works: Pass the did_no, the flow_id to play and the customer_no. The platform dials the customer and runs the flow, capturing the keypresses defined in it; add schedule_datetime and timezone to send it later.

Use it for order confirmations, reminders, surveys and any menu-driven outbound call.

Place an outbound call that speaks a text-to-speech message built from a template.

How it works: Pass the did_no, customer_no and a template_name, filling any Variable placeholders. The platform dials the customer and reads out the rendered message; schedule it with schedule_datetime.

Use it for OTP and voice alerts, personalized reminders and confirmations without recording audio.

List your auto-dialer campaigns with their IDs and status.

How it works: Send your token to get every dialer you've created, so you can pick a dialerid to load numbers into or start and stop.

Use it for showing a campaign dashboard, or looking up a dialerid before adding numbers.

Add a single contact to an existing auto-dialer campaign.

How it works: Pass the dialerid with the number (and optional name / order_id). The contact joins the campaign's queue and is called when the dialer runs.

Use it for dripping new leads or COD orders into a running campaign one at a time.

Add many contacts to an auto-dialer campaign in one request.

How it works: Pass the dialerid and an array of numbers; all are queued for the campaign at once.

Use it for loading a full contact list or daily batch before starting a campaign.

Start, pause or stop an auto-dialer campaign.

How it works: Pass the dialerid and the new status; the platform begins or halts dialing immediately.

Use it for launching a campaign, pausing during off-hours or stopping once a target is met.

List the saved customer/contact lists in your account.

How it works: Send your token to retrieve every contact list with its name and ID.

Use it for choosing an audience when building a campaign.

Create a new named customer list to group contacts.

How it works: Pass a listname; the API creates an empty list you can then fill with contacts.

Use it for segmenting audiences — by city, product or campaign — before dialing.

Create an outbound text-to-speech dialer campaign.

How it works: Define the name, did_no, calls-per-attempt (no_of_call), calling window (start_time/end_time) and the text_template_id to speak. The campaign is created ready for numbers.

Use it for setting up recurring TTS broadcasts — reminders, offers or alerts.

Update the settings of an existing text-to-speech dialer.

How it works: Pass the dialer id with any fields to change — name, did_no, calling window or text_template_id.

Use it for retuning a campaign's hours, message or pace without recreating it.

Add a batch of records to a dialer campaign.

How it works: Pass a recordList array of contacts; all are queued for dialing in one call.

Use it for bulk-loading leads from a form, sheet or nightly export.

Trigger a flow-based outbound call with simple query parameters.

How it works: Pass your token, did, flow and phone (with optional body); the platform dials the number and plays the flow.

Use it for webhook actions and links that can only send query parameters.

Turn an agent extension on or off.

How it works: Pass the ext_no and the desired status; a disabled agent can't make or receive calls until re-enabled.

Use it for suspending agents who've left a shift, are offboarding or are temporarily blocked.

Create a new agent with a login and extension.

How it works: Pass name, email, phonenumber and password; the agent is provisioned and can sign in to take calls.

Use it for onboarding new team members programmatically from your HR or admin tool.

Assign or change the DID number tied to an agent.

How it works: Pass the agent_ext and the did_num; outbound calls from that agent then show the new DID.

Use it for giving agents local caller IDs or moving numbers between team members.

List the agents in your account.

How it works: Send your token to retrieve all agents with their extensions and status.

Use it for team dashboards and looking up an extension before assigning calls.

List all extensions configured in your account.

How it works: Call the endpoint to get every extension with its owner and state.

Use it for mapping extensions to agents and building routing UIs.

Get the full configuration of a single extension.

How it works: Pass the ext_no to retrieve its settings, owner and assigned DID.

Use it for showing or editing one extension's setup.

Deactivate the user on a group extension.

How it works: Pass the ext_no; that user can no longer use the extension until reactivated.

Use it for revoking access when someone leaves a shared line or team.

Set an expiry date on an extension.

How it works: Pass the ext_no and expiry_date; the extension auto-disables after that date.

Use it for temporary agents, trials and contractor access.

Create a new group extension with its user and call settings.

How it works: Pass name, extn_no, password and options like did_no, call_forwarding, expiry_date and kyc_required; the extension is provisioned ready to take calls.

Use it for onboarding team members onto shared DIDs with the right routing.

Fetch your full call history for a date range.

How it works: Pass from_date and to_date; the API returns calls across click-to-call, dialer and inbound with status and timing.

Use it for reporting, reconciliation and syncing call activity into your CRM.

Look up all calls involving a specific phone number.

How it works: Pass your token and the phone; the API returns every log entry for that number.

Use it for showing a contact's call history on their profile screen.

Fetch logs specific to click-to-call (agent↔customer bridge) calls.

How it works: Call the endpoint to get click-to-call records with connection status and duration.

Use it for measuring callback success and agent response on click-to-call.

Look up click-to-call records for one phone number.

How it works: Pass your token and the phone to get that number's click-to-call history.

Use it for tracing a specific customer's callback attempts.

Fetch the results of an auto-dialer campaign.

How it works: Pass the dialerid to get every attempted call with answer status, keypresses and outcome.

Use it for reconciling campaign delivery and acting on customer responses.

Get the list of call status values you can filter by or set on records.

How it works: Send your token to retrieve the supported status labels (e.g. answered, missed, busy).

Use it for building status filters and dropdowns in your dashboard.

Attach a status and note to a call record.

How it works: Pass the record_id with call_status, call_type and call_remark; the record is updated for reporting.

Use it for logging dispositions — interested, callback, wrong number — against each call.

Pull new call logs since your last sync, across all call types.

How it works: Pass the last seen IDs (last_c2c_log_id, last_call_log_id, last_dialer_log_id); the API returns only newer records so you never refetch.

Use it for efficient incremental syncs into a data warehouse or CRM.

Attach a note and status to a specific call.

How it works: Pass the sip_call_id with the note, call_type and status to annotate that call.

Use it for logging dispositions and context against individual calls.

List the DID (virtual) numbers linked to your account.

How it works: Call the endpoint to retrieve every DID you own with its details.

Use it for populating caller-ID pickers and auditing your number inventory.

List the regions where DID numbers are available to buy.

How it works: Send your token to get the regions you can search and purchase numbers in.

Use it for driving a region selector before searching for a number.

Search for DID numbers available to purchase.

How it works: Pass country_code, region and an optional search_pattern; the API returns matching available numbers.

Use it for letting customers pick a local or vanity number to buy.

Purchase a DID number and add it to your account.

How it works: Pass the country and the chosen number; the platform provisions it and links it to you.

Use it for self-serving new local presence or campaign numbers.

List the DID numbers linked to your account.

How it works: Call the endpoint to retrieve every DID with its status and assignment.

Use it for auditing numbers and choosing caller IDs.

Search for purchasable DID numbers by region and pattern.

How it works: Pass did_region, availabilty_level, pattern_last_digits and size to get matching available numbers.

Use it for offering customers a choice of local or memorable numbers.

Provision and configure a DID — routing, owner and options — in one call.

How it works: Pass did_no with settings like extn_no, call_forwarding, connection, expiry_date and kyc_required to set up or update the number.

Use it for fully automating number onboarding and routing changes.

Configure a DID shared by a group or team.

How it works: Pass did_no with the group's settings — call_forwarding, connection, expiry_date and kyc_required — to manage the shared number.

Use it for running a team hotline or department line by API.

Configure a group DID for a SIP / softphone user.

How it works: Pass did_no with the SIP user's details (email, phone) and routing options to provision them on the shared number.

Use it for putting softphone or WebRTC agents on a shared DID.

Check the live status of your DID numbers.

How it works: Send your token to see which DIDs are active and reachable right now.

Use it for uptime dashboards and routing health checks.

Check live DID status in the agent's context.

How it works: Send your token to get the agent's DIDs and their current state.

Use it for showing agents whether their lines are live.

List the AI voice bots configured in your account.

How it works: Call the endpoint to get each bot with its ID, so you can reference one when placing AI calls.

Use it for populating a bot selector before dialing with an AI agent.

Place an outbound call answered by an AI voice bot over your WebSocket bridge.

How it works: Pass the customer_no and a wss_url (plus optional system_msg, sttlanguage_code and wss_header). The call connects to your WebSocket for real-time, two-way audio — speech-to-text in, audio out, with in-call transfers and DTMF.

Use it for AI receptionists, lead qualification calls and conversational reminders.

Place an outbound call handled by a pre-built voice bot.

How it works: Pass the customer_no, did_num and the Voicechat_id (with optional system_msg/text). The platform dials and runs the chosen bot.

Use it for running a saved conversational bot without wiring up your own WebSocket.

List your AI voice bots.

How it works: Call the endpoint to get each bot with its ID and metadata.

Use it for choosing a bot when configuring AI calls.

Get a voice bot's configuration and training data.

How it works: Pass the voicebot_id (and the aitraingdata flag) to retrieve its setup and knowledge.

Use it for inspecting or syncing a bot's training before deploying it.

Create a reusable text-to-speech template.

How it works: Pass a template_name and the text_content (with variable placeholders); it's saved for use by TTS dialers.

Use it for standardizing OTP, reminder and alert scripts across campaigns.

Check whether a text template is approved and ready to use.

How it works: Pass the template_name to get its current status.

Use it for confirming a template is live before launching a dependent campaign.

List your text-to-speech templates.

How it works: Send your token to retrieve every template with its name and status.

Use it for showing a template picker when building TTS dialers.

Save a contact to your address book.

How it works: Pass name, number and country_code; the contact is stored for lookups and screen-pops.

Use it for syncing CRM contacts so agents see names on incoming calls.

Look up a saved contact by phone number.

How it works: Pass the phone to get the matching contact's stored details.

Use it for caller-ID screen-pops and click-to-dial lookups.

Look up a contact in the calling agent's context.

How it works: Pass the phone to resolve the contact as visible to the agent handling the call.

Use it for powering agent screen-pops scoped to their own contacts.

List the variables available for call flows and text templates.

How it works: Send your token to get the variable keys you can insert into messages and flows.

Use it for showing available merge fields when authoring templates.

Resolve details about an inbound caller.

How it works: Pass the caller_number to get any stored contact and history for that caller.

Use it for instant screen-pops the moment a call rings.

Register a URL to receive real-time call events.

How it works: Pass your webhookurl and a secret_key; the platform POSTs events — rings, answers, hangups, DTMF — to that URL, signed with your key.

Use it for syncing call state into your app, triggering automations and verifying payloads.

Fetch lead data formatted for CRM integration.

How it works: Call the endpoint to pull lead and call data ready to push into your CRM.

Use it for feeding leads and call outcomes into your sales pipeline.