Lusha API Documentation

Copy

• Copy for LLM

  Copy page as Markdown for LLMs
• View as Markdown

  Open this page as Markdown
• Open in ChatGPT

  Get insights from ChatGPT
• Open in Claude

  Get insights from Claude
• Connect to Cursor

  Install MCP server on Cursor
• Connect to VS Code

  Install MCP server on VS Code

Search APIs: Find contacts or companies using known identifiers.

Look up contacts by id, linkedinUrl, email, or firstName + lastName + companyName/companyDomain. Look up companies by id, name, or domain.

Returns a non-PII preview of each profile with a has field listing available data points and a canReveal field showing what can be unlocked via Enrich.

Billing: Charged per successful result via the api_search action.

Search & Enrich APIs: Find and retrieve full contact or company data in a single call.

Combines Search and Enrich into one request. Provide identifiers and control what gets revealed via the reveal field.

Billing: Two charges apply — one for the search (api_search) and one per revealed field.

Prospecting APIs: Filter-based search for contacts and companies.

Use prospecting to find new records that match your Ideal Customer Profile (ICP). Apply rich filters across:

• Contact attributes: title, seniority, location, signals
• Company attributes: size, revenue, industry, technologies, intent

Results are paginated: up to 1,000 pages x 50 results = 50,000 results per query.

Billing: Uses the capture/charge model with api_search actions. Signal charges apply additionally.

Lookalike APIs: Use AI-powered recommendations to discover contacts and companies similar to your best existing customers. The Contact Lookalikes and Company Lookalikes endpoints return paginated results you can pipe directly into Enrich for full data.

Real-world activity data for contacts and companies.

Signals are available as standalone endpoints or as an optional signals filter on Search and Prospecting endpoints.

Contact signal types: promotion, companyChange, allSignals

Company signal types: headcountIncrease1m/3m/6m/12m, headcountDecrease1m/3m/6m/12m, surgeInHiring, surgeInHiringByDepartment, surgeInHiringByLocation, websiteTrafficIncrease, websiteTrafficDecrease, itSpendIncrease, itSpendDecrease, riskNews, commercialActivityNews, corporateStrategyNews, financialEventsNews, peopleNews, marketIntelligenceNews, productActivityNews, allSignals

Credits are charged per matched signal per result via showSignalsContact or showSignalsCompany.

Filter APIs: Retrieve available filter values for prospecting.

Use the discovery endpoints to list all available filter types, then fetch valid values for a specific filter type before building a prospecting request.

Contact filter types: departments, seniority, existingDataPoints, countries, locations

Company filter types: names, sizes, revenues, locations, sics, naics, industriesLabels, intentTopics, technologies

Account API: Retrieve account usage, credit balance, rate limits, plan details, and pricing.

Use this endpoint to monitor consumption and understand the credit cost of each action type in the public API flow.

Rate limit: 5 requests per minute.

Subscribe to real-time notifications when contacts change jobs or companies experience key business events.

Webhooks deliver HTTP POST requests to your endpoints when signals occur - from promotions and job changes to company growth.

For a full list of available signals, refer to Signal Options.

Key Features:

• Real-time contact & company signal notifications
• Bulk subscription management (up to 25 items per request)
• Secure delivery with HMAC-SHA256 signatures
• Delivery monitoring with audit logs

Available Endpoints:

Webhook Delivery Acknowledgment: When receiving webhook deliveries (POST requests), your endpoint must acknowledge with a specific response format. See the Create Subscription endpoint for the required acknowledgment structure.

const crypto = require('crypto');

function verifySignature(payload, signature, timestamp, secret) {
  const signedPayload = `${timestamp}.${JSON.stringify(payload)}`;
  const expectedSignature = crypto
    .createHmac('sha256', secret)
    .update(signedPayload)
    .digest('hex');
  
  return crypto.timingSafeEqual(
    Buffer.from(signature),
    Buffer.from(expectedSignature)
  );
}

{
  "statusCode": 400,
  "message": "Validation failed",
  "errors": ["entityType must be one of: contact, company"]
}