# Webhooks and multiple API keys Canonical: Released January 26, 2026 · Week of Jan 26 Topics: API, Automations, Admin & Billing, Signals Lusha's intelligence layer now comes to you. Webhooks send new Contact and Company Signals to your endpoint in real time, so your CRM, automations and AI agents act on them without polling. And with multiple API keys, teams and projects no longer share one key. ![Lusha webhook event payload and webhook subscriptions](https://www.lusha.com/wp-content/uploads/2026/11/Webhooks-hero-1024x608.png) ## What it is Two updates for teams building on Lusha. With webhooks, you subscribe to the contacts and companies you care about, and Lusha sends new signals to your endpoint as soon as they are detected. Opt-out notifications tell you when a contact opts out of Lusha's data processing, so you can update your CRM. With multiple API keys, every user gets their own key, and Admins and Managers can create as many keys as they need, each with its own monthly credit limit. - **Signals, delivered** New Contact and Company Signals, including intent, reach your endpoint in real time. - **Opt-out notifications** Get notified when a contact opts out, so your CRM and suppression lists stay current. - **Set up in Lusha or by API** Create webhooks under API, Webhooks in Lusha, or manage subscriptions through the API. - **Separate API keys** Give each team, project or agent its own key, with an optional monthly credit limit. [Try it](https://www.lusha.com/lusha-api/?utm_source=lusha_website&utm_medium=whats_new&utm_campaign=webhooks-and-multiple-api-keys) · [Learn more](https://docs.lusha.com/webhooks/overview) ## Good to know Creating webhooks in Lusha requires Admin access. Credits are used when a signal is delivered to your webhook, once per signal. Retries and test deliveries don't use credits. Every delivery is signed with HMAC-SHA256 and retried automatically. API keys are managed under API & connectors, Manage API Keys.