How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Lusha Signals API

Real-world activity data for contacts and companies — promotions and job changes on the contact side; headcount movement, hiring surges, web traffic, IT spend, news classes and LinkedIn activity intent on the company side — as raw dated events or as a single 0-1 momentum score per entity.

Lusha Signals API is one of 19 APIs that Lusha publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Signals and Intent. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 13 operations across 13 paths, and defines 44 schemas. It is described by OpenAPI 3.2.0.

Requests are made against a single base URL, https://api.lusha.com.

13 operations 13 paths 44 schemas 5 GET8 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
Base URL
https://api.lusha.com
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Lusha Signals API declares 1 security scheme for authenticating requests. An API key is passed in the header as api_key (ApiKeyAuth). By default, every request must be authenticated.

  • ApiKeyAuth — Your Lusha API key. You can find this in your Lusha dashboard under API settings. Include this key in the apikey header for all requests.

Paths & Operations 13

Across 13 paths, the API surfaces 13 operations — 5 GET, 8 POST. Each is listed below with its method, path, parameters, and response codes.

Signals 13

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 si…

POST
/v3/contacts/signals
Contact Signals
getContactSignals body → 200400401402403429
POST
/v3/companies/signals
Company Signals
getCompanySignals body → 200400401402403429
GET
/v3/contacts/signals/types
Get Contact Signal Types
getContactSignalTypes → 200401403
GET
/v3/companies/signals/types
Get Company Signal Types
getCompanySignalTypes → 200401403
GET
/v3/companies/signals/filters
Get Company Signal Filters (Discovery)
getCompanySignalFilters → 200401403
GET
/v3/companies/signals/filters/{filterType}
Get Company Signal Filter Values
getCompanySignalFilterValues 2 params → 200400401403
POST
/v3/companies/signal-score
Score Companies by Signal Activity
getCompanySignalScores body → 200400401402403429
POST
/v3/contacts/signal-score
Score Contacts by Signal Activity
getContactSignalScores body → 200400401402403429502
GET
/api/signals/filters/{objectType}
Get Signal Options
getSignalOptions 1 param → 200401403
POST
/api/signals/contacts
Get Contact Signals by IDs
getContactSignalsById body → 200400401403429
POST
/api/signals/contacts/search
Search Contact Signals
searchContactSignals body → 200400401403429
POST
/api/signals/companies
Get Company Signals by IDs
getCompanySignalsById body → 200400401403429
POST
/api/signals/companies/search
Search Company Signals
searchCompanySignals body → 200400401403429

Schemas 44

The contract defines 44 schemas that model the data the API accepts and returns. The most detailed are CompanySignalData (25 properties), LinkedinActivityIntentItem (13 properties), CompanyNewsSignal (11 properties), ContactSignal (10 properties). Each schema is shown below with its type and property counts.

V3SignalScoreContactsResponse
object
3 properties
LinkedinActivityIntentCompanyMention
object
A company referenced in a LinkedIn activity intent post.
3 properties
V3SignalScoreContactsRequest
object
1 property 1 required
V3SignalScoreCompaniesRequest
object
1 property 1 required
LinkedinActivityIntentTopic
object
2 properties
LinkedinActivityIntentItem
object
13 properties
V3CompanySignalsRequest
object
6 properties 2 required
V3ContactSignalsResponse
object
5 properties
ErrorResponse
object
3 properties 2 required
CompanySignalTypesResponse
object
1 property
V3SignalScoreCompaniesResponse
object
3 properties
V3CompanySignalsResponse
object
5 properties
V3SignalScoreCompanyItem
object
Must contain exactly one of id, domain, name, or email.
5 properties
V3ItemError
object
Per-item error in a batch response
2 properties
TableWrite
object
Added to a Prospecting, Enrich, Signals, or Lookalike response when tableId is passed on the request. The primary response is unaffected even if the table writ…
8 properties
ContactSignalTypesResponse
object
1 property
V3SignalScoreCompanyResult
object
A scored entry, or an error entry with NOTFOUND / NOSCORE instead of the score fields.
8 properties
FilterValuesResponse
object
1 property
V3SignalScoreContactResult
object
A scored entry, or an error entry with NOTFOUND / NOSCORE instead of the score fields.
8 properties
FilterTypesDiscoveryResponse
object
1 property
V3SignalScoreContactCompanyRef
object
Company the contact was scored at.
3 properties
V3ContactSignalsRequest
object
5 properties 2 required
V3SignalScoreContactItem
object
Must contain id, linkedinUrl, email, or firstName + lastName + (companyName | companyDomain).
8 properties
LinkedinActivityIntentPerson
object
A person referenced in a LinkedIn activity intent post (author or mention).
3 properties
V3Billing
object
Credit usage summary for a V3 API request
2 properties
ContactSignalsSearchResponse
object
4 properties
CompanyHeadcountChangeSignal
object
8 properties
CompanySignalFiltersInclude
object
Optional sub-filters to narrow results within a signal type. - Multi-value filters use OR logic - Filter values are not case-sensitive - state without country…
3 properties
CompanySignalData
object
25 properties
ContactSignalData
object
3 properties
CompanySurgeInHiringSignal
object
8 properties
CompanySignalsSearchRequest
object
5 properties 2 required
CompanySignalsByIdRequest
object
5 properties 2 required
CompanySurgeInHiringByDepartmentSignal
object
9 properties
SignalFilterLocation
object
Location filter for hiring signals. country is required; state is optional.
2 properties 1 required
CompanySurgeInHiringByLocationSignal
object
10 properties
CompanyNewsSignal
object
11 properties
ContactSignalsByIdRequest
object
4 properties 2 required
ContactSignalsSearchRequest
object
4 properties 2 required
CompanySignalsByIdResponse
object
4 properties
CompanyWebsiteTrafficSignal
object
8 properties
ContactSignalsByIdResponse
object
4 properties
CompanyItSpendSignal
object
7 properties
ContactSignal
object
10 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lusha-signals-api-openapi.yml Raw ↑

Other APIs Lusha publishes across the network.

Lusha Search API
Lusha Enrich API
Lusha Search & Enrich API
Lusha Prospecting API
Lusha Lookalikes API
Lusha Buying Group API
Lusha Website Visitors API
Lusha Filters API
Lusha Contacts Tables API
Lusha Companies Tables API
Lusha Webhooks API
Lusha Account API
Where this information came from

This is an independent, third-party profile of Lusha Signals API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.