Why Is My Webhook Not Receiving Events?
Check webhook status, search filters, endpoint and quota
Written by Erick Horn
July 6, 2026
Updated October 16, 2026
Why is my webhook not receiving events?
Check the webhook’s status first, then test its filters, endpoint and available quota. It must be active, match new articles and receive a 2xx response within 30 seconds. The delivery log shows failed attempts and their reasons.
Is the webhook status still “active”?
Check its details in the dashboard, or list your webhooks:
curl "https://api.apitube.io/v1/webhooks" -H "X-API-Key: YOUR_API_KEY"
paused means someone stopped it. disabled means APITube stopped it after three consecutive failed deliveries. Fix the endpoint first, then set active in the dashboard or send PATCH /v1/webhooks/:id with {"status":"active"}.
See webhook retries and delivery history.

Do your filters actually match any new articles?
Try the saved filters on /v1/news/everything:
curl "https://api.apitube.io/v1/news/everything?title=acme&language.code=en&source.domain=reuters.com&api_key=YOUR_API_KEY"
If no articles match, try removing a filter at a time. Historical matches do not guarantee new ones, but they help check whether the search is too narrow. See empty search results and the official parameter reference.
Does your endpoint answer 2xx within 30 seconds?
A status outside 2xx, a redirect, a connection error or a 30-second timeout counts as failure. Redirects are not followed. Three failed deliveries in a row disable the webhook.
Store the payload, return 2xx, then do slow processing separately. Retries keep the same X-Webhook-Delivery-Id; skip a delivery your app has already processed and still acknowledge it.
Is the endpoint URL reachable from the public internet?
Use a public HTTPS URL. Localhost, private networks, loopback and link-local addresses, carrier-grade NAT ranges and their IPv6 equivalents cannot receive deliveries. A hostname that does not resolve also fails.
For local development, use a public tunnel. A blocked or unreachable destination can show a failed delivery without an HTTP status code; read its error details.
Do you still have webhook quota?
Each successfully delivered article uses webhook quota. Once it is empty, a paid account can use pay-as-you-go balance if enabled and within its spending limit. If neither can cover delivery, add funds or wait for quota renewal.
Failed deliveries are free. See what counts as a request for the separate quotas.
Still stuck? Send a test event
Click Send test event on the webhook’s details page. It sends a signed sample immediately, works while paused or disabled, and is free. The delivery log records the response and payload.
If it fails, investigate the endpoint, URL or signature handler. If it succeeds, check status, filters, new article availability and quota. See how to verify webhook signatures.
Common Questions
- How quickly should a new article arrive?
- Are failed deliveries retried?
- Am I charged while the webhook delivers nothing?
- Why did my webhook go quiet right after a deploy?
How quickly should a new article arrive?
New matches are checked about every 10 seconds, with up to 100 articles per delivery. Your plan’s data delay and any delivery retries can add time. Check history if delivery seems late.
Are failed deliveries retried?
Yes. There are up to five attempts total, with gaps of about one minute, five minutes, 30 minutes and two hours. See delivery history for attempts and the automatic-disable rule.
Am I charged while the webhook delivers nothing?
No. Only successfully delivered articles use quota. A paused, quiet or failing webhook has no delivery charge.
Why did my webhook go quiet right after a deploy?
The endpoint may have failed three deliveries in a row, disabling the webhook. Fix it, then set active again. Return 2xx promptly and move slow work after acknowledgement to avoid timeouts.