Webhook Failures

Fix outbound webhooks that do not arrive, API requests that do not start calls, and duplicate deliveries.

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.

Webhooks and the API run in two directions. Outbound webhooks carry call events and outcomes from Xebit to your systems. API requests from your systems ask Xebit to start calls. When something is not arriving or not starting, work out which direction is failing, then check the endpoint, the key and the request.

Where to look

  • Webhook settings and API keys are in the Xebit VoiceCloud dashboard at voice.xebit.ai. The API base URL is https://api.voice.xebit.ai/v1.
  • Webhook settings and API keys are in the Xebit VoiceKit admin console on your own host. The API base URL is https://<your-xebit-voicekit-host>/v1.

Outbound webhooks not arriving

  • Is the webhook set up and enabled? Check it is configured for the events you expect, such as call ended or outcome recorded. See Outbound Webhooks.
  • Is the endpoint URL right? Check for typos, the right path and HTTPS.
  • Is the endpoint reachable? Send a request to it yourself and confirm it answers.
  • Does it return a success status? If your endpoint returns an error, the delivery is treated as failed.
  • Did the event happen? A call that failed to connect does not produce the same events as a completed one. Check the call in the calls list.

On Xebit VoiceCloud the endpoint must be reachable from the internet.

On Xebit VoiceKit the endpoint must be reachable from your deployment. On an air gapped deployment nothing leaves the network, so the endpoint must be inside it.

API requests not starting calls

  • Is the request well formed? Check it includes the agent and a destination number, as described in Creating Calls.
  • Is the number in E.164 format? A plus sign, the country code and the number, with no spaces.
  • Is the API key valid? A 401 means the key is missing, wrong or revoked. See Auth Setup and API Keys.
  • Are you over a limit? Check Rate Limits, and that the account has minutes left this month or a top up.
  • Is there capacity? Check your deployment's concurrency, node capacity and licence band.
  • Did the call start but fail? If the request succeeded, find the call in the calls list. A failed to connect disposition points at the number or your trunk. See Carrier and SIP Trunk Issues.

It was working and stopped

What it usually means: the endpoint moved, the key changed or the receiving server went down.

  • Check whether your endpoint URL, server or certificate changed recently.
  • Check the API key is still active. If it was rotated or revoked, create a new one and update every system that uses it.
  • Check your server's logs for errors around the time deliveries stopped.

Receiving duplicate events

What it usually means: your endpoint takes too long to acknowledge, so the same event is delivered again.

  • Respond with a success status as soon as the request arrives.
  • Do the real work, such as writing to your CRM, in the background after responding.
  • Use the event ID in each payload to recognise and ignore events you have already processed.

Still need help?

Email hello@xebit.ai or use the contact page, with the call ID or event ID, your endpoint's response and the time it happened.

Support is included in your Xebit VoiceKit licence.

Next steps