See what Klovio costs for your operation. Personalized quote in your inbox in 60 seconds.

Troubleshoot webhooks

Last updated May 2026

When a webhook isn’t working, the problem is almost always at one of three points: Klovio, the network, or your endpoint.

Check the delivery log

Settings → Developers → Webhooks shows recent deliveries and their results. Start here — it tells you whether Klovio sent the event and what your endpoint replied.

Common problems

Nothing in the log. You may not be subscribed to that event. Check the webhook’s event list.

Sent, but failed. Your endpoint returned an error or didn’t respond. Check:

  • The URL is correct and publicly reachable.
  • Your endpoint responds quickly — a slow reply can time out.
  • Your server isn’t rejecting the request (firewall, auth).

Events arriving twice. That’s expected — Klovio retries if it isn’t sure a delivery succeeded. Your endpoint should handle a repeated event without doing the work twice.

Test in isolation

Use the Send test button on the webhook to fire a known event on demand. If the test arrives but real events don’t, the issue is your event subscription, not your endpoint.

Re-deliver

If your endpoint was down, fix it and re-send failed deliveries from the log — no event is lost.

Tip: log every webhook your endpoint receives, with its timestamp. When something looks missing, your own log plus Klovio’s log together pinpoint the gap fast.

Was this article helpful?

Still stuck? Our team replies in about 47 minutes on average.