This page is the technical entry point to the Lusha API. It introduces the core data types exposed by the API, the main access patterns, and the fundamentals required to authenticate and make a first request. Use this section to understand how the API is structured and confirm access before moving into specific capabilities.

The Lusha API exposes GTM data through a small set of core data types and access patterns.

• Contacts — contact profiles and identifiers
• Companies — firmographic and company-level attributes
• Signals — change-based events across contacts and companies
• Lookalikes — similarity-based recommendations for expansion

• Enrichment — add missing or updated data to existing records
• Search & prospecting — find contacts and companies using filters
• Automation — use enrichment and signals inside workflows

• Generate and manage API keys in the Lusha API Dashboard
• Store keys securely (for example, using environment variables)
• Never expose API keys in client-side code

When making an API call, include your API key in the api_key header of the request.

• Header: api_key
• Format: Bearer YOUR_API_KEY

• All responses are returned as structured JSON
• Common fields include email, phone, job title, company, and location
• Some fields may be missing depending on availability, permissions, or compliance rules

GET https://api.lusha.com/v2/person

• Send identifying fields such as firstName, lastName, company
• Parse the JSON response
• Locate returned fields such as email or phone when available

• Check HTTP status codes for every response
• Handle 4xx and 5xx errors explicitly
• Implement retry logic for rate limit responses (HTTP 429)

Detailed error formats and retry guidance are covered in Errors & handling.

• Default rate limit: 25 requests per second
• Some endpoints return paginated results
• Use pagination tokens to retrieve additional pages

See Rate limits for full details.

Once you've validated access, you can:

Start with Contacts and Companies enrichment endpoints to add missing data to your existing contacts and accounts.

→ Contact enrichment guide
→ Company enrichment guide

Start with Prospecting to build targeted tables, then add Signals for timing and triggers.

→ Prospecting guide
→ Signals guide

Add Lookalikes once you have clean seed data from your best customers or champions.

→ Recommendations guide

Explore the MCP (Model Context Protocol) integration for Claude and other AI agents.

→ MCP guide

Quick implementations for common platforms:

• Salesforce

  • Apex trigger on Lead creation → call Lusha API → update fields.
  • Flows for easy webhook API implementation.

• HubSpot

  • Workflow → custom webhook
  • Map response to HubSpot properties (YAML/JSON examples).

• Webhooks

  • Subscribe to events (e.g., data updates).
  • Verify signatures; Node.js/Express listener example.

• Bulk Enrichment

  • Python scripts to process CSV files
  • Submit bulk requests, poll for results, and write output to a database or file

• SDK Examples (Node.js, Python, Java)

  • Community wrappers: install, initialize, fetch data.
  • Raw HTTP equivalents for each example.

Deeper guidance for teams running Lusha at scale.

• Performance & Cost
  Batch requests, caching (Redis/in-memory), cost-aware enrichment patterns.

• Complex Queries
  Combine parameters for higher accuracy, client-side matching and deduplication.

• Security Best Practices
  Encrypt API keys, enforce least privilege, audit logging.

• Orchestration Workflows
  Terraform/CloudFormation snippets for AWS Lambda and API Gateway.

• Data Quality & Fallbacks
  Handle missing fields: fallback to alternative data sources, merge multiple enrichers.

• Schema & Data Modeling
  DB table structures (Postgres, MongoDB), indexing (email hash, domain), migration strategies.

• Compliance & Privacy
  GDPR/CCPA guidelines: retention policies, anonymization, privacy disclaimers.

• Custom Connectors
  Build for Workato, Zapier, Make: HTTP module config, auth, mapping, error patterns.

• Full API Doc: Complete endpoint docs with examples (cURL, Node.js, Python, Java).
• Common API questions: FAQs and clarifications.
• Changelog & Release Notes: Track new endpoints, parameter changes, deprecations.
• Help Center: Links to community-driven wrappers; installation and usage.

Explore the Postman Public Environment: Test out the API endpoints and see how the data is structured. You can access our public Postman workspace to experiment with live examples and understand the response formats - Access Lusha's Postman Workspace!