Skip to main content

All there is to know about Lusha's API

An overview of Lusha's API endpoints, authentication, rate limits, credit consumption, and how to manage API key credit limits.

Written by Hila
Updated in the last hour

Lusha's API gives you programmatic access to contact and company data for enrichment, prospecting, and sales intelligence. All requests are made over HTTPS and responses are returned in JSON format.

πŸ’‘ Note: API access requires an API key, which is available to Admins and Managers on Premium and Scale plans. For full endpoint documentation, visit docs.lusha.com.

Authentication

Find your API key on your API page. Pass it in the request header to authenticate. The key is shared at the account level β€” clicking Update generates a new key and invalidates the previous one, which will break any active integrations using the old key.

Rate limits

Limits vary by plan:

  • Free + Starter: 5/min, 10/hour, 25/day

  • Professional + Premium: 200/min, 400/hour, 2,000/day

  • Scale: 300/min, 600/hour, 6,000/day

Available endpoints

Person API

Retrieves contact data using identifiers like email, LinkedIn URL, name, company name, or domain. Returns location, email, phone, LinkedIn URL, and more. The Bulk Person API processes up to 100 contacts per request.

Company API

Retrieves firmographic data for a company based on its domain or name β€” industry, employee count, location, revenue, and more. The Bulk Company API handles multiple domains or names in a single request.

Prospecting API

Queries Lusha's database using filters like job title, seniority, location, and industry to generate contact or company lists aligned with your ICP. The process has three stages: select filters, run the search, then enrich the results. See the Prospecting API documentation for all available filters.

Lookalike API

Uses machine learning to find contacts and companies that mirror your best-performing customers. Contact Lookalikes match by role, seniority, and career trajectory; Company Lookalikes match by industry, headcount, revenue, and firmographic profile. See the Lookalike API documentation.

Signals API

Enriches contacts and companies with timely sales intelligence like job moves, promotions, and company growth signals. Useful for triggering outreach at moments of change. See the Signals API documentation.

Credit Usage API

Returns current credit consumption by type. Rate limit: 5 requests per minute.

Credit consumption

Credits are charged based on two factors: the data points revealed and the number of API results returned.

Data points (per reveal):

Data point type

Credit cost

Email

1 credit

Phone number

5 credits

Company info

1 credit

Request type:

Request type

Results returned

Credit cost

Single request

1 contact/company

1 credit per result

Bulk request

Up to 25 results

1 credit per 1–25 results

Example: revealing an email and phone for one contact costs 7 credits total (5 for phone + 1 for email + 1 for the request).

Signals credits:

  • Growth Surge in Hiring: 1 credit per company

  • Growth in Headcount: 1 credit per company

  • Job Change: 1 credit per contact

Key rules: A minimum of 1 credit applies per request even if no data is returned. Maximum 100 contacts or companies per request. Each contact's data point is only charged once β€” re-querying the same contact won't incur additional charges for already-revealed data.

Managing API key credit limits

You can set monthly credit limits per API key to control consumption per workflow (e.g. Zapier, Make, or internal tools).

  1. Go to API β†’ Manage API keys.

  2. Click the edit (pencil) icon or Set limit in the Credit usage column.

  3. In the Edit Key panel, toggle on the limit and enter the maximum credits allowed per month.

  4. Click Continue.

To remove a limit, click the pencil icon and select Remove in the side panel.

πŸ’‘ Note: Only Admins can set or edit credit limits. The sum of all individual API key limits cannot exceed your total account credit allowance. Limits reset automatically at the start of each billing cycle.

Error handling

Lusha's API uses standard HTTP response codes. See the full list in the API documentation.

Did this answer your question?