Available filters for contact searches
Lusha API Documentation
Lusha provides a RESTful API that allows you to query a comprehensive dataset of business profiles and company information. It is designed for teams building prospecting, enrichment, automation, and analytics workflows that require accurate, continuously updated business data. The API supports both real-time and bulk use cases and is suitable for production environments. Use the Lusha API to search for new prospects, enrich existing records, react to real-world changes, and expand coverage using lookalike recommendations.
All API requests should be made over HTTPS (SSL), and the response bodies are delivered in JSON format.
Person
https://api.lusha.com/v2/person
▶ Common Use Cases
- • Form enrichment
- • CRM completion
- • Outbound personalization
Company
https://api.lusha.com/v2/company
▶ Common Use Cases
- • Account enrichment
- • Routing, scoring, territory logic
- • Market analysis & segmentation
Signals
https://api.lusha.com/v2/signals
▶ Common Use Cases
- • Job change tracking
- • Company updates signals
- • News event alerts
Lookalikes
https://api.lusha.com/v2/recommendations
▶ Common Use Cases
- • Market expansion
- • Similar account discovery
- • Prospect recommendations
Filters
Account
Data Source and Privacy
Please note that Lusha is a search platform, meaning the data provided is not created or directly managed by us. Instead, it is retrieved from publicly available sources and through contributions from trusted business partners.
For more information on how we collect, use, and handle business profiles, please refer to our Privacy Policy.
API keys are required for all API and MCP requests and are tied to your Lusha account and plan. To access the Lusha API, you must authenticate your requests using your API key. This key is unique to your account and is used to identify your usage of the API. How to Authenticate:
When making an API call, include your API key in the api_key header of the request.
You can generate and retrieve your API key here. API keys should be stored securely and used only in server-side environments.
Lusha API enforces rate limiting to ensure fair usage and protect against excessive load.
- General Rate Limit: You can make up to 25 requests per second to each API endpoint
- Credit Usage API: Has a specific rate limit of 5 requests per minute
Note: Rate limits may vary based on your account type and subscription plan. If you're encountering rate limit issues frequently, please consult with your account manager or Lusha support team to discuss your specific needs.
Rate Limit Headers
To monitor your current rate limit status, check the HTTP response headers in your API calls:
| Header | Description |
|---|---|
x-rate-limit-daily | The total number of requests allowed per day under your current plan |
x-daily-requests-left | The number of requests remaining in your daily quota |
x-daily-usage | The number of requests you have made in the current daily period |
x-rate-limit-hourly | The total number of requests allowed per hour under your current plan |
x-hourly-requests-left | The number of requests remaining in your hourly quota |
x-hourly-usage | The number of requests you have made in the current hourly period |
x-rate-limit-minute | The total number of requests allowed per minute under your current plan |
x-minute-requests-left | The number of requests remaining in your current minute window |
x-minute-usage | The number of requests you have made in the current minute window |
Notes on API Rate Limiting
- If you exceed the rate limit, the API will return a 429 (Too Many Requests) error.
- To ensure a smooth experience, respect the rate limits defined by your subscription tier.
- Daily limits vary based on your billing plan — higher tiers have higher quotas.
- You can programmatically track your usage through these response headers:
X-RateLimit-Remaining-DailyX-RateLimit-Reset-Daily
- It is strongly recommended to implement logic that:
- Monitors these headers
- Pauses or retries requests accordingly
- Helps avoid hitting the limit and ensures reliable operation
Lusha API uses standard HTTP response codes to indicate the status of your request. These codes help you understand whether the request was successful or if there was an issue.
| Status Code | Name | Description |
|---|---|---|
| 200 | OK | Successful request |
| 400 | Bad Request | Badly formatted request |
| 401 | Unauthorized | The API key is invalid |
| 402 | Payment Required | Your account requires payment |
| 403 | Forbidden | Your account is not active. Please reach out to support at support@lusha.com for assistance |
| 403 | Forbidden | Your pricing version does not support requesting individual datapoints [revealEmails, revealPhones] |
| 404 | Not Found | The requested endpoint was not found |
| 412 | Precondition Failed | The request failed due to invalid syntax that was provided. Please make sure to send a full name field that contains a valid first & last name |
| 429 | Too Many Requests | You've reached your trial limit, please contact support for upgrade |
| 429 | Too Many Requests | Daily API quota limit exceeded. Limit X calls per day |
| 429 | Too Many Requests | Hourly API rate limit exceeded. Limit: X calls per hour. Reset in X seconds |
| 451 | Unavailable For Legal Reasons | We are unable to process this contact request due to our GDPR regulations |
| 499 | Client Closed Request | Request failed due to request timeout |
| 5XX | Server Error | There's a problem on Lusha's end |
Error Response Format
In case of an error, the response body will contain details about the error:
{
"error": {
"code": 400,
"message": "Invalid request parameters"
}
}Handling errors
Always ensure your API key is correct and valid
Pay attention to the specific error message and code to troubleshoot issues efficiently
Implement proper error handling and retry logic in your application
For 5XX errors, implement exponential backoff before retrying
Download OpenAPI description
Overview
Languages
Servers
Mock server
https://docs.lusha.com/_mock/apis/openapi/
Production server
https://api.lusha.com/
Enrichment
What is enrichment?:
Enrichment is the process of adding missing or updated data to existing contact or company records.
Use enrichment to:
- Complete CRM records
- Improve outbound accuracy and deliverability
- Keep records current as people and companies change
Enrichment can be performed in real time or in bulk, depending on the endpoint and use case.
Available enrichment APIs
Person enrichment:
- Search single contact - Enrich one contact at a time
- Search multiple contacts - Bulk enrich contacts
Company enrichment:
- Search a single company - Enrich one company at a time
- Search multiple companies - Bulk enrich companies
Operations
Prospecting - Search & Enrich
With Lusha's Prospecting API, you can query Lusha's extensive database based on specific criteria (such as job title, seniority, location, and more) to retrieve detailed contact and company information.
The Prospecting API is designed to help you generate new records (contacts or companies) for your CRM system, using filters that align with your Ideal Customer Profile (ICP).
This process involves three main steps:
Operations
Signals
With Lusha’s Signals API, you can enrich your contacts and companies with timely insights that highlight key account and prospect changes. Signals help you identify moments of opportunity - from job moves and promotions to company growth and new initiatives - so you can engage prospects and customers at exactly the right time. Easily integrate signal data into enrichment flows, CRM systems, or automation workflows to keep pipelines and customer records always up to date.
Operations
Lookalikes
Lusha's Lookalikes API helps you discover similar contacts and companies based on your existing data. Get AI-powered suggestions for new prospects that match your ideal customer profile.
Contact Lookalikes - Find similar contacts based on role, seniority, and industry patterns.
Company Lookalikes- Discover companies with similar firmographics and characteristics.
Operations
Account Management
Manage your account and monitor usage.
Use this endpoint to:
- Monitor credit usage
- Understand consumption patterns
- Align API usage with plan limits
- Support governance and production operations
Account-level insights are especially important for teams running Lusha at scale or across multiple systems.
Operations