Vivoldi Webhook — Real-Time Event Delivery
Deliver real-time event data for link clicks, coupon redemptions, and stamp rewards reliably, even under high-traffic workloads.
From HMAC-SHA256 signature verification and duplicate event prevention to automatic retries, enterprise-grade reliability is built in and ready to use without additional configuration.
What Is the Vivoldi Webhook?
The Vivoldi Webhook is a real-time server-to-server integration system that pushes event data directly to your endpoint the moment an event occurs.
Without requiring separate API polling, event data is instantly delivered to endpoints registered in Vivoldi, enabling fast and seamless real-time data synchronization.
💡 Why use Webhooks?
Traditional API polling requires sending requests to the server at regular intervals, which can lead to unnecessary API traffic and delays in detecting events.
Vivoldi Webhook calls your server only when an event actually occurs, enabling immediate responses without unnecessary requests.
It is ideal for time-sensitive workflows such as CRM updates, payment processing, and marketing automation.
Webhook Workflow
Vivoldi Webhooks work in four steps: event detection → signature generation → HTTPS delivery → delivery confirmation.
Event detection
When an event occurs on a link, coupon, or stamp card with Webhooks enabled, Vivoldi detects it immediately.
Signature generation
Before delivery, Vivoldi generates an HMAC-SHA256 signature for the payload and includes it in the request headers.
Your server can verify this signature to confirm that the request was sent by Vivoldi.
HTTPS delivery
Vivoldi sends a POST request to the registered Callback URL. The response timeout is 5 seconds.
Delivery confirmation
If your server returns a 2xx response, the delivery is considered successful. If no response is received or an HTTP error is returned, Vivoldi proceeds with the retry process below.
Where do I configure Webhooks?
Configuring a global Webhook alone does not cause events to be sent. Global settings define the default Callback URL and Secret Key used for event delivery. Events are sent only when Webhooks are enabled for the relevant link, coupon, or stamp card.
If a separate Webhook is configured for a link group, coupon group, or stamp card, that configuration takes precedence over the global settings. Even if both the global and individual Webhooks are enabled, each event is sent only once.
What happens if delivery fails?
Delivery is considered failed if the response status code is not 2xx or no response is received within 5 seconds.
Failed requests are retried regardless of the response status code, so a single delivery failure does not disable the Webhook.
A delivery failure does not disable the Webhook immediately.
Vivoldi first sends an email notification about the failure and then provides a 60-minute grace period.
If the receiving server recovers within that time, the Webhook remains enabled and delivery continues.
| Stage | Timing | Action |
|---|---|---|
| Immediate retry | After 1 sec · 2 sec | Retries are performed to handle temporary network errors. Including the initial delivery, a total of 3 attempts are made. |
| Delayed retry | After 10 min · 20 min | Additional retries are performed to account for receiving server restarts or temporary service interruptions. Including the initial delivery, up to 5 attempts are made. |
| Warning notification | About 30 min | The Webhook is not disabled at this stage. An email notification is sent with details about the failed endpoint and the cause of the failure. |
| Grace period | 60 min | If the receiving server recovers within the grace period, delivery automatically resumes without disabling the Webhook. Coupon and stamp events that occurred during the grace period are also delivered sequentially. |
| Automatic disablement | About 90 min | If delivery failures continue after the grace period, the Webhook status is changed to System disabled and an email notification is sent. |
If continuous failures occur from the same receiving endpoint, delivery is temporarily paused and Vivoldi performs test deliveries to check whether the server has recovered.
Requests are managed to prevent them from continuously building up on an unresponsive receiving server. Short interruptions, such as customer deployments or temporary outages, are automatically resolved.
Coupon usage and stamp earning events are never lost.
Since these are important one-time events, they are stored in a queue during delivery retries or rate limiting and delivered sequentially once delivery can resume.
Link click events occur repeatedly, and all analytics data is stored in Vivoldi. Therefore, no additional delivery attempts are made during temporary delivery restrictions.
When a Webhook is automatically disabled
Webhook status is managed using three states.
Use the Webhook filter on the list page to view Webhooks by status.
- Active The Webhook is operating normally and events are being delivered.
- Disabled The Webhook has been manually disabled by the user.
- System disabled The Webhook has been automatically disabled by Vivoldi due to repeated delivery failures. An email notification is sent when it is disabled.
The System disabled status can be re-enabled from the dashboard after resolving the issue with the receiving server.
After re-enabling, delivery resumes for new events. Events that occurred while the Webhook was disabled are processed according to the previous policy.
Webhook Key Features
Real-time Automation
Automate your marketing, CRM, and payment workflows with instant updates for link visits, coupon usage, and stamp collection & reward redemption.
Enterprise Security
Protect Link, Coupon, and Stamp events from tampering and replay attacks through HMAC-SHA256 signatures, content hashing, and timestamp verification.
Operational Reliability
Ensure reliable processing of Link, Coupon, and Stamp events even during system failures — with at-least-once delivery, automatic retries, email notifications, and deactivation logic.
Availability by plan
Webhooks are available on Premium plans and higher. The number of available Webhooks is limited based on the number of targets where Webhooks can be enabled.
| Free · Personal | Premium | Business | Business Plus | Enterprise | |
|---|---|---|---|---|---|
| Webhook usage | — | ✓ | ✓ | ✓ | ✓ |
| Individual links | — | 1 | 5 | 1 per 1,000 links per month (up to 50) |
Unlimited |
| Link groups | — | — | — | — | Unlimited |
| Individual coupons | — | Unlimited | Unlimited | Unlimited | Unlimited |
| Coupon groups | — | — | Unlimited | Unlimited | Unlimited |
| Stamp cards | — | 1 | 5 | 1 per 1,000 links per month (up to 50) |
Unlimited |
| Requests per minute / hour | — | 240 / 12,000 | 384 / 20,000 | Starting at 614 / 32,000 | Starting at 960 / 48,000 |
Webhook request limits are set to 80% of the API request limits.
For the Business Plus plan, the number of Webhooks available increases based on the selected monthly link creation limit.
Enterprise plans are provided through a separate agreement based on your usage requirements.
See request limits by plan for detailed limits.
Link group Webhooks are available exclusively on the Enterprise plan.
When a Webhook is enabled for a link group, it is automatically applied to all links included in that group.
Upgrading to a higher plan immediately expands your Webhook usage limits.
If you downgrade to a lower plan and have targets that exceed the new limit, the oldest targets are automatically disabled first. A list of disabled targets will be sent by email.
Even if your account switches to the Free plan after the subscription period ends, your Webhook settings are preserved and will resume automatically without additional setup when you subscribe to a paid plan again.
✨ Enterprise-grade Real-time Integration
Optimized for enterprise environments that handle large-scale link, coupon, and stamp event processing.
Built on high-availability infrastructure and reliable queueing systems, Vivoldi delivers stable integrations with your CRM, payment, and analytics platforms without event loss, even during sudden traffic spikes.