GET /v2/company to enrich a single company in real time. Provide a domain, company name, or Lusha company ID and receive firmographics, employee count, funding details, technologies, intent data, and optional company signals.
Endpoint
api_key request header.
Search requirements
You must provide at least one of the following:domain- the company’s web domain (recommended for highest match accuracy)company- the company namecompanyId- the Lusha company identifier
Signal sub-filters (
newsEventTypes, hiringByDepartments, hiringByLocations) are not supported on this endpoint. To filter signal results, use POST /bulk/company/v2 with the signalsFilters parameter instead.Query parameters
string
The domain name associated with the company. Example:
lusha.comstring
The name of the company. Example:
Lushastring
The unique Lusha company identifier. Example:
1234567890array
Signal types to retrieve for the company. Use
allSignals to receive all available signal types, or provide one or more specific values.Allowed values: allSignals, websiteTrafficIncrease, websiteTrafficDecrease, itSpendIncrease, itSpendDecrease, headcountIncrease1m, headcountDecrease1m, headcountIncrease3m, headcountDecrease3m, headcountIncrease6m, headcountDecrease6m, headcountIncrease12m, headcountDecrease12m, surgeInHiring, surgeInHiringByDepartment, surgeInHiringByLocation, riskNews, commercialActivityNews, corporateStrategyNews, financialEventsNews, peopleNews, marketIntelligenceNews, productActivityNewsstring
Start date for signal retrieval in
YYYY-MM-DD format. Defaults to 6 months ago if not specified. Example: 2025-03-01boolean
Set to
true to expand coverage by including partial company profiles when a full match is not available.Response fields
A successful200 response returns a data object with the following key fields:
Signal fields such as
riskNews, commercialActivityNews, surgeInHiring, websiteTrafficIncrease, and headcountIncrease1m are included in the response when the corresponding signal type is requested via the signals parameter.