Skip to main content
Webhooks let Lusha push HTTP POST requests directly to your server the moment a tracked signal fires. Instead of polling the API, you register a subscription for a contact or company and receive a delivery to your endpoint in real time - complete with the signal data, a verifiable signature, and billing details.

​
What webhooks deliver

When a subscribed entity triggers a signal, Lusha sends a signed JSON payload to your webhook URL. Signals include contact events such as promotions and job changes, as well as company events such as commercial activity news and growth milestones. For the full list of available signal types, see the Signal Options reference.

​
Key features

​
Available endpoints

​
Rate limits

​
Credits and billing

Credits are charged when a signal is detected and delivered to your webhook. The billing.creditsCharged field in each payload shows how many credits were used for that delivery. Each signal is charged once - retries due to delivery failures do not incur additional charges.

​
Prerequisites

Your account must have a webhook secret before subscriptions can receive deliveries. Generate one by calling POST /api/account/secret/regenerate and store it securely - it is only shown once.
Before creating your first subscription:
  1. Call POST /api/account/secret/regenerate to generate your account secret.
  2. Store the secret in your secrets manager - you cannot retrieve it again.
  3. Use the secret to verify signatures on every incoming delivery.
Webhook URLs must use HTTPS in production. HTTP URLs are not accepted.