Overview
After creating a Webhook, you can send a test event to check whether the receiving system can successfully receive requests from Appical. You can also use Delivery History to check Webhook events that Appical has attempted to send and investigate failed deliveries.
Example
You have created a Webhook for course.completed, but the receiving system is not showing the expected information. You can check Delivery History to see whether Appical sent the event and what response was returned.
Steps to test a Webhook
→ Send a test event
Go to Settings > Webhooks and open the Webhook you want to test.
Click Send test event. Appical sends example data for a fictional user (Jane Doe) using the first Trigger configured for the Webhook.
→ Check Delivery History
Open Delivery History for the Webhook. Here you can see each delivery attempt, including the Event, Response code, Time, and Status. You can filter the Delivery History by status and Trigger. Click a delivery to see more information about the request Appical sent and the response from the receiving system.
📌 Note: A delivery is considered successful when the receiving system responds with a 2xx status code within 30 seconds.
Delivery, retries and failures
Appical tries each delivery once. There are no automatic retries, and none are planned. A failed delivery can only be resent by hand from Delivery History.
We recommend accepting webhooks into a queue: the endpoint stores the request, answers with a 2xx code straight away, and your system processes it from the queue. This keeps the response well within the 30-second limit, and a slow or failing step on your side does not lose the event.
Success means the receiver answered with a 2xx status code within 30 seconds. Anything else is marked Failed: a 3xx redirect, a 4xx or 5xx code, a timeout, an unreachable host or an SSL error.
Timing: requests are sent in the background, normally within seconds. They have the lowest priority of Appical's background jobs, so they can be delayed while large jobs run, such as a big user import. Events can arrive out of order.
Delivery History on the webhook's page lists every attempt with the event, response code, time and status, and can be filtered by status and trigger. Clicking a row shows the request headers and body, and the response status, headers and body (the body is cut off after 64 KB). Header values such as Authorization, Cookie and API keys are shown as [REDACTED].
Replay: the replay icon on a delivery sends the same body with the same webhook-id again, as a new attempt. This only works while the webhook is enabled.
Repeated failures do not disable the webhook and do not send an alert. Check Delivery History yourself.
Retention: delivery history is kept until the webhook is deleted.
Steps to troubleshoot a failed Webhook
→ Check the delivery status
Open the failed event in Delivery History and check the response code and error information. A delivery can be marked as failed when:
The receiving system returns a 3xx, 4xx, or 5xx response.
The receiving system does not respond within 30 seconds.
The URL cannot be reached.
An SSL error occurs.
If no response was received, the response code is shown as "—". Open the delivery details to view the error message.
→ Check the receiving system
If Appical sent the request but the receiving system returned an error, check the configuration of the receiving endpoint. For example, check whether:
The URL is correct and publicly reachable.
The selected Method is accepted by the endpoint.
Any required Custom headers are configured correctly.
The receiving system is available and able to process the request within 30 seconds.
→ Replay a failed event
Appical does not automatically retry failed Webhook deliveries. To resend an event, find the failed delivery under Delivery History and click the replay icon. Appical sends the same event again as a new delivery attempt. The Webhook must be enabled before an event can be replayed.
📌 Important:
Repeated failures do not automatically disable the Webhook and do not generate an alert.
We recommend checking Delivery History if you suspect that events are not being received correctly.
Webhook requests are normally sent within seconds, but they can sometimes be delayed while larger background jobs are running. Events may also arrive in a different order than they occurred.
👉 Let us know if this article answered your question by using the buttons below. If not, get in touch with our Support Channel for more information: