Lusha's API and Connectors let you bring verified contact and company data directly into your own systems and workflows — automatically, at scale, without manual exports.
Whether you're a developer building a custom integration or a RevOps manager setting up a no-code automation, Lusha has a path for you. Everything lives in API Hub — accessible from the left sidebar — with dedicated tabs for APIs, Connectors, Webhooks, MCP, and Manage API Keys.
The Lusha API
The API gives you programmatic access to Lusha's full data set — contacts, companies, enrichment, signals, and lookalikes. Use it to enrich records the moment they enter your systems, build waterfall enrichment logic, or power your own internal tools with Lusha data.
Common use cases:
Enrich inbound form submissions in real time before they hit your CRM
Bulk-enrich existing records on a schedule
Trigger outreach based on job change or hiring signals
Find lookalike contacts and companies from your best customers
Your API key is available in API Hub (left sidebar). Use the Copy API key button in the top right, or go to the Manage API Keys tab to view and manage all your keys. Visible to Admins and Managers only.
Connectors
Connectors are pre-built integrations between Lusha and popular automation platforms. They're the fastest way to get Lusha data flowing into your stack without writing code.
Supported platforms include Zapier, Make, n8n, Workato, Pipedream, Albato, Clay, and Google Sheets. Each connector lets you trigger enrichment from an event in another tool — a new CRM lead, a form submission, a spreadsheet row — and push the enriched data wherever you need it. Open the Connectors tab in API Hub to browse use cases, platform tiles, and ready-to-use templates.
API or Connectors — which should you use?
Use the API if you're a developer, need custom logic, or want to integrate Lusha directly into your own product or internal tooling
Use Connectors if you want to automate enrichment without code, using tools your team already runs
💡 Note: Both the API and Connectors consume Lusha credits. Credit cost depends on the data points returned — check All There Is to Know About Lusha's API for a full breakdown.
Now you're ready to put Lusha data to work across your entire stack.