Skip to content

Troubleshooting

Common issues when integrating VoxBridge — API authentication, webhooks, calls, and billing. Still stuck? Contact support with call IDs and request timestamps.

API authentication

  • 401 Unauthorized — Verify Authorization: Bearer sk_live_... header. Keys are shown once at creation; revoke and create a new key in the dashboard if lost.
  • 403 Forbidden — Your organization may be inactive or the endpoint requires dashboard JWT instead of API key.

See Authentication for JWT vs API key usage.

Webhooks

  • Signature verification fails — Use the raw request body and your webhook secret. Compare against X-Voice-Signature per Webhooks.
  • Endpoint returns non-2xx — VoxBridge retries; fix your handler to respond within 10 seconds with HTTP 200.
  • No events received — Confirm webhook_url is set under Integration in the dashboard and reachable from the public internet.

Calls stuck in queued

  • Live dialing requires telephony configuration (SIP / carrier). Until configured, calls are persisted but remain queued. See SIP & telephony.
  • Check GET /health and system status for database and telephony checks.

Signup and login

  • Email verification required — Complete POST /auth/verify-email with the code sent to your inbox before logging in.
  • Captcha errors — Enter the numeric answer only; refresh the question if it expires.
  • Google sign-in hidden — The Google button appears only when OAuth is configured in Admin → Security. Until then, use email sign-in.

Billing and plans

  • Usage overage is charged per plan rates; view minutes and call points in the dashboard Billing panel.
  • Stripe webhooks must reach /api/payments/webhooks/stripe with a valid signing secret in server .env.

Before contacting support

  • Include API error detail, call UUID, and UTC timestamp.
  • Confirm your API key is active and webhooks return 2xx.
  • For billing, include invoice number and account email.

Support center → · Quick start → · System status →