Lusha

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.

GitHub OpenAPI

Operations 13

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

POST /v3/contacts/signals Get job changes and promotions for contacts · Contact Signals #
Ask an LLM
“Which of my contacts recently got promoted or changed companies?”
“Can I limit contact signal results to events after a date?”
Tell an agent
Get {signalTypes} signals for contacts {ids}.
Show {signalTypes} events for contacts {ids} since {startDate}.
POST /v3/companies/signals Get hiring, news and growth signals for companies · Company Signals #
Ask an LLM
“Which of my target accounts are hiring or in the news?”
“Can I see headcount changes and IT spend signals for a list of companies?”
Tell an agent
Get {signalTypes} signals for companies {ids}.
Show {signalTypes} for companies {ids} since {startDate}, at most {maxResultsPerSignal} per signal.
GET /v3/contacts/signals/types List contact signal types · Get Contact Signal Types #
Ask an LLM
“What kinds of signals does Lusha track for people?”
“Which contact signal type names can I request?”
Tell an agent
List the supported contact signal types.
Show every signal type available for contacts.
GET /v3/companies/signals/types List company signal types · Get Company Signal Types #
Ask an LLM
“What kinds of signals are tracked for companies?”
“Which company signal type names can I request?”
Tell an agent
List the supported company signal types.
Show every signal type available for companies.
GET /v3/companies/signals/filters List company signal filter types · Get Company Signal Filters (Discovery) #
Ask an LLM
“What filters can I apply to company signals, like news event type?”
“Which company signal filters need a search query?”
Tell an agent
List the filter types for company signals.
Show which company signal filters require a query.
GET /v3/companies/signals/filters/{filterType} Get values for one company signal filter · Get Company Signal Filter Values #
Ask an LLM
“What news event types can I filter company signals by?”
“How do I find hiring location values for a company signal filter?”
Tell an agent
Show the valid values for company signal filter {filterType}.
Search company signal filter {filterType} for {query}.
POST /v3/companies/signal-score Score companies by buying signal activity · Score Companies by Signal Activity #
Ask an LLM
“Which of my accounts show the most active buying signals?”
“What does a company signal score between 0 and 1 mean?”
Tell an agent
Score these companies by signal activity: {companies}.
Rank accounts {companies} by their buying signal score.
POST /v3/contacts/signal-score Score contacts by buying signal activity · Score Contacts by Signal Activity #
Ask an LLM
“Which of my contacts have the strongest buying signals right now?”
“Can I get a signal score for up to 100 people at once?”
Tell an agent
Score these contacts by signal activity: {contacts}.
Rank people {contacts} by their buying signal score.
GET /api/signals/filters/{objectType} List signal options for contacts or companies (legacy) · Get Signal Options #
Ask an LLM
“Which signal options can I use when enriching with the older signals endpoints?”
“What legacy signal filters exist for contact versus company objects?”
Tell an agent
List the legacy signal options for {objectType}.
Show which signals I can filter {objectType} enrichment by.
POST /api/signals/contacts Get signals for contact IDs (legacy) · Get Contact Signals by IDs #
Ask an LLM
“How do I pull signals for contact IDs with the older signals API?”
“Does the legacy contact signals call have a default lookback period?”
Tell an agent
Using the legacy endpoint, get {signals} signals for contact IDs {contactIds}.
Fetch legacy {signals} signals for contact IDs {contactIds} since {startDate}.
POST /api/signals/contacts/search Look up people and their signals together · Search Contact Signals #
Ask an LLM
“Can I get signals for a person using just their LinkedIn URL or email?”
“How do I find a contact by name and company and see their job changes?”
Tell an agent
Find contacts {contacts} and return their {signals} signals.
Search signals for people {contacts} with {signals} since {startDate}.
POST /api/signals/companies Get signals for company IDs (legacy) · Get Company Signals by IDs #
Ask an LLM
“How do I pull signals for company IDs with the older signals API?”
“Can I filter legacy company signals by department or location?”
Tell an agent
Using the legacy endpoint, get {signals} signals for company IDs {companyIds}.
Fetch legacy {signals} signals for company IDs {companyIds} with filters {filters}.
POST /api/signals/companies/search Look up companies and their signals together · Search Company Signals #
Ask an LLM
“Can I get signals for a company using only its domain or name?”
“How do I look up an account and see its latest news in one call?”
Tell an agent
Find companies {companies} and return their {signals} signals.
Search signals for accounts {companies} with {signals} since {startDate}.

Documentation

📖
Documentation
https://docs.lusha.com/apis/openapi/signals

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/lusha/refs/heads/main/openapi/lusha-signals-api-openapi.yml

Other Resources

🔗
Overlay
https://raw.githubusercontent.com/api-evangelist/lusha/refs/heads/main/overlays/lusha-signals-overlay.yaml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/lusha:lusha-signals-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

lusha-signals-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Lusha Signals API
  version: ''
  contact:
    name: Lusha Support
    url: https://api.lusha.com
    email: support@lusha.com
  license:
    name: Proprietary
    url: https://lusha.com/legal/terms
  termsOfService: https://lusha.com/legal/terms
  x-logo:
    url: https://www.lusha.com/logo.png
  x-privacy-policy:
    name: Privacy Policy
    url: https://lusha.com/legal/privacy-notice/
  description: 'Operations tagged Signals across 2 of this provider''s published API definitions: lusha-openapi.yml, lusha-v2-openapi.yaml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api.lusha.com
  description: Production server
security:
- ApiKeyAuth: []
tags:


# --- truncated at 32 KB (85 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/lusha/refs/heads/main/openapi/lusha-signals-api-openapi.yml