Webhooks
Send scans, leads and QR code changes to your own systems the moment they happen.
Webhooks push events from EZQR to a URL you control. Use them to add new leads to your CRM, log scans in your data warehouse, or alert your team when a destination goes down. Every request is signed so you can verify it came from EZQR.
This page covers setting up endpoints in the dashboard. For payload formats and signature verification, see the webhooks API reference.
Events
| Event | Sent when |
|---|---|
qr.scanned | A dynamic QR code was scanned |
qr.created | A QR code was created |
qr.updated | A QR code was edited |
qr.deleted | A QR code was deleted |
qr.destination_down | A dynamic QR code's destination stopped responding |
qr.destination_recovered | A dynamic QR code's destination is reachable again |
lead.created | A lead was captured from a form, lead gate or business card |
card.viewed | A business card was opened |
Add an endpoint
Open webhook settings
Go to Settings → Webhooks and click Add endpoint.
Enter the URL
Add your Endpoint URL and an optional Description. The URL must use https:// on the standard port and be reachable on the public internet.
Choose events
Under Events, select the events this endpoint should receive.
Save the signing secret
After you add the endpoint, EZQR shows its signing secret. Copy it and store it with your receiving code. You use it to verify the EZQR-Signature header.
Your endpoint should respond with a 2xx status code. Any other status, or no response within 10 seconds, counts as a failed delivery.
Test an endpoint
Open the endpoint's menu and choose Send test. EZQR sends a ping event to the URL. Check Recent deliveries a few seconds later to see the result.
Delivery history
Choose Recent deliveries from the endpoint's menu to see the latest 25 deliveries. Each one shows the event, its status and the HTTP status your endpoint returned. You can resend a delivery from here, which makes a single new attempt.
Retries
If a delivery fails, EZQR retries it with increasing delays, starting at about a minute and spacing out to a few hours between attempts. Retries continue for about ten hours before the delivery is marked as failed.
Automatic disabling
If 20 deliveries in a row fail after all their retries, EZQR turns the endpoint off and shows how many deliveries failed. Fix the endpoint, then switch it back on with its toggle. A successful delivery resets the count.
You can also switch an endpoint off yourself at any time. Events aren't sent to endpoints that are off.
Signing secret
Each endpoint has its own secret. From the endpoint's menu:
- Show signing secret displays the current secret.
- Rotate secret replaces it with a new one straight away. Update your receiving code with the new secret.
See the webhooks API reference for how to verify signatures.
Endpoints from Zapier and Make
When you use the Zapier or Make apps, they create endpoints for you. These appear in the list marked with the app that created them, and don't count toward your plan's endpoint limit.
Who can manage webhooks
In a team workspace, only owners and admins can add, edit, test or delete endpoints and view secrets.
Plan limits
| Free | Lite | Pro | Max | |
|---|---|---|---|---|
| Webhook endpoints | Not included | Not included | 5 | 25 |