Webhooks are automatic notifications that fire the moment something changes in your Lusha account. Instead of manually checking for updates, your external tools receive a notification as soon as an event occurs โ keeping everything in sync without any manual work.
You can now create and manage webhook subscriptions directly from the API Hub in Lusha. No API configuration required.
What you'll need
Admin access to your Lusha account
An API key (Grab your key from the API Hub โ Manage API Keys)
A target URL โ the endpoint where Lusha will send webhook payloads
Available event types
Right now, one event type is available:
Opt Out โ fires when a contact you've previously revealed opts out of Lusha's database. Use this to automatically update your CRM or suppression lists and stay compliant with consent requirements.
๐ก Coming soon: Signals webhooks are on the way. You'll be able to subscribe to buying signal events and act the moment they fire โ no manual checking needed.
How to create a webhook
Go to API Hub โ Webhooks.
Click + Create Webhook.
Select an event type. Currently available: Opt Out โ fires when a revealed contact opts out.
4. Enter a Webhook name.
5. Select your API key from the dropdown.
6. Enter your Target URL โ the endpoint that will receive the event payload.
7.
Click Save Webhook.
Your new webhook will appear in the Webhook Subscriptions list with a status toggle. It's active as soon as it's saved.
๐ก Note: You can enable or disable any webhook at any time using the status toggle in the subscriptions list. Disabled webhooks will not send notifications.
Managing your webhooks
From API Hub โ Webhooks, you can:
Toggle a webhook on or off using the status switch
Use the โฎ menu to edit or delete a subscription
Click Regenerate secret to rotate your webhook signing secret
โ ๏ธ Important: Regenerating your webhook secret will invalidate your current secret immediately. Any systems using the old secret to verify webhook payloads will need to be updated.
You're all set! Your webhook will now notify your systems automatically whenever the subscribed event occurs.

