SpringDB Data Exchange Search data fieldsData vendorsAI Data ConsultantList your data

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 keysid
Geo coverageGlobal
Refresh cadenceOn-demand
LifecycleActive
Pricing modelPer-result
Last verified2026-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

FieldAPI nameCategoryTypeFill rateDescription
Company NamecompanyNameString-Company name.
Full NamefullNameString-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 DateactivityPublicationDateDate (String)-Date the LinkedIn post was published.
Company NamenameString-Company name.
Activity Companies Mentioned ObjectcompaniesMentionedArray of Objects-PARENT: companies mentioned/tagged in this activity post.
LinkedIn URLlinkedinUrlURL (String)-URL of the person's or company's LinkedIn profile.
Lusha Company IDidString-Lusha's internal unique global identifier for the organization.
Activity Shares CountactivitySharesInteger-Number of shares of the LinkedIn post.
Activity Comments CountactivityCommentsInteger-Number of comments on the LinkedIn post.
Activity TypeactivityTypeString-The type of LinkedIn activity (e.g. post).
Company Primary DomaindomainString-The bare domain of the company's website (e.g. "apollo.io"), distinct from the full website URL.
LinkedIn URLlinkedinUrlURL (String)-URL of the person's or company's LinkedIn profile.
Lusha Company IDidString-Lusha's internal unique global identifier for the organization.
Lusha Company IDcompanyIdInteger-Lusha's internal unique global identifier for the organization.
Activity Intent TopictopicString-The specific Bombora intent topic detected in this activity (e.g. Cloud Security).
Activity Intent Topics ObjectintentTopicsArray of Objects-PARENT: detected Bombora intent topics and their category for this activity.
Activity Intent Topic CategorycategoryString-The category of the detected intent topic (e.g. Technology).
Activity Signal CategorysignalCategoryString-Classification of the LinkedIn post (e.g. Technology or Stack Discussion).
Activity Contacts Mentioned ObjectcontactsMentionedArray 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 CountactivityLikesInteger-Number of likes on the LinkedIn post.
Activity AI SummaryactivitySummaryString-AI-generated summary of the LinkedIn post; never contains the raw post text.
Activity Author ObjectauthorObject-PARENT: a person referenced in a LinkedIn activity intent post (author or mention).
Activity URLactivityUrlURL (String)-URL of the source LinkedIn post.
Activity Author Contact IDidString-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 ObjectlinkedinActivityIntentArray 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

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.