Skip to main content
April 2026 was a focused month: webhook subscriptions gained full delivery visibility, with a logs panel, status filters, a health indicator, and CSV or JSON export.

Overview

April brought one change, aimed at anyone who keeps an Alvys webhook pointed at another system. Until now there was no way to see whether an event actually arrived. You can now open any webhook and read its full delivery history — what was sent, whether it succeeded, and what the receiving system said when it failed — without leaving Alvys.

Integrations & API (April 15)

Delivery Logs for your webhook subscriptions

Webhook subscriptions now keep a visible record of every delivery attempt. Open Settings → API → Webhooks, select a webhook, and the Delivery Logs panel lists each attempt with its event type, a Success, Failed, or Skipped status badge, a timestamp, and the error message when something went wrong. A health indicator on the webhook’s detail page flags an endpoint that has started to degrade, so you can spot a failing integration before someone downstream reports missing data. What this includes:
  • A status filter to narrow the list to All, Success, Skipped, or Failed.
  • Export .CSV and Export .JSON buttons at the bottom of the panel, for audit trails or analysis elsewhere. The export covers the entries matching your current filters, so set the filters first.
  • Email notification to Partner Admins when a webhook is automatically disabled after repeated failures.
  • A “Skipped” status, which means the subscription was disabled or paused at the moment the event fired — not that the delivery failed.
Replaying a failed delivery from this screen is not part of this release. For now, export the failures and re-trigger the events from your own system. This rolls out with the Public API feature set, so the panel appears once your account has access to the Webhooks section under Settings. Learn more: How to Monitor Webhook Deliveries