Company Signals API - Funding, M&A, Layoffs, Hiring Data
Under maintenancePricing
$20.00 / 1,000 results
Company Signals API - Funding, M&A, Layoffs, Hiring Data
Under maintenancePull company trigger events by date, company, industry, location and deal size: startup funding and venture rounds, mergers, acquisitions and divestments, layoffs and job cuts, business expansion and major hiring, C-suite changes, security breaches and company news. Bring your own API key.
Pricing
$20.00 / 1,000 results
Rating
0.0
(0)
Developer
Nabeel Hassan
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
12 days ago
Last modified
Categories
Share
Pull company trigger events as structured rows: startup funding and venture capital rounds, mergers, acquisitions and divestments, layoffs and job cuts, business expansion and major hiring, C-suite and executive changes, data and security breaches, and curated company news. Seven signal families, one dataset, one set of leading columns.
What this actor does
- Collects seven signal families into one table. Funding, mergers, layoffs, expansion, executive changes, breaches and news each have their own endpoint and their own record shape, and every one of them is flattened here to the same leading columns: signal type, date, company name, company domain, location, amount, currency, people count, headline and source URL.
- Filters on the server with the provider's own vocabularies. Industry, company type, funding round, deal status, deal type, layoff type, layoff reason, expansion type, executive title category and incident type are all exact-match lists, and they are offered here exactly as the provider publishes them, so a filter you set actually narrows the query instead of quietly matching nothing.
- Works around the lack of pagination. This API has no cursor and no page parameter: one request returns at most the records-per-request limit for the filter it was given. Set a days-per-request window and the actor slices your date range into windows and walks them newest first, which is how a run pulls far more than a single request could.
- Handles the daily incremental pull properly. Filter on last modified rather than announced date and each run picks up records that were created or changed since the last one, including late additions to older events.
- Pins both sides of a deal. Merger filters can be applied to the acquiring, the acquired or the selling company, and a counterparty name or domain narrows to deals between two specific companies.
- Carries on when a plan does not cover a signal. A signal your subscription excludes is skipped with a warning rather than failing the run and losing the signals it does cover.
- Never charges twice for the same signal. Overlapping date windows and companies matching more than one filter are de-duplicated before the charge, not after.
Input
| Field | What it does |
|---|---|
signalTypes | Which of the seven signal families to pull. |
startDate, endDate, exactDate | The date range, or a single date. |
dateType | Filter on the announced date or on the last modified date. |
windowDays | Split the range into windows and make one request per window. |
companyName, companyDomain, companyTicker | Which company to track. |
companyIndustry, companyType, companyLocation | Firmographic filters. |
mnaCompanyRole | Apply the company filters to the acquiring, acquired or selling side. |
counterpartyCompanyName, counterpartyCompanyDomain | Pin the other side of a deal. |
mnaStatus, mnaType | Deal stage and deal structure. |
fundingRound, investor, valuation, dealAmount, currency | Funding filters. |
layoffType, layoffReason | Layoff filters. |
expansionType, investment, jobs | Expansion filters. |
executiveName, executiveTitle, executiveTitleCategory, executiveChangeReason | Executive change filters. |
incidentType, peopleImpacted | Breach filters. |
eventLocation | Where the event happened, not where the company is based. |
newsCompanyDomains, newsTriggerCodes | Which companies and triggers the news signal watches. |
recordsPerRequest, requestDelayMs | Request size and pacing. |
maxResults | Hard cap on rows, and therefore on spend and run time. |
apiKey | Your own API key. Stored as a secret. |
Example output
{"signalType": "funding","id": "a1b2c3d4","date": "2026-07-14","companyName": "Example Labs","companyDomain": "examplelabs.com","companyIndustries": ["technology", "bio-technology"],"companyLocation": "Boston, Massachusetts, United States","companyType": "Private","companyTicker": null,"amount": 42000000,"currency": "USD","peopleCount": null,"fundingRound": "Series B","investors": "Acme Ventures, Northwind Capital","leadInvestors": "Acme Ventures","valuation": 310000000,"title": "Example Labs raises 42 million dollars in Series B","url": "https://example.com/news/example-labs-series-b","lastModified": "2026-07-15","raw": { }}
Frequently asked questions
What data does the Company Signals API return?
Each signal returns the event date, the company with its name, domain, industries, headquarters location, company type, ticker and stock exchange, the event location broken into country, state and city, the headline and the source URL, and the date the record was last modified. On top of that each family carries its own fields: funding adds the round, the investors and lead investors, the deal amount, the valuation and the currency; mergers add the acquiring, acquired and selling companies with the deal type, deal status and deal amount; layoffs add the number and percentage of staff, the layoff type, the reason, the business division and whether the source was a WARN filing or the press; expansion adds the expansion type, the investment and the jobs created; executive changes add the executive name, title, title category, reason and effective date; breaches add the incident type, the people impacted, the notice date and any third party involved; and news adds the publisher, the description, the trigger names and codes, and related coverage.
Do I need my own API key?
Yes. This actor does not include data access. You use your own API key from Intellizence, which is the provider whose company signals API this actor calls, requested from them directly. Your own plan, credit balance and terms apply. Paste the key into the apiKey field, where it is stored as an Apify secret and sent in a request header rather than a URL parameter, so it never appears in a log line or a redirect.
How do I pull more than one request's worth of signals?
Set windowDays. The API has no pagination, so one request returns at most recordsPerRequest records for the filter it was given, and the documented way to reach more is to narrow the filter. Setting a window of, say, 7 days over a one year range turns that into 53 requests, each covering a week, walked newest first so a run stopped early still has the most recent signals. Without a window the whole range goes out as a single request.
How do I run this daily without re-pulling everything?
Set dateType to last modified and give a start date of yesterday. The provider then returns records created or changed in that window rather than events announced in it, which is what catches a record added three days late for an event announced last week. Announced date is the right choice for analysis of a fixed historical period; last modified is the right choice for a feed.
How do I track acquisitions by a specific company?
Set the company domain and leave mnaCompanyRole on acquiring to get the deals that company made. Switch it to acquired to get the deals where it was the target, or to selling for divestments it sold out of. To pin both ends of a deal at once, add counterpartyCompanyName or counterpartyCompanyDomain.
Can I collect several signals in one run?
Yes, and that is the normal way to use this. Select as many families as you want in signalTypes and they all land in the same dataset with the same leading columns, so a single table can hold this week's funding rounds, layoffs and executive changes and be sorted by date or filtered by company. A family your plan does not cover is skipped with a warning and the rest still run.
Which industries and deal types can I filter on?
The provider publishes exact-match lists and this actor offers them verbatim: 55 industries, 5 company types, 21 funding rounds, 13 deal statuses, 11 deal types, 8 layoff types, 29 layoff reasons, 23 expansion types, 16 executive title categories, 8 change reasons, 8 incident types and 10 currencies. Because they are exact matches, a value outside a list matches nothing rather than matching loosely, which is why they appear as dropdowns rather than free text.
How far back does the data go?
The datasets begin at 2020-01-01. How much of that history your own key can reach depends on your subscription, and a request for a range outside it comes back as a subscription error, which this actor reports with that reason rather than as a generic failure.
How much does a run cost?
Pricing is pay per result: you are charged for each signal returned to the dataset, and never for duplicates across overlapping date windows. Apify platform usage is included in the per-result price. Your own API provider's credits are separate and billed by them, and the run log reports how many of them a run consumed.
Keyword map
company signals API, trigger events API, sales trigger data, startup funding API, venture capital deals data, funding rounds dataset, mergers and acquisitions API, M&A deal data, layoffs API, layoff tracker data, WARN notice data, business expansion signals, hiring signals API, C-suite changes API, executive movement data, leadership change tracking, data breach API, security incident dataset, company news API, buying intent signals, account intelligence, CRM signal enrichment