Skip to main content
The Lusha API gives you programmatic access to one of the world’s largest B2B contact and company databases. All requests go to a single base URL - https://api.lusha.com - and are authenticated with an API key you pass in a request header. Whether you are enriching CRM records, prospecting for new leads, or wiring up real-time event signals, every capability is available through a consistent REST interface.

​
What you can build

Enrichment

Add verified emails, phone numbers, and firmographics to existing contact and company records.

Prospecting

Search Lusha’s database with ICP filters to build targeted lists of contacts and companies.

Signals

Detect job changes, promotions, and company events to reach prospects at the right moment.

Webhooks

Receive real-time push notifications when signals occur for your monitored contacts or companies.

Lookalikes

Discover new prospects that resemble your best customers using AI-powered similarity search.

Account

Check your credit balance and usage at any time with the account usage endpoint.

​
Base URL

All endpoints are served from a single base URL:

​
Credits and billing

The Lusha API uses a credit-based model. Credits are charged per data point revealed (for example, an email address or phone number), with a minimum of 1 credit per request - even if no match is found. Contact your account manager for the rates on your plan. To check how many credits you have remaining, call the account usage endpoint:
The contact.isCreditCharged field in enrichment responses tells you whether a credit was consumed for a given request.

​
Your first API call

The example below fetches enriched contact data for a person by first name, last name, and company domain. Replace YOUR_API_KEY with your actual key.
A successful response returns a contact object containing email addresses, phone numbers, job title, location, and social links.
You can also search by email, linkedinUrl, or personId instead of name and company. Providing more identifiers generally improves match accuracy.
Lusha is rolling out a V3 API (endpoints under /v3/) alongside the current endpoints shown in this guide. V2 and V3 run in parallel, and V2 endpoints keep working - see the V3 migration guide if you want to plan ahead.

​
Next steps

Before making API calls in your application, read the authentication guide to understand how to pass your API key securely and what to expect when credentials are missing or invalid.