Company Signals (POST /v3/companies/signals) — linkedinActivityIntent signal type only; other signal types (headcount change, hiring surge, website traffic, IT spend, news categories) exist per the request schema but their response shapes are undocumented and not yet catalogued
A Lusha dataset with 25 fields. View the Lusha profile.
Product details
| Match keys | id |
|---|---|
| Geo coverage | Global |
| Refresh cadence | On-demand |
| Lifecycle | Active |
| Pricing model | Per-result |
| Last verified | 2026-08-16 |
Company Signals (POST /v3/companies/signals) — linkedinActivityIntent signal type only; other signal types (headcount change, hiring surge, website traffic, IT spend, news categories) exist per the request schema but their response shapes are undocumented and not yet catalogued fields
| Field | API name | Category | Type | Fill rate | Description |
|---|---|---|---|---|---|
| Company Name | companyName | String | - | Company name. | |
| Full Name | fullName | String | - | Full name (or full display name) of a person, contact, executive, officer, or social-media account. Entity-differentiated: Contact, Executive, Officer/Director, Person, Social Profile, Social Post (tagged account). | |
| Activity Publication Date | activityPublicationDate | Date (String) | - | Date the LinkedIn post was published. | |
| Company Name | name | String | - | Company name. | |
| Activity Companies Mentioned Object | companiesMentioned | Array of Objects | - | PARENT: companies mentioned/tagged in this activity post. | |
| LinkedIn URL | linkedinUrl | URL (String) | - | URL of the person's or company's LinkedIn profile. | |
| Lusha Company ID | id | String | - | Lusha's internal unique global identifier for the organization. | |
| Activity Shares Count | activityShares | Integer | - | Number of shares of the LinkedIn post. | |
| Activity Comments Count | activityComments | Integer | - | Number of comments on the LinkedIn post. | |
| Activity Type | activityType | String | - | The type of LinkedIn activity (e.g. post). | |
| Company Primary Domain | domain | String | - | The bare domain of the company's website (e.g. "apollo.io"), distinct from the full website URL. | |
| LinkedIn URL | linkedinUrl | URL (String) | - | URL of the person's or company's LinkedIn profile. | |
| Lusha Company ID | id | String | - | Lusha's internal unique global identifier for the organization. | |
| Lusha Company ID | companyId | Integer | - | Lusha's internal unique global identifier for the organization. | |
| Activity Intent Topic | topic | String | - | The specific Bombora intent topic detected in this activity (e.g. Cloud Security). | |
| Activity Intent Topics Object | intentTopics | Array of Objects | - | PARENT: detected Bombora intent topics and their category for this activity. | |
| Activity Intent Topic Category | category | String | - | The category of the detected intent topic (e.g. Technology). | |
| Activity Signal Category | signalCategory | String | - | Classification of the LinkedIn post (e.g. Technology or Stack Discussion). | |
| Activity Contacts Mentioned Object | contactsMentioned | Array of Objects | - | PARENT: people mentioned/tagged in this activity post. Lusha's endpoint reference does not expand this array's item schema (unlike companiesMentioned and author, which are documented) — shape unconfirmed, flagged for… | |
| Activity Likes Count | activityLikes | Integer | - | Number of likes on the LinkedIn post. | |
| Activity AI Summary | activitySummary | String | - | AI-generated summary of the LinkedIn post; never contains the raw post text. | |
| Activity Author Object | author | Object | - | PARENT: a person referenced in a LinkedIn activity intent post (author or mention). | |
| Activity URL | activityUrl | URL (String) | - | URL of the source LinkedIn post. | |
| Activity Author Contact ID | id | String | - | Lusha contact ID of the post's author, or null if the person couldn't be resolved to a Lusha record. Exact ID format (legacy numeric vs encrypted token) not specified in the endpoint documentation. | |
| Company LinkedIn Activity Intent Signal Events Object | linkedinActivityIntent | Array of Objects | - | PARENT: array of detected LinkedIn post/activity events showing buyer-intent signals for this company. This is the only company signal type with a fully documented response shape; other signal types (headcount change… |
More from Lusha
- Contacts Enrichment (POST /v3/contacts/enrich)
- Prospecting Contacts (POST /v3/contacts/prospecting)
- Contact Signals (POST /v3/contacts/signals)
- Companies Enrichment (POST /v3/companies/enrich)
- Contact Lookalikes (POST /v3/contacts/lookalike)
- Company Lookalikes (POST /v3/companies/lookalike)
- Prospecting Companies (POST /v3/companies/prospecting)
Company Signals (POST /v3/companies/signals) — linkedinActivityIntent signal type only; other signal types (headcount change, hiring surge, website traffic, IT spend, news categories) exist per the request schema but their response shapes are undocumented and not yet catalogued FAQ
What fields are in Company Signals (POST /v3/companies/signals) — linkedinActivityIntent signal type only; other signal types (headcount change, hiring surge, website traffic, IT spend, news categories) exist per the request schema but their response shapes are undocumented and not yet catalogued?
Company Signals (POST /v3/companies/signals) — linkedinActivityIntent signal type only; other signal types (headcount change, hiring surge, website traffic, IT spend, news categories) exist per the request schema but their response shapes are undocumented and not yet catalogued from Lusha has 25 fields, including Company Name, Full Name and Activity Publication Date.
What do I need to match against Company Signals (POST /v3/companies/signals) — linkedinActivityIntent signal type only; other signal types (headcount change, hiring surge, website traffic, IT spend, news categories) exist per the request schema but their response shapes are undocumented and not yet catalogued?
Company Signals (POST /v3/companies/signals) — linkedinActivityIntent signal type only; other signal types (headcount change, hiring surge, website traffic, IT spend, news categories) exist per the request schema but their response shapes are undocumented and not yet catalogued matches on id.
How is Company Signals (POST /v3/companies/signals) — linkedinActivityIntent signal type only; other signal types (headcount change, hiring surge, website traffic, IT spend, news categories) exist per the request schema but their response shapes are undocumented and not yet catalogued priced?
Per-result. Request a quote or a sample on SpringDB.