Auth Setup

Create an API key, find your inbound webhook URL and register an outbound webhook with its signing secret.

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.

Three credentials cover every way of talking to Xebit: an API key for the REST API, a secret inbound webhook URL for tools that can only send a POST, and a signing secret for the outbound webhooks Xebit sends to you. All three are managed on the Integrations page of the Xebit VoiceCloud dashboardthe Xebit VoiceKit admin console.

API key

An API key gives a program access to the Xebit API.

  1. Open the Xebit VoiceCloud dashboard → Integrations → API Keysthe Xebit VoiceKit admin console → Integrations → API Keys.
  2. Choose Generate New Key and pick the scopes the integration needs.
  3. Copy the key straight away. It is shown once and cannot be retrieved later.

Send the key in the x-api-key header on every request:

HTTP
x-api-key: YOUR_API_KEY

Inbound webhook URL

An inbound webhook URL lets an outside tool create, cancel or delete calls without handling an API key. The secret token inside the URL is the credential.

  1. Open the Xebit VoiceCloud dashboard → Integrations → Inbound Webhooksthe Xebit VoiceKit admin console → Integrations → Inbound Webhooks.
  2. Copy your unique inbound URL.
  3. Use it as the destination for POST requests from your tool.

Example: https://api.voice.xebit.ai/v1/hooks/{YOUR_SECRET_TOKEN}

Example: https://<your-xebit-voicekit-host>/v1/hooks/{YOUR_SECRET_TOKEN}

Outbound webhook events

Outbound webhooks are how Xebit tells your server what happened on a call, as it happens.

  1. Open the Xebit VoiceCloud dashboard → Integrations → Webhook (Outbound)the Xebit VoiceKit admin console → Integrations → Webhook (Outbound).
  2. Enter your HTTPS endpoint URL.
  3. Select the events you want, for example call.completed.
  4. Copy the webhook secret. You need it to verify signatures.

Signature verification

Each delivery carries an X-Webhook-Id header holding the event's event_id, plus two signing headers:

HeaderDescription
X-Webhook-TimestampUnix time in seconds at which the payload was signed. It is part of the signed string.
X-Webhook-SignatureThe signature, formatted as v1=<base64-encoded HMAC-SHA256>.

The signature is HMAC-SHA256(secret, "{timestamp}.{rawBody}"), Base64 encoded (not hex) and prefixed with v1=. X-Webhook-Id is not signed; only the timestamp and the raw body are.

Use the secret exactly as displayed, whsec_ prefix included. The prefix is part of the HMAC key. Do not remove it and do not Base64 decode the secret. The full rules and common mistakes are on Outbound Webhooks.

# Send a signed test delivery to your own endpoint
SECRET="YOUR_WEBHOOK_SECRET"
TIMESTAMP=$(date +%s)
PAYLOAD='{"event_id":"evt_123","event_type":"call.completed"}'
SIG="v1=$(printf '%s.%s' "$TIMESTAMP" "$PAYLOAD" | openssl dgst -sha256 -hmac "$SECRET" -binary | base64)"

curl -X POST https://your-server.example.com/webhook \
  -H "Content-Type: application/json" \
  -H "X-Webhook-Timestamp: $TIMESTAMP" \
  -H "X-Webhook-Signature: $SIG" \
  -d "$PAYLOAD"

Configuration summary

Integration pointAuthenticationBest for
Call APIx-api-key headerBackend logic and scheduling
Inbound webhooksUnique secret token in the URLNo-code tools and simple CRM triggers
Outbound webhooksX-Webhook-Signature (HMAC-SHA256)Real-time status sync and outcome logging

Keep API keys and webhook secrets out of public repositories and client-side code. Load them from environment variables on your server.