Introduction

Drive Xebit voice agents over HTTPS from any language: start and track calls, manage appointments and receive outcomes by webhook.

Showing instructions for Xebit VoiceCloud.Showing instructions for Xebit VoiceKit, on your own infrastructure. Switch with the selector at the top. Updated 22 October 2026.

The Xebit API lets your own systems start voice conversations, follow them through to an outcome and manage the appointments your agents book. Everything is plain HTTPS with JSON bodies, so any language or automation tool that can send an HTTP request can use it.

What Xebit does

Xebit runs AI voice agents that hold real phone conversations at scale and then turn each call into structured data. You can call it from a custom CRM integration, a backend job or a no-code workflow. The API and the webhooks are designed so that developers can wire it in without talking to anyone first.

Xebit does not supply phone numbers or telephony. Calls go out over your own carrier and SIP trunks, and the number a call comes from is a number on your trunk that you have configured in Xebit.

Key capabilities

  • Outbound calls on demand: place a call now or schedule it for later with one request.
  • Transcripts: get the full record of what was said as soon as a call ends.
  • Summary and sentiment: every completed call carries an AI generated summary, sentiment, next steps and a disposition.
  • Appointments: read availability, book, reschedule and cancel appointments in the built in booking engine.
  • Asynchronous notifications: outbound webhooks push call and appointment events to your server so you never have to poll.

Base URL

All versioned endpoints live under /v1.

On Xebit VoiceCloud the base URL is https://api.voice.xebit.ai/v1. Xebit operates the platform and issues your keys from the Xebit VoiceCloud dashboard.

On Xebit VoiceKit the base URL is https://<your-xebit-voicekit-host>/v1, the host your team deployed Xebit VoiceKit on. Keys are issued from the Xebit VoiceKit admin console of your own deployment.

Ways to integrate

ChannelHow it authenticatesTypical use
REST APIx-api-key headerBackend logic, scheduling and anything that needs a response you can act on.
Inbound webhooksSecret token in the URLNo-code tools and simple CRM triggers that can only send a POST.
Outbound webhooksX-Webhook-Signature (HMAC-SHA256)Receiving call and appointment outcomes in real time.

Next steps: your first call

  1. Create credentials in Auth Setup.
  2. Read how keys, scopes and errors work in API Keys.
  3. Place a call with Creating Calls, then follow it with Call Status or Outbound Webhooks.