Skip to main content
Every webhook subscription keeps a log of its delivery attempts. Open a webhook from Settings and use the Delivery Logs panel to see what was sent, whether it arrived, and what your endpoint returned when it failed.

​
Overview

When Alvys sends an event to your webhook endpoint, the result is recorded. The Delivery Logs panel on a webhook’s detail page shows each attempt with its outcome, so you can tell the difference between “Alvys never sent it” and “your endpoint rejected it” without asking anyone to check a server log. A health indicator on the same page flags an endpoint that has started failing, which is usually the first sign that something changed on the receiving side — an expired certificate, a moved URL, a deploy that broke a handler. Also known as: webhook logs, delivery history, webhook failures, webhook troubleshooting.

​
Before You Start

  • Your account needs the Alvys Public API enabled, and you need access to the Webhooks section under Settings.
  • At least one webhook subscription must exist. Logs are recorded per subscription, so a webhook created today has no history yet.
  • Delivery logs are retained according to the standard Alvys data retention policy. Export anything you need to keep for an audit trail.

​
Steps

  1. Open your webhook subscriptions.
    • Go to Settings → API → Webhooks.
    • The page lists the webhook subscriptions configured for your account.
  2. Open the webhook you want to inspect.
    • Click the webhook to open its detail page.
    • The Delivery Logs panel opens alongside the webhook’s configuration.
  3. Read the delivery history. Each entry in the panel shows:
    • Event type — which event Alvys attempted to deliver.
    • Status — a badge reading Success, Failed, or Skipped.
    • Timestamp — when the attempt was made.
    • Error message — what your endpoint returned, shown only when the attempt failed.
    The list loads a page of entries at a time, so scroll or page through for older attempts.
  4. Narrow the list to what you are investigating.
    • Use the status filter to show All, Success, Skipped, or Failed.
    • Filtering to Failed is the fastest way to see whether failures share one event type or one time window.
  5. Export the history if you need it outside Alvys.
    • Use Export .CSV or Export .JSON at the bottom of the logs panel.
The export covers the entries matching your current filters and the pages already loaded — not the entire history. Apply the status filter you want and load the range you need before exporting, or you will get a partial file.

​
Result

You can see the outcome of every delivery attempt on the subscription, tell whether a failure came from Alvys or from your endpoint, and hand a developer an exported log instead of a description.

​
Understanding the statuses

A run of Skipped entries almost always means the subscription was turned off — including automatically, after repeated failures. Check whether the webhook is still enabled before investigating the endpoint.

​
Webhook health and automatic disabling

The webhook detail page shows a health indicator so you can spot a degrading endpoint at a glance rather than by reading the log. If a webhook keeps failing, Alvys disables it automatically and emails your Partner Admins. Once that happens the subscription stops attempting deliveries, and subsequent events are recorded as Skipped. Fix the endpoint, then re-enable the subscription.

​
Troubleshooting

​
Every recent delivery shows Failed

  1. Read the error message on one of the failed entries — it is what your endpoint returned, so it usually names the problem directly.
  2. Confirm the endpoint URL on the webhook is still correct and reachable from outside your network.
  3. Check whether the failures all start at the same timestamp. A clean cut-off usually points to a change on the receiving side rather than to Alvys.

​
Deliveries show Skipped and nothing is arriving

  1. Check whether the subscription is enabled. A paused or automatically disabled webhook records Skipped rather than attempting delivery.
  2. Check with your Partner Admins for an email about the webhook being disabled after repeated failures.
  3. Re-enable the subscription once the endpoint is fixed.

​
The log is empty

  1. Confirm the subscription has existed long enough for a matching event to have occurred.
  2. Confirm the webhook is subscribed to the events you expect to see. No matching event means no delivery attempt, and so no log entry.

​
An export is missing rows you can see on screen

Apply your filters and page through to load the entries you want first. The export only includes what your current filters and loaded pages cover.

​
FAQs

Q: Can I replay a failed delivery from this screen? A: Not currently. Export the failed entries and re-trigger the events from your own system. Q: Does a Skipped entry mean the delivery failed? A: No. Skipped means Alvys did not attempt the delivery at all, because the subscription was disabled or paused when the event was generated. Q: Will I be told when a webhook stops working? A: Yes. Partner Admins are emailed automatically when a webhook is disabled after repeated failures. The health indicator on the webhook’s detail page also reflects its current state. Q: How far back do the logs go? A: Delivery logs follow the standard Alvys data retention policy. Export the logs you need to retain beyond that. Q: Does the export include the full history? A: No — only the entries matching your current filters and the pages you have loaded.

​
Go Deeper