# Intellizence API Documentation

**Welcome to the Intellizence API Documentation!**

This guide is designed to help developers and data teams seamlessly access and integrate curated business  signals from Intellizence into your applications, platforms, or workflows. The Intellizence APIs deliver near real-time signals as news and structured data covering key company events across sectors and business types. With Intellizence, you can enable smarter, data-driven decisions and power intelligent, responsive solutions.\
\
Ready to get started? [**Request your API key**](https://intellizence.com/api-trial/) and start building.\
Questions? [**Schedule a call**](https://intellizence.com/schedule-a-demo/) or email us at <sales@intellizence.com>.

**DATASET APIs:**

{% hint style="info" %}
The following **REST APIs**  provide  **access to structured, ongoing, and historical company signals.**

Designed for:

* **Prospect Discovery & Pipeline Generation**

  Identify high-intent, net-new target accounts.

* **Signal Monitoring Systems**

  Track company signals across target accounts and industries.

* **CRM & Internal System Enrichment**

  Enrich your CRM and internal dashboards with structured signals.

* **Market & Trend Analysis**

  Analyze historical data to uncover patterns and market trends.

* **Company Relationship Graphs & Entity Intelligence**

  Map strategic relationships across companies and ecosystems.

* **Automated Workflows**

  Trigger alerts and tasks based on company signals.

* **AI Agents, Co-Pilots & Intelligence Platforms**

  Power AI systems with structured, real-time signals.
  {% endhint %}

* [**Mergers & Acquisitions Signals API**](/signals-api/mergers-and-acquisitions)

* [**Startup Funding & Venture Capital (VC) Deal Signals API**](/signals-api/startup-funding-venture-capital-deals)

* [**Layoffs Signals API**](/signals-api/layoffs)

* [**Business Expansion and Major Hiring Signals API**](/signals-api/business-expansion-major-hiring)

* [**C-Suite Changes Signals API**](/signals-api/c-suite-changes)

* [**Data & Security Breaches Signals API**](/signals-api/data-security-breaches)

**Company News Signals API:**&#x20;

{% hint style="info" %}
The **REST APIs** deliver **100+ curated, real-time news signals** on target companies.

* **Sales Intelligence** – Opportunity discovery and timely engagement

* **Customer Intelligence** – Cross-sell, upsell, and churn risk monitoring

* **Vendor Risk Intelligence** – Supplier risk monitoring and exposure tracking

* **Competitor Intelligence** – Competitive tracking and market visibility

* **Partner Intelligence** – Ecosystem monitoring and opportunity insights
  {% endhint %}

* [**Company News Signals API**](/company-news-signal-api/search-signals-by-company-domain)

* [**Intellizence News Signals ( Trigger Codes)**](/company-news-signal-api/intellizence-signals-trigger-codes-reference)


# Intellizence Mergers & Acquisitions (M\&A) Signals API

This REST API provides continuous access to ongoing and historical Mergers & Acquisitions (M\&A) and divestment deal data from the Intellizence Mergers & Acquisitions Dataset.

{% hint style="info" %}
Best  suited for:

* Continuous monitoring of M\&A and divestment events
* Trigger alerts and automated workflows
* M\&A trends & analysis
* Company relationship graphs and entity intelligence
* Power AI agents and internal intelligence platforms<br>
  {% endhint %}

> **Ready to get started?** [**Request your API key**](https://intellizence.com/api-trial/) and start building.\
> **Questions?** [**Schedule a call**](https://intellizence.com/schedule-a-demo/) or email us at <sales@intellizence.com>.

\
**Security Notice:** Please keep the API Key secure. Do not share your API key in publicly accessible areas such as GitHub, client-side code, and so forth.

## Submit a request to get Mergers & Acquisitions (M\&A) data

> This REST API endpoint provides access to both ongoing and historical Mergers & Acquisitions (M\&A) and Divestment deal data from the Intellizence Mergers & Acquisitions Dataset. Data access is limited to records within your subscription’s entitled date range.\
> \
> Users can filter results using the following parameters:\
> \
> \`dateType\`, \`startDate\`, \`endDate\`, \`date\`,\
> \`acquiringCompanyName\`, \`acquiringCompanyDomain\`, \`acquiringCompanyIndustry\`, \`acquiringCompanyLocation\`, \`acquiringCompanyType\`, \`acquiringCompanyTicker\`,\
> \`acquiredCompanyName\`, \`acquiredCompanyDomain\`, \`acquiredCompanyIndustry\`, \`acquiredCompanyLocation\`, \`acquiredCompanyType\`, \`acquiredCompanyTicker\`,\
> \`sellingCompanyName\`, \`sellingCompanyDomain\`, \`sellingCompanyIndustry\`, \`sellingCompanyLocation\`, \`sellingCompanyType\`, \`sellingCompanyTicker\`,\
> \`dealAmount\`, \`currency\`, \`mnaStatus\`, and \`mnaType\`.\
> \
> Users can limit the number of records returned using the \`limit\` parameter. All parameters are optional.\
> \
> The API key must be passed in the HTTP header as \`x-api-key\`.

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Mergers & Acquisitions (M&A) Signals API","version":"1.0"},"servers":[{"url":"https://connect.intellizence.com"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","name":"x-api-key","in":"header"}},"schemas":{"dataset_mna_body":{"type":"object","properties":{"dateType":{"type":"string","description":"Choose the date type used to filter records.The default value is 'Announced'.To get the daily update of records created or modified, 'LAST-MODIFIED' is recommended.","enum":["ANNOUNCED","LAST-MODIFIED"]},"startDate":{"type":"string","description":"The start date(YYYY-MM-DD) from which M&A deals data is required. The Intellizence Mergers & Acquisitions Dataset contains data beginning from 2020-01-01. Access to historical data may vary depending on your subscription plan.","format":"date"},"endDate":{"type":"string","description":"The end date(YYYY-MM-DD) up to which M&A deals data is required.","format":"date"},"date":{"type":"string","description":"Exact date(YYYY-MM-DD) for which the M&A deals data is required.","format":"date"},"acquiringCompanyName":{"type":"string","description":"The name of the acquiring company for which the M&A deals data is required. Partial name matches are supported. Multiple values can be provided either as a comma-separated string or as an array."},"acquiringCompanyDomain":{"type":"string","description":"The website domain of the acquiring company for which the M&A deals data is required. Partial matches are supported. Multiple values can be provided either as a comma-separated string or as an array."},"acquiringCompanyIndustry":{"type":"string","description":"The industry of the acquiring companies for which M&A deals data is required. The industries are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values should be provided as an array.","enum":["accounting, audit & tax","advertising & communication","agriculture, animal husbandry & forestry","angels/ venture capital/ private equity","automobile","aviation","banking","bio-technology","business services","chemicals & fertilizers","clean technology","conglomerate","consulting","consumer products","consumer services","defence","distribution","e-commerce","economic development","education","energy & utilities","engineering, procurement & construction","financial services","gambling","gaming","government","healthcare","human resources","insurance","it services & outsourcing","legal","logistics & supply chain","manufacturing","media & entertainment","medical device","metals & mining","not-for-profit/ ngo","others","pharmaceuticals","publishing","railways","real estate","regulatory","restaurants & food services","retail","security","shipping & ports","spac/blank check","sports","technology","telecommunication","textiles","tourism & hospitality","trading","transportation"]},"acquiringCompanyLocation":{"type":"string","description":"The HeadQuarters location of the acquiring companies for which M&A deals data is required. The location can be City or State/Province or Country. Multiple values can be provided either as a comma-separated string or as an array."},"acquiringCompanyType":{"type":"string","description":"The company type of the acquiring companies for which M&A deals data is required. The company types are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Public","Private","Government/Regulator","Not-for-profit","Others"]},"acquiringCompanyTicker":{"type":"string","description":"The company type of the acquiring companies for which M&A deals data is required. The company types are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided either as a comma-separated string or as an array."},"acquiredCompanyName":{"type":"string","description":"The name of the acquired company for which the M&A deals data is required. Partial name matches are supported. Multiple values can be provided either as a comma-separated string or as an array."},"acquiredCompanyDomain":{"type":"string","description":"The website domain of the acquired company for which the M&A deals data is required. Partial matches are supported. Multiple values can be provided either as a comma-separated string or as an array."},"acquiredCompanyIndustry":{"type":"string","description":"The industry of the acquired companies for which M&A deals data is required. The industries are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values should be provided as an array.","enum":["accounting, audit & tax","advertising & communication","agriculture, animal husbandry & forestry","angels/ venture capital/ private equity","automobile","aviation","banking","bio-technology","business services","chemicals & fertilizers","clean technology","conglomerate","consulting","consumer products","consumer services","defence","distribution","e-commerce","economic development","education","energy & utilities","engineering, procurement & construction","financial services","gambling","gaming","government","healthcare","human resources","insurance","it services & outsourcing","legal","logistics & supply chain","manufacturing","media & entertainment","medical device","metals & mining","not-for-profit/ ngo","others","pharmaceuticals","publishing","railways","real estate","regulatory","restaurants & food services","retail","security","shipping & ports","spac/blank check","sports","technology","telecommunication","textiles","tourism & hospitality","trading","transportation"]},"acquiredCompanyLocation":{"type":"string","description":"The HeadQuarters location of the acquired companies for which M&A deals data is required. The location can be City or State/Province or Country. Multiple values can be provided either as a comma-separated string or as an array."},"acquiredCompanyType":{"type":"string","description":"The company type of the acquired companies for which M&A deals data is required. The company types are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Public","Private","Government/Regulator","Not-for-profit","Others"]},"acquiredCompanyTicker":{"type":"string","description":"Acquired company stock ticker if it's a public company."},"sellingCompanyName":{"type":"string","description":"The name of the selling company for which the M&A deals data is required. Partial matches are supported."},"sellingCompanyDomain":{"type":"string","description":"The website domain of the selling company for which the M&A deals data is required. Partial matches are supported."},"sellingCompanyIndustry":{"type":"string","description":"The industry of the selling companies for which M&A deals data is required. The industries are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values should be provided as an array.","enum":["accounting, audit & tax","advertising & communication","agriculture, animal husbandry & forestry","angels/ venture capital/ private equity","automobile","aviation","banking","bio-technology","business services","chemicals & fertilizers","clean technology","conglomerate","consulting","consumer products","consumer services","defence","distribution","e-commerce","economic development","education","energy & utilities","engineering, procurement & construction","financial services","gambling","gaming","government","healthcare","human resources","insurance","it services & outsourcing","legal","logistics & supply chain","manufacturing","media & entertainment","medical device","metals & mining","not-for-profit/ ngo","others","pharmaceuticals","publishing","railways","real estate","regulatory","restaurants & food services","retail","security","shipping & ports","spac/blank check","sports","technology","telecommunication","textiles","tourism & hospitality","trading","transportation"]},"sellingCompanyLocation":{"type":"string","description":"The HeadQuarters location of the selling companies for which M&A deals data is required. The location can be City or State/Province or Country."},"sellingCompanyType":{"type":"string","description":"The company type of the selling companies for which M&A deals data is required. The company types are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Public","Private","Government/Regulator","Not-for-profit","Others"]},"sellingCompanyTicker":{"type":"string","description":"Selling company stock ticker if it's a public company."},"mnaStatus":{"type":"string","description":"Filter M&A deals data based on M&A status. The common status are Announced, Completed and Terminated.","enum":["Announced","Completed","Terminated","Rumours & Speculation","Bid/Offer","In Discussion/Negotiation","Shareholder Approved","Shareholder Rejected","Board Rejected","Regulator Review","Regulator Approved","Regulator Rejected","Legal Dispute"]},"mnaType":{"type":"string","description":"Filter M&A deals data by M&A Type.","enum":["Acquisition - Total","Acquisition - Asset / Business Division Sale","Acquisition - Financial Stake","Acquisition - Joint Venture Stake","Merger","Merger - Business Operations","Merger - Internal Operations/Subsidiaries","Reverse Takeover","Tender Offer","Acqui-hire","Other"]},"dealAmount":{"pattern":"^(>|>=|<|<=|=|!=)?\\d+(,\\d+)?$","type":"number","description":"Filter the M&A deals data by deal amount. Pass the `currency` whenver `dealAmount` is used. If `currency` is not provided along with `dealAmount`, all the deals data that matches the deal amount of any currency will be returned. The allowed operators are >, >=, <, <=,=,!=, (MinimumValue),(Maximum Value). Examples: >1000000, >=1000000, <1000000, <=1000000,=1000000,!=1000000, 1000000,400000","format":"float"},"currency":{"type":"string","description":"The currency of the deal transaction.","enum":["USD","CAD","EUR","GBP","INR","AUD","CHF","CNY","JPY","SEK"]},"limit":{"type":"integer","description":"The maximum number of records to be returned."}}},"MnaSearchResponse":{"required":["code","count","dataset"],"type":"object","properties":{"code":{"type":"integer"},"count":{"type":"integer"},"dataset":{"type":"array","items":{"$ref":"#/components/schemas/inline_response_200"}},"openingBalance":{"type":"integer","nullable":true},"closingBalance":{"type":"integer","nullable":true},"creditsConsumed":{"type":"integer","nullable":true}}},"inline_response_200":{"type":"object","properties":{"id":{"type":"string","description":"Unique ID of the record"},"announcedDate":{"type":"string","description":"Merger/Acqusition announced date(YYYY-MM-DD).","format":"date"},"acquiringCompany":{"$ref":"#/components/schemas/inline_response_200_acquiringCompany"},"acquiredCompany":{"$ref":"#/components/schemas/inline_response_200_acquiredCompany"},"sellingCompany":{"$ref":"#/components/schemas/inline_response_200_sellingCompany"},"mnaType":{"type":"string","description":"Merger & Acquisition type"},"mnaStatus":{"type":"string","description":"Merger & Acquisition deal status"},"dealAmount":{"type":"number","description":"The deal amount if publicly disclosed","format":"float"},"currency":{"type":"string","description":"The currency of the deal transaction"},"lastModified":{"type":"string","description":"The last modified date of the record (YYYY-MM-DD)","format":"date"},"title":{"type":"string","description":"Source title - News or press release headline"},"url":{"type":"string","description":"URL of the source document."}}},"inline_response_200_acquiringCompany":{"type":"object","properties":{"name":{"type":"string","description":"Acquiring company name"},"domain":{"type":"string","description":"Acquiring company website domain"},"industries":{"type":"array","description":"The industries associated with the acquiring company.","items":{"type":"string"}},"location":{"type":"string","description":"The HQ location of the acquiring company."},"type":{"type":"string","description":"The company type of the acquiring company"},"ticker":{"type":"array","description":"The stock ticker symbol of the acquiring company (if public).","items":{"type":"string"}}}},"inline_response_200_acquiredCompany":{"type":"object","properties":{"name":{"type":"string","description":"Acquired company name"},"domain":{"type":"string","description":"Aacquired company website domain"},"industries":{"type":"array","description":"The industries associated with the acquired company.","items":{"type":"string"}},"location":{"type":"string","description":"The HQ location of the acquired company."},"type":{"type":"string","description":"The company type of the acquired company."},"ticker":{"type":"array","description":"The stock ticker symbol of the acquired company (if public).","items":{"type":"string"}}}},"inline_response_200_sellingCompany":{"type":"object","properties":{"name":{"type":"string","description":"Selling company name"},"domain":{"type":"string","description":"Selling company website domain"},"industries":{"type":"array","description":"The industries associated with the selling company.","items":{"type":"string"}},"location":{"type":"string","description":"The HQ location of the selling company."},"type":{"type":"string","description":"The company type of the selling company."},"ticker":{"type":"array","description":"The stock ticker symbol of the selling company (if public)","items":{"type":"string"}}}}}},"paths":{"/api/dataset/mna":{"post":{"summary":"Submit a request to get Mergers & Acquisitions (M&A) data","description":"This REST API endpoint provides access to both ongoing and historical Mergers & Acquisitions (M&A) and Divestment deal data from the Intellizence Mergers & Acquisitions Dataset. Data access is limited to records within your subscription’s entitled date range.\n\nUsers can filter results using the following parameters:\n\n`dateType`, `startDate`, `endDate`, `date`,\n`acquiringCompanyName`, `acquiringCompanyDomain`, `acquiringCompanyIndustry`, `acquiringCompanyLocation`, `acquiringCompanyType`, `acquiringCompanyTicker`,\n`acquiredCompanyName`, `acquiredCompanyDomain`, `acquiredCompanyIndustry`, `acquiredCompanyLocation`, `acquiredCompanyType`, `acquiredCompanyTicker`,\n`sellingCompanyName`, `sellingCompanyDomain`, `sellingCompanyIndustry`, `sellingCompanyLocation`, `sellingCompanyType`, `sellingCompanyTicker`,\n`dealAmount`, `currency`, `mnaStatus`, and `mnaType`.\n\nUsers can limit the number of records returned using the `limit` parameter. All parameters are optional.\n\nThe API key must be passed in the HTTP header as `x-api-key`.","operationId":"getMnaDataset","parameters":[{"name":"x-api-key","in":"header","description":"Intellizence API key for authenticating the request.","required":true,"schema":{"type":"string"}}],"requestBody":{"description":"Intellizence Mergers & Acquisitions Data Request Body","content":{"application/json":{"schema":{"$ref":"#/components/schemas/dataset_mna_body"}}}},"responses":{"200":{"description":"Successful response.\n\nNote: Credit fields (openingBalance, closingBalance, creditsConsumed) are returned only for Pay-Per-Use billing.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/MnaSearchResponse"}}}},"400":{"description":"400 - Bad Request\n\nBad request, possibly missing required parameters, invalid data, invalid or missing API key.\n\n- 701 - Invalid Start Date format (YYYY-MM-DD required)\n- 702 - Invalid End Date format (YYYY-MM-DD required)\n- 703 - Plan or resource not subscribed\n- 709 - No companies configured for this account\n- 710 - No triggers configured for this account"},"402":{"description":"402 - Payment Required\n\n- 704 - Payment is pending\n- 712 - Insufficient credits for this request"},"403":{"description":"403 - Forbidden\n- 706 - Requested resource/data product is not included in the current subscription plan\n- 707 - Subscription has expired\n- 708 - Start date is outside your subscription’s allowed date range"},"406":{"description":"406 - Invalid deal amount filter format"},"500":{"description":"500 - Internal Server Error\n- 715 - A technical error occurred\n- 799 - A technical error occurred"}}}}}}
```

## The inline\_response\_200\_sellingCompany object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Mergers & Acquisitions (M&A) Signals API","version":"1.0"},"components":{"schemas":{"inline_response_200_sellingCompany":{"type":"object","properties":{"name":{"type":"string","description":"Selling company name"},"domain":{"type":"string","description":"Selling company website domain"},"industries":{"type":"array","description":"The industries associated with the selling company.","items":{"type":"string"}},"location":{"type":"string","description":"The HQ location of the selling company."},"type":{"type":"string","description":"The company type of the selling company."},"ticker":{"type":"array","description":"The stock ticker symbol of the selling company (if public)","items":{"type":"string"}}}}}}}
```

## The inline\_response\_200\_acquiringCompany object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Mergers & Acquisitions (M&A) Signals API","version":"1.0"},"components":{"schemas":{"inline_response_200_acquiringCompany":{"type":"object","properties":{"name":{"type":"string","description":"Acquiring company name"},"domain":{"type":"string","description":"Acquiring company website domain"},"industries":{"type":"array","description":"The industries associated with the acquiring company.","items":{"type":"string"}},"location":{"type":"string","description":"The HQ location of the acquiring company."},"type":{"type":"string","description":"The company type of the acquiring company"},"ticker":{"type":"array","description":"The stock ticker symbol of the acquiring company (if public).","items":{"type":"string"}}}}}}}
```

## The inline\_response\_200 object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Mergers & Acquisitions (M&A) Signals API","version":"1.0"},"components":{"schemas":{"inline_response_200":{"type":"object","properties":{"id":{"type":"string","description":"Unique ID of the record"},"announcedDate":{"type":"string","description":"Merger/Acqusition announced date(YYYY-MM-DD).","format":"date"},"acquiringCompany":{"$ref":"#/components/schemas/inline_response_200_acquiringCompany"},"acquiredCompany":{"$ref":"#/components/schemas/inline_response_200_acquiredCompany"},"sellingCompany":{"$ref":"#/components/schemas/inline_response_200_sellingCompany"},"mnaType":{"type":"string","description":"Merger & Acquisition type"},"mnaStatus":{"type":"string","description":"Merger & Acquisition deal status"},"dealAmount":{"type":"number","description":"The deal amount if publicly disclosed","format":"float"},"currency":{"type":"string","description":"The currency of the deal transaction"},"lastModified":{"type":"string","description":"The last modified date of the record (YYYY-MM-DD)","format":"date"},"title":{"type":"string","description":"Source title - News or press release headline"},"url":{"type":"string","description":"URL of the source document."}}},"inline_response_200_acquiringCompany":{"type":"object","properties":{"name":{"type":"string","description":"Acquiring company name"},"domain":{"type":"string","description":"Acquiring company website domain"},"industries":{"type":"array","description":"The industries associated with the acquiring company.","items":{"type":"string"}},"location":{"type":"string","description":"The HQ location of the acquiring company."},"type":{"type":"string","description":"The company type of the acquiring company"},"ticker":{"type":"array","description":"The stock ticker symbol of the acquiring company (if public).","items":{"type":"string"}}}},"inline_response_200_acquiredCompany":{"type":"object","properties":{"name":{"type":"string","description":"Acquired company name"},"domain":{"type":"string","description":"Aacquired company website domain"},"industries":{"type":"array","description":"The industries associated with the acquired company.","items":{"type":"string"}},"location":{"type":"string","description":"The HQ location of the acquired company."},"type":{"type":"string","description":"The company type of the acquired company."},"ticker":{"type":"array","description":"The stock ticker symbol of the acquired company (if public).","items":{"type":"string"}}}},"inline_response_200_sellingCompany":{"type":"object","properties":{"name":{"type":"string","description":"Selling company name"},"domain":{"type":"string","description":"Selling company website domain"},"industries":{"type":"array","description":"The industries associated with the selling company.","items":{"type":"string"}},"location":{"type":"string","description":"The HQ location of the selling company."},"type":{"type":"string","description":"The company type of the selling company."},"ticker":{"type":"array","description":"The stock ticker symbol of the selling company (if public)","items":{"type":"string"}}}}}}}
```

## The dataset\_mna\_body object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Mergers & Acquisitions (M&A) Signals API","version":"1.0"},"components":{"schemas":{"dataset_mna_body":{"type":"object","properties":{"dateType":{"type":"string","description":"Choose the date type used to filter records.The default value is 'Announced'.To get the daily update of records created or modified, 'LAST-MODIFIED' is recommended.","enum":["ANNOUNCED","LAST-MODIFIED"]},"startDate":{"type":"string","description":"The start date(YYYY-MM-DD) from which M&A deals data is required. The Intellizence Mergers & Acquisitions Dataset contains data beginning from 2020-01-01. Access to historical data may vary depending on your subscription plan.","format":"date"},"endDate":{"type":"string","description":"The end date(YYYY-MM-DD) up to which M&A deals data is required.","format":"date"},"date":{"type":"string","description":"Exact date(YYYY-MM-DD) for which the M&A deals data is required.","format":"date"},"acquiringCompanyName":{"type":"string","description":"The name of the acquiring company for which the M&A deals data is required. Partial name matches are supported. Multiple values can be provided either as a comma-separated string or as an array."},"acquiringCompanyDomain":{"type":"string","description":"The website domain of the acquiring company for which the M&A deals data is required. Partial matches are supported. Multiple values can be provided either as a comma-separated string or as an array."},"acquiringCompanyIndustry":{"type":"string","description":"The industry of the acquiring companies for which M&A deals data is required. The industries are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values should be provided as an array.","enum":["accounting, audit & tax","advertising & communication","agriculture, animal husbandry & forestry","angels/ venture capital/ private equity","automobile","aviation","banking","bio-technology","business services","chemicals & fertilizers","clean technology","conglomerate","consulting","consumer products","consumer services","defence","distribution","e-commerce","economic development","education","energy & utilities","engineering, procurement & construction","financial services","gambling","gaming","government","healthcare","human resources","insurance","it services & outsourcing","legal","logistics & supply chain","manufacturing","media & entertainment","medical device","metals & mining","not-for-profit/ ngo","others","pharmaceuticals","publishing","railways","real estate","regulatory","restaurants & food services","retail","security","shipping & ports","spac/blank check","sports","technology","telecommunication","textiles","tourism & hospitality","trading","transportation"]},"acquiringCompanyLocation":{"type":"string","description":"The HeadQuarters location of the acquiring companies for which M&A deals data is required. The location can be City or State/Province or Country. Multiple values can be provided either as a comma-separated string or as an array."},"acquiringCompanyType":{"type":"string","description":"The company type of the acquiring companies for which M&A deals data is required. The company types are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Public","Private","Government/Regulator","Not-for-profit","Others"]},"acquiringCompanyTicker":{"type":"string","description":"The company type of the acquiring companies for which M&A deals data is required. The company types are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided either as a comma-separated string or as an array."},"acquiredCompanyName":{"type":"string","description":"The name of the acquired company for which the M&A deals data is required. Partial name matches are supported. Multiple values can be provided either as a comma-separated string or as an array."},"acquiredCompanyDomain":{"type":"string","description":"The website domain of the acquired company for which the M&A deals data is required. Partial matches are supported. Multiple values can be provided either as a comma-separated string or as an array."},"acquiredCompanyIndustry":{"type":"string","description":"The industry of the acquired companies for which M&A deals data is required. The industries are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values should be provided as an array.","enum":["accounting, audit & tax","advertising & communication","agriculture, animal husbandry & forestry","angels/ venture capital/ private equity","automobile","aviation","banking","bio-technology","business services","chemicals & fertilizers","clean technology","conglomerate","consulting","consumer products","consumer services","defence","distribution","e-commerce","economic development","education","energy & utilities","engineering, procurement & construction","financial services","gambling","gaming","government","healthcare","human resources","insurance","it services & outsourcing","legal","logistics & supply chain","manufacturing","media & entertainment","medical device","metals & mining","not-for-profit/ ngo","others","pharmaceuticals","publishing","railways","real estate","regulatory","restaurants & food services","retail","security","shipping & ports","spac/blank check","sports","technology","telecommunication","textiles","tourism & hospitality","trading","transportation"]},"acquiredCompanyLocation":{"type":"string","description":"The HeadQuarters location of the acquired companies for which M&A deals data is required. The location can be City or State/Province or Country. Multiple values can be provided either as a comma-separated string or as an array."},"acquiredCompanyType":{"type":"string","description":"The company type of the acquired companies for which M&A deals data is required. The company types are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Public","Private","Government/Regulator","Not-for-profit","Others"]},"acquiredCompanyTicker":{"type":"string","description":"Acquired company stock ticker if it's a public company."},"sellingCompanyName":{"type":"string","description":"The name of the selling company for which the M&A deals data is required. Partial matches are supported."},"sellingCompanyDomain":{"type":"string","description":"The website domain of the selling company for which the M&A deals data is required. Partial matches are supported."},"sellingCompanyIndustry":{"type":"string","description":"The industry of the selling companies for which M&A deals data is required. The industries are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values should be provided as an array.","enum":["accounting, audit & tax","advertising & communication","agriculture, animal husbandry & forestry","angels/ venture capital/ private equity","automobile","aviation","banking","bio-technology","business services","chemicals & fertilizers","clean technology","conglomerate","consulting","consumer products","consumer services","defence","distribution","e-commerce","economic development","education","energy & utilities","engineering, procurement & construction","financial services","gambling","gaming","government","healthcare","human resources","insurance","it services & outsourcing","legal","logistics & supply chain","manufacturing","media & entertainment","medical device","metals & mining","not-for-profit/ ngo","others","pharmaceuticals","publishing","railways","real estate","regulatory","restaurants & food services","retail","security","shipping & ports","spac/blank check","sports","technology","telecommunication","textiles","tourism & hospitality","trading","transportation"]},"sellingCompanyLocation":{"type":"string","description":"The HeadQuarters location of the selling companies for which M&A deals data is required. The location can be City or State/Province or Country."},"sellingCompanyType":{"type":"string","description":"The company type of the selling companies for which M&A deals data is required. The company types are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Public","Private","Government/Regulator","Not-for-profit","Others"]},"sellingCompanyTicker":{"type":"string","description":"Selling company stock ticker if it's a public company."},"mnaStatus":{"type":"string","description":"Filter M&A deals data based on M&A status. The common status are Announced, Completed and Terminated.","enum":["Announced","Completed","Terminated","Rumours & Speculation","Bid/Offer","In Discussion/Negotiation","Shareholder Approved","Shareholder Rejected","Board Rejected","Regulator Review","Regulator Approved","Regulator Rejected","Legal Dispute"]},"mnaType":{"type":"string","description":"Filter M&A deals data by M&A Type.","enum":["Acquisition - Total","Acquisition - Asset / Business Division Sale","Acquisition - Financial Stake","Acquisition - Joint Venture Stake","Merger","Merger - Business Operations","Merger - Internal Operations/Subsidiaries","Reverse Takeover","Tender Offer","Acqui-hire","Other"]},"dealAmount":{"pattern":"^(>|>=|<|<=|=|!=)?\\d+(,\\d+)?$","type":"number","description":"Filter the M&A deals data by deal amount. Pass the `currency` whenver `dealAmount` is used. If `currency` is not provided along with `dealAmount`, all the deals data that matches the deal amount of any currency will be returned. The allowed operators are >, >=, <, <=,=,!=, (MinimumValue),(Maximum Value). Examples: >1000000, >=1000000, <1000000, <=1000000,=1000000,!=1000000, 1000000,400000","format":"float"},"currency":{"type":"string","description":"The currency of the deal transaction.","enum":["USD","CAD","EUR","GBP","INR","AUD","CHF","CNY","JPY","SEK"]},"limit":{"type":"integer","description":"The maximum number of records to be returned."}}}}}}
```

## The inline\_response\_200\_acquiredCompany object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Mergers & Acquisitions (M&A) Signals API","version":"1.0"},"components":{"schemas":{"inline_response_200_acquiredCompany":{"type":"object","properties":{"name":{"type":"string","description":"Acquired company name"},"domain":{"type":"string","description":"Aacquired company website domain"},"industries":{"type":"array","description":"The industries associated with the acquired company.","items":{"type":"string"}},"location":{"type":"string","description":"The HQ location of the acquired company."},"type":{"type":"string","description":"The company type of the acquired company."},"ticker":{"type":"array","description":"The stock ticker symbol of the acquired company (if public).","items":{"type":"string"}}}}}}}
```

## The ErrorResponse object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Mergers & Acquisitions (M&A) Signals API","version":"1.0"},"components":{"schemas":{"ErrorResponse":{"required":["httpCode","message"],"type":"object","properties":{"httpCode":{"type":"integer"},"businessCode":{"type":"integer","nullable":true},"message":{"type":"string"},"details":{"type":"object","nullable":true}}}}}}
```

## The MnaSearchResponse object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Mergers & Acquisitions (M&A) Signals API","version":"1.0"},"components":{"schemas":{"MnaSearchResponse":{"required":["code","count","dataset"],"type":"object","properties":{"code":{"type":"integer"},"count":{"type":"integer"},"dataset":{"type":"array","items":{"$ref":"#/components/schemas/inline_response_200"}},"openingBalance":{"type":"integer","nullable":true},"closingBalance":{"type":"integer","nullable":true},"creditsConsumed":{"type":"integer","nullable":true}}},"inline_response_200":{"type":"object","properties":{"id":{"type":"string","description":"Unique ID of the record"},"announcedDate":{"type":"string","description":"Merger/Acqusition announced date(YYYY-MM-DD).","format":"date"},"acquiringCompany":{"$ref":"#/components/schemas/inline_response_200_acquiringCompany"},"acquiredCompany":{"$ref":"#/components/schemas/inline_response_200_acquiredCompany"},"sellingCompany":{"$ref":"#/components/schemas/inline_response_200_sellingCompany"},"mnaType":{"type":"string","description":"Merger & Acquisition type"},"mnaStatus":{"type":"string","description":"Merger & Acquisition deal status"},"dealAmount":{"type":"number","description":"The deal amount if publicly disclosed","format":"float"},"currency":{"type":"string","description":"The currency of the deal transaction"},"lastModified":{"type":"string","description":"The last modified date of the record (YYYY-MM-DD)","format":"date"},"title":{"type":"string","description":"Source title - News or press release headline"},"url":{"type":"string","description":"URL of the source document."}}},"inline_response_200_acquiringCompany":{"type":"object","properties":{"name":{"type":"string","description":"Acquiring company name"},"domain":{"type":"string","description":"Acquiring company website domain"},"industries":{"type":"array","description":"The industries associated with the acquiring company.","items":{"type":"string"}},"location":{"type":"string","description":"The HQ location of the acquiring company."},"type":{"type":"string","description":"The company type of the acquiring company"},"ticker":{"type":"array","description":"The stock ticker symbol of the acquiring company (if public).","items":{"type":"string"}}}},"inline_response_200_acquiredCompany":{"type":"object","properties":{"name":{"type":"string","description":"Acquired company name"},"domain":{"type":"string","description":"Aacquired company website domain"},"industries":{"type":"array","description":"The industries associated with the acquired company.","items":{"type":"string"}},"location":{"type":"string","description":"The HQ location of the acquired company."},"type":{"type":"string","description":"The company type of the acquired company."},"ticker":{"type":"array","description":"The stock ticker symbol of the acquired company (if public).","items":{"type":"string"}}}},"inline_response_200_sellingCompany":{"type":"object","properties":{"name":{"type":"string","description":"Selling company name"},"domain":{"type":"string","description":"Selling company website domain"},"industries":{"type":"array","description":"The industries associated with the selling company.","items":{"type":"string"}},"location":{"type":"string","description":"The HQ location of the selling company."},"type":{"type":"string","description":"The company type of the selling company."},"ticker":{"type":"array","description":"The stock ticker symbol of the selling company (if public)","items":{"type":"string"}}}}}}}
```


# Intellizence Mergers & Acquisitions (M\&A) API Sample Requests

Explore sample requests for the Intellizence Mergers and Acquisitions API. Learn how to retrieve M\&A records by date, company, industry, location, deal status, deal type, and deal value.

Use these sample API requests to retrieve mergers, acquisitions, divestments, and related transaction records from the Intellizence Mergers and Acquisitions API.

These examples show common ways to filter M\&A records by date, company, industry, geography, deal status, deal type, and deal value.

{% hint style="info" %}
All request parameters are optional. You can use a single filter or combine multiple filters based on your use case.
{% endhint %}

***

### Endpoint

```http
POST https://connect.intellizence.com/api/dataset/mna
```

### Authentication

Include your API key in the request header.

```http
x-api-key: YOUR_API_KEY
```

### Content Type

```http
Content-Type: application/json
```

***

## M\&A API Sample API Requests

### 1. Get Daily Updated Records

Use `dateType: "LAST-MODIFIED"` to retrieve records that were created or updated on a specific date.

This is recommended for daily syncs, alerts, enrichment workflows, and automated data pipelines.

#### Request Body

```json
{
  "dateType": "LAST-MODIFIED",
  "date": "2025-02-24",
  "limit": 5
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/mna \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "LAST-MODIFIED",
    "date": "2025-02-24",
    "limit": 5
  }'
```

***

### 2. Get Deals Announced on a Specific Date

Use `dateType: "ANNOUNCED"` and `date` to retrieve M\&A deals announced on a specific date.

#### Request Body

```json
{
  "dateType": "ANNOUNCED",
  "date": "2025-02-24",
  "limit": 10
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/mna \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "ANNOUNCED",
    "date": "2025-02-24",
    "limit": 10
  }'
```

***

### 3. Get Deals Announced Within a Date Range

Use `startDate` and `endDate` to retrieve deals announced during a specific period.

#### Request Body

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-02-01",
  "endDate": "2025-02-28",
  "limit": 25
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/mna \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "ANNOUNCED",
    "startDate": "2025-02-01",
    "endDate": "2025-02-28",
    "limit": 25
  }'
```

***

### 4. Search by Acquiring Company

Use `acquiringCompanyName` to find deals involving a specific acquirer.

This is useful for tracking acquisition activity by strategic buyers, private equity firms, investment firms, and large corporations.

#### Request Body

```json
{
  "acquiringCompanyName": "Blackstone",
  "limit": 10
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/mna \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "acquiringCompanyName": "Blackstone",
    "limit": 10
  }'
```

***

### 5. Search by Acquired Company

Use `acquiredCompanyName` to find deals involving a specific target or acquired company.

#### Request Body

```json
{
  "acquiredCompanyName": "VMware",
  "limit": 10
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/mna \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "acquiredCompanyName": "VMware",
    "limit": 10
  }'
```

***

### 6. Search by Industry

Use industry filters to retrieve deals where the acquiring or acquired company belongs to one or more industries.

This is useful for sector research, market mapping, investment analysis, and competitive intelligence.

#### Request Body

```json
{
  "acquiredCompanyIndustry": [
    "technology",
    "financial services"
  ],
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/mna \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "acquiredCompanyIndustry": [
      "technology",
      "financial services"
    ],
    "limit": 20
  }'
```

***

### 7. Search by Company Location

Use company location filters to find deals involving companies headquartered in a specific country, state, province, city, or region.

#### Request Body

```json
{
  "acquiredCompanyLocation": "United States of America",
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/mna \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "acquiredCompanyLocation": "United States of America",
    "limit": 20
  }'
```

***

### 8. Search by Deal Status

Use `mnaStatus` to filter deals by status such as announced, completed, pending, or terminated.

#### Request Body

```json
{
  "mnaStatus": "Announced",
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/mna \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "mnaStatus": "Announced",
    "limit": 20
  }'
```

***

### 9. Search by Deal Value

Use `dealAmount` to filter deals by transaction value.

You can use comparison operators such as `>`, `>=`, `<`, `<=`, `=`, and `!=`.

When filtering by deal amount, include `currency` for more precise results.

#### Request Body

```json
{
  "dealAmount": ">1000000000",
  "currency": "USD",
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/mna \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dealAmount": ">1000000000",
    "currency": "USD",
    "limit": 20
  }'
```

***

### 10. Use Multiple Filters Together

Combine filters to narrow results by date range, industry, company type, deal value, currency, and deal status.

#### Request Body

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-01-01",
  "endDate": "2025-03-31",
  "acquiredCompanyIndustry": [
    "technology"
  ],
  "acquiringCompanyType": [
    "Public"
  ],
  "mnaStatus": "Announced",
  "dealAmount": ">500000000",
  "currency": "USD",
  "limit": 50
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/mna \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "ANNOUNCED",
    "startDate": "2025-01-01",
    "endDate": "2025-03-31",
    "acquiredCompanyIndustry": [
      "technology"
    ],
    "acquiringCompanyType": [
      "Public"
    ],
    "mnaStatus": "Announced",
    "dealAmount": ">500000000",
    "currency": "USD",
    "limit": 50
  }'
```

***

## Use Case Examples

### 1. Daily Data Sync

Use this example when you want to pull newly added or updated M\&A records into your application, database, CRM, or analytics workflow.

#### Recommended Filters

```json
{
  "dateType": "LAST-MODIFIED",
  "date": "2025-02-24",
  "limit": 100
}
```

#### Best For

* Data pipelines
* Daily refreshes
* Internal dashboards
* Alerts and workflow automation
* CRM and data warehouse enrichment

***

### 2. CRM or Account Enrichment

Use this example to check whether a company in your CRM has recent M\&A activity.

#### Recommended Filters

```json
{
  "acquiringCompanyDomain": "salesforce.com",
  "dateType": "LAST-MODIFIED",
  "startDate": "2025-01-01",
  "endDate": "2025-03-31",
  "limit": 10
}
```

#### Best For

* CRM enrichment
* Account scoring
* Sales intelligence
* Customer intelligence
* Signal-based selling workflows

***

### 3. Investment Research

Use this example to track large transactions in a specific sector.

#### Recommended Filters

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-01-01",
  "endDate": "2025-12-31",
  "acquiredCompanyIndustry": [
    "healthcare"
  ],
  "dealAmount": ">1000000000",
  "currency": "USD",
  "limit": 50
}
```

#### Best For

* Market mapping
* Sector research
* Deal trend analysis
* Event-driven investing
* Private equity and corporate development research

***

### 4. Competitive Intelligence

Use this example to monitor acquisition activity in a specific industry or geography.

#### Recommended Filters

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-01-01",
  "endDate": "2025-03-31",
  "acquiredCompanyIndustry": [
    "software"
  ],
  "acquiredCompanyLocation": "United States of America",
  "limit": 25
}
```

#### Best For

* Competitor tracking
* Market consolidation analysis
* Industry monitoring
* Strategic planning
* Product and market research

***

### 5. Sales and Account Monitoring

Use this example to identify companies going through ownership changes, integration activity, vendor reassessment, or strategic transformation.

#### Recommended Filters

```json
{
  "dateType": "LAST-MODIFIED",
  "startDate": "2025-01-01",
  "endDate": "2025-03-31",
  "acquiredCompanyIndustry": [
    "software"
  ],
  "mnaStatus": "Announced",
  "limit": 25
}
```

#### Best For

* Prospecting
* Account prioritization
* Trigger-based outreach
* Customer risk monitoring
* Expansion and cross-sell opportunities

***

## Recommended Use Cases

| Use Case                     | Recommended Filters                                        |
| ---------------------------- | ---------------------------------------------------------- |
| Daily data sync              | `dateType`, `date`, `limit`                                |
| CRM enrichment               | company domain filters, `dateType`, `startDate`, `endDate` |
| Investment research          | industry, date range, deal value, currency                 |
| Competitive intelligence     | industry, geography, announced date                        |
| Sales and account monitoring | industry, status, last modified date                       |

***

## Best Practices

### Use `LAST-MODIFIED` for daily syncs

For recurring syncs, alerts, and automated workflows, use `LAST-MODIFIED`.

```json
{
  "dateType": "LAST-MODIFIED",
  "date": "2025-02-24"
}
```

This helps retrieve records that were newly added or updated on that date.

### Use `ANNOUNCED` for event-date research

For research based on when a deal was announced, use `ANNOUNCED`.

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-01-01",
  "endDate": "2025-03-31"
}
```

### Use `limit` to control result size

The default limit is `100` records if no limit is provided.

```json
{
  "limit": 100
}
```

### Combine filters for more precise results

You can combine multiple filters in a single request to narrow your results.

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-01-01",
  "endDate": "2025-03-31",
  "acquiredCompanyIndustry": [
    "technology"
  ],
  "mnaStatus": "Announced",
  "dealAmount": ">500000000",
  "currency": "USD",
  "limit": 50
}
```

***

## Notes

* All parameters are optional.
* Dates should be provided in `YYYY-MM-DD` format.
* Use `LAST-MODIFIED` when you want newly added or updated records.
* Use `ANNOUNCED` when you want records based on the deal announcement date.
* Include `currency` when filtering by `dealAmount`.
* Use company domain filters for CRM matching, account enrichment, and workflow automation.
* Use industry and geography filters for market research, competitive intelligence, and investment analysis.


# Intellizence Startup Funding & Venture Capital (VC) Deals Signals API

This REST API provides continuous access to ongoing and historical Startup Funding & Venture Capital (VC) deals data from the Intellizence Startup Funding Dataset.

{% hint style="info" %}
Best  suited for :

* Continuous monitoring of Startup Funding and Venture Capital (VC) deal events
* Trigger alerts and automated workflows
* Startup funding trends & analysis
* Company relationship graphs and entity intelligence
* Power AI agents and internal intelligence platforms
  {% endhint %}

> **Ready to get started?** [**Request your API key**](https://intellizence.com/api-trial/) and start building.\
> **Questions?** [**Schedule a call**](https://intellizence.com/schedule-a-demo/) or email us at <sales@intellizence.com>.

**Security Notice:** Please keep API Key secure. Do not share your API key in publicly accessible areas such as GitHub, client-side code, and so forth.

## Submit a request to get the startup funding and VC deals data

> This REST API endpoint provides access to both ongoing and historical startup funding and Venture Capital (VC) deals from the Intellizence Startup Funding Dataset. Data access is limited to records within your subscription’s entitled date range.\
> \
> Users can search data using the following parameters:\
> \
> \`dateType\`, \`startDate\`, \`endDate\`, \`date\`, \`companyDomain\`, \`companyName\`, \`companyIndustry\`, \`companyLocation\`, \`companyType\`, \`companyTicker\`, \`fundingRound\`, \`dealAmount\`, \`valuation\`, \`investor\`, and \`currency\`.\
> \
> Users can limit the number of records returned using the \`limit\` parameter. All parameters are optional.\
> \
> The API key must be passed in the HTTP header as \`x-api-key\`.\
> \
> Note: Startup funding data is generally available for VC-funded private companies only. It is not available for public companies, non-VC-funded private companies, government entities, hospitals, universities, or other non-commercial organizations.

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Startup Funding Signals API","version":"1.0"},"servers":[{"url":"https://connect.intellizence.com"}],"paths":{"/api/dataset/fundraising":{"post":{"summary":"Submit a request to get the startup funding and VC deals data","description":"This REST API endpoint provides access to both ongoing and historical startup funding and Venture Capital (VC) deals from the Intellizence Startup Funding Dataset. Data access is limited to records within your subscription’s entitled date range.\n\nUsers can search data using the following parameters:\n\n`dateType`, `startDate`, `endDate`, `date`, `companyDomain`, `companyName`, `companyIndustry`, `companyLocation`, `companyType`, `companyTicker`, `fundingRound`, `dealAmount`, `valuation`, `investor`, and `currency`.\n\nUsers can limit the number of records returned using the `limit` parameter. All parameters are optional.\n\nThe API key must be passed in the HTTP header as `x-api-key`.\n\nNote: Startup funding data is generally available for VC-funded private companies only. It is not available for public companies, non-VC-funded private companies, government entities, hospitals, universities, or other non-commercial organizations.","operationId":"getFundraisingDataset","parameters":[{"name":"x-api-key","in":"header","description":"Intellizence API key for authenticating the request.","required":true,"schema":{"type":"string"}}],"requestBody":{"description":"Intellizence Startup Funding Data request body","content":{"application/json":{"schema":{"$ref":"#/components/schemas/dataset_fundraising_body"}}}},"responses":{"200":{"description":"Successful response. Note: Credit fields (openingBalance, closingBalance, creditsConsumed) are returned only for Pay-Per-Use billing.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/FundraisingSearchResponse"}}}},"400":{"description":"400 - Bad Request\n\nBad request, possibly missing required parameters, invalid data, invalid or missing API key.\n\n- 701 - Invalid Start Date format (YYYY-MM-DD required)\n- 702 - Invalid End Date format (YYYY-MM-DD required)\n- 703 - Plan or resource not subscribed\n- 709 - No companies configured for this account\n- 710 - No triggers configured for this account"},"402":{"description":"402 - Payment Required\n\n- 704 - Payment is pending\n- 712 - Insufficient credits for this request"},"403":{"description":"403 - Forbidden\n\n- 706 - Requested resource not included in subscription plan\n- 707 - Subscription has expired\n- 708 - Start date outside subscription allowed range"},"406":{"description":"406 - Invalid Deal Amount Filter Format"},"407":{"description":"407 - Invalid Valuation Filter Format"},"500":{"description":"500 - Internal Server Error\n- 715 - Technical error occurred\n- 799 - Technical error occurred"}}}}},"components":{"schemas":{"dataset_fundraising_body":{"type":"object","properties":{"dateType":{"type":"string","description":"Choose the date type used to filter records.The default value is 'ANNOUNCED'. To get the daily update of records created or modified, 'LAST-MODIFIED' is recommended.","enum":["ANNOUNCED","LAST-MODIFIED"]},"startDate":{"type":"string","description":"The start date (YYYY-MM-DD) from which funding data is needed. The Intellizence Startup Funding Dataset contains data beginning from 2020-01-01.","format":"date"},"endDate":{"type":"string","description":"The end date (YYYY-MM-DD) up to which funding data is needed.","format":"date"},"date":{"type":"string","description":"Exact date (YYYY-MM-DD) for which the funding data is needed.","format":"date"},"companyName":{"type":"string","description":"The name(s) of the company for which the funding data is needed. Partial name matches are supported. Multiple values can be provided either as a comma-separated string or as an array."},"companyDomain":{"type":"string","description":"The website domain(s) of the company for which the funding data is needed. Partial website domain matches are supported. Multiple values can be provided either as a comma-separated string or as an array."},"companyIndustry":{"type":"string","description":"The industry or industries of companies for which funding data is needed. The industries are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided as an array.","enum":["accounting, audit & tax","advertising & communication","agriculture, animal husbandry & forestry","angels/ venture capital/ private equity","automobile","aviation","banking","bio-technology","business services","chemicals & fertilizers","clean technology","conglomerate","consulting","consumer products","consumer services","defence","distribution","e-commerce","economic development","education","energy & utilities","engineering, procurement & construction","financial services","gambling","gaming","government","healthcare","human resources","insurance","it services & outsourcing","legal","logistics & supply chain","manufacturing","media & entertainment","medical device","metals & mining","not-for-profit/ ngo","others","pharmaceuticals","publishing","railways","real estate","regulatory","restaurants & food services","retail","security","shipping & ports","spac/blank check","sports","technology","telecommunication","textiles","tourism & hospitality","trading","transportation"]},"companyLocation":{"type":"string","description":"The location of the company headquarters for which funding data is needed. The location can be city or state/province or country. Multiple values can be provided either as a comma-separated string or as an array."},"companyType":{"type":"string","description":"The type of company or organization for which funding data is needed. The company types are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Public","Private","Government/Regulator","Not-for-profit","Others"]},"companyTicker":{"type":"string","description":"Company Ticker if it's a public company."},"fundingRound":{"type":"string","description":"The funding round for which data is needed. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Angel","Crowdfunding","Pre-Seed","Seed","Post-Seed / Pre-Series A","Series A","Series B","Series C","Series D","Series E","Series F","Series G","Series H","Series I","Series J","Private Equity","Secondary Offering","Venture - Series Unknown","Debt Financing","Corporate Round","Grant"]},"dealAmount":{"pattern":"^(>|>=|<|<=|=|!=)?\\d+(,\\d+)?$","type":"number","description":"Filter the records by funding deal amount. Pass the `currency` whenver `dealAmount` is used. If `currency` is not provided along with `dealAmount`, all the records that matches the deal amount of any currency will be returned. The allowed operators are >, >=, <, <=,=,!=, (MinimumValue),(Maximum Value). Examples: >1000000, >=1000000, <1000000, <=1000000,=1000000,!=1000000, (1000000,400000)","format":"float"},"valuation":{"pattern":"^(>|>=|<|<=|=|!=)?\\d+(,\\d+)?$","type":"number","description":"Filter records based on company valuation. Valuation data is not available for all records and is typically provided only for companies with valuations in the billion-dollar range. The allowed operators are >, >=, <, <=,=,!=, (MinimumValue),(Maximum Value). Examples: >1000000, >=1000000, <1000000, <=1000000,=1000000,!=1000000, 1000000,400000","format":"float"},"investor":{"type":"string","description":"Name of the investor(s) who invested in this round. Partial name matches are supported. Multiple values can be provided either as a comma-separated string or as an array."},"currency":{"type":"string","description":"The currency of the deal transaction.","enum":["USD","CAD","EUR","GBP","INR","AUD","CHF","CNY","JPY","SEK"]},"limit":{"type":"integer","description":"The maximum number of records to be returned."}}},"FundraisingSearchResponse":{"required":["code","count","dataset"],"type":"object","properties":{"code":{"type":"integer"},"count":{"type":"integer"},"dataset":{"type":"array","items":{"$ref":"#/components/schemas/inline_response_200"}},"openingBalance":{"type":"integer","nullable":true},"closingBalance":{"type":"integer","nullable":true},"creditsConsumed":{"type":"integer","nullable":true}}},"inline_response_200":{"type":"object","properties":{"id":{"type":"string","description":"Unique ID of the record"},"announcedDate":{"type":"string","description":"Funding announced date","format":"date"},"company":{"$ref":"#/components/schemas/inline_response_200_company"},"fundingRound":{"type":"string","description":"Funding Round"},"investors":{"type":"string","description":"Name of the investors who invested in this round"},"leadInvestors":{"type":"string","description":"Name of the lead investors who invested in this round"},"dealAmount":{"type":"number","description":"The deal amount if publicly disclosed.","format":"float"},"valuation":{"type":"number","description":"The valuation amount if publicly disclosed.","format":"float"},"currency":{"type":"string","description":"The currency of the deal transaction."},"lastModified":{"type":"string","description":"The last modified date of the record.","format":"date"},"title":{"type":"string","description":"Source title - News or press release headline"},"url":{"type":"string","description":"URL of the source document"}}},"inline_response_200_company":{"type":"object","properties":{"name":{"type":"string","description":"Company or Venture name"},"domain":{"type":"string","description":"Company website domain"},"industries":{"type":"array","description":"Company industry classification by Intellizence","items":{"type":"string"}},"location":{"type":"string","description":"Company HQ location"},"ticker":{"type":"array","description":"Company stock ticker (if public)","items":{"type":"string"}},"type":{"type":"string","description":"Company type"}}}}}}
```

## The dataset\_fundraising\_body object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Startup Funding Signals API","version":"1.0"},"components":{"schemas":{"dataset_fundraising_body":{"type":"object","properties":{"dateType":{"type":"string","description":"Choose the date type used to filter records.The default value is 'ANNOUNCED'. To get the daily update of records created or modified, 'LAST-MODIFIED' is recommended.","enum":["ANNOUNCED","LAST-MODIFIED"]},"startDate":{"type":"string","description":"The start date (YYYY-MM-DD) from which funding data is needed. The Intellizence Startup Funding Dataset contains data beginning from 2020-01-01.","format":"date"},"endDate":{"type":"string","description":"The end date (YYYY-MM-DD) up to which funding data is needed.","format":"date"},"date":{"type":"string","description":"Exact date (YYYY-MM-DD) for which the funding data is needed.","format":"date"},"companyName":{"type":"string","description":"The name(s) of the company for which the funding data is needed. Partial name matches are supported. Multiple values can be provided either as a comma-separated string or as an array."},"companyDomain":{"type":"string","description":"The website domain(s) of the company for which the funding data is needed. Partial website domain matches are supported. Multiple values can be provided either as a comma-separated string or as an array."},"companyIndustry":{"type":"string","description":"The industry or industries of companies for which funding data is needed. The industries are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided as an array.","enum":["accounting, audit & tax","advertising & communication","agriculture, animal husbandry & forestry","angels/ venture capital/ private equity","automobile","aviation","banking","bio-technology","business services","chemicals & fertilizers","clean technology","conglomerate","consulting","consumer products","consumer services","defence","distribution","e-commerce","economic development","education","energy & utilities","engineering, procurement & construction","financial services","gambling","gaming","government","healthcare","human resources","insurance","it services & outsourcing","legal","logistics & supply chain","manufacturing","media & entertainment","medical device","metals & mining","not-for-profit/ ngo","others","pharmaceuticals","publishing","railways","real estate","regulatory","restaurants & food services","retail","security","shipping & ports","spac/blank check","sports","technology","telecommunication","textiles","tourism & hospitality","trading","transportation"]},"companyLocation":{"type":"string","description":"The location of the company headquarters for which funding data is needed. The location can be city or state/province or country. Multiple values can be provided either as a comma-separated string or as an array."},"companyType":{"type":"string","description":"The type of company or organization for which funding data is needed. The company types are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Public","Private","Government/Regulator","Not-for-profit","Others"]},"companyTicker":{"type":"string","description":"Company Ticker if it's a public company."},"fundingRound":{"type":"string","description":"The funding round for which data is needed. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Angel","Crowdfunding","Pre-Seed","Seed","Post-Seed / Pre-Series A","Series A","Series B","Series C","Series D","Series E","Series F","Series G","Series H","Series I","Series J","Private Equity","Secondary Offering","Venture - Series Unknown","Debt Financing","Corporate Round","Grant"]},"dealAmount":{"pattern":"^(>|>=|<|<=|=|!=)?\\d+(,\\d+)?$","type":"number","description":"Filter the records by funding deal amount. Pass the `currency` whenver `dealAmount` is used. If `currency` is not provided along with `dealAmount`, all the records that matches the deal amount of any currency will be returned. The allowed operators are >, >=, <, <=,=,!=, (MinimumValue),(Maximum Value). Examples: >1000000, >=1000000, <1000000, <=1000000,=1000000,!=1000000, (1000000,400000)","format":"float"},"valuation":{"pattern":"^(>|>=|<|<=|=|!=)?\\d+(,\\d+)?$","type":"number","description":"Filter records based on company valuation. Valuation data is not available for all records and is typically provided only for companies with valuations in the billion-dollar range. The allowed operators are >, >=, <, <=,=,!=, (MinimumValue),(Maximum Value). Examples: >1000000, >=1000000, <1000000, <=1000000,=1000000,!=1000000, 1000000,400000","format":"float"},"investor":{"type":"string","description":"Name of the investor(s) who invested in this round. Partial name matches are supported. Multiple values can be provided either as a comma-separated string or as an array."},"currency":{"type":"string","description":"The currency of the deal transaction.","enum":["USD","CAD","EUR","GBP","INR","AUD","CHF","CNY","JPY","SEK"]},"limit":{"type":"integer","description":"The maximum number of records to be returned."}}}}}}
```

## The inline\_response\_200 object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Startup Funding Signals API","version":"1.0"},"components":{"schemas":{"inline_response_200":{"type":"object","properties":{"id":{"type":"string","description":"Unique ID of the record"},"announcedDate":{"type":"string","description":"Funding announced date","format":"date"},"company":{"$ref":"#/components/schemas/inline_response_200_company"},"fundingRound":{"type":"string","description":"Funding Round"},"investors":{"type":"string","description":"Name of the investors who invested in this round"},"leadInvestors":{"type":"string","description":"Name of the lead investors who invested in this round"},"dealAmount":{"type":"number","description":"The deal amount if publicly disclosed.","format":"float"},"valuation":{"type":"number","description":"The valuation amount if publicly disclosed.","format":"float"},"currency":{"type":"string","description":"The currency of the deal transaction."},"lastModified":{"type":"string","description":"The last modified date of the record.","format":"date"},"title":{"type":"string","description":"Source title - News or press release headline"},"url":{"type":"string","description":"URL of the source document"}}},"inline_response_200_company":{"type":"object","properties":{"name":{"type":"string","description":"Company or Venture name"},"domain":{"type":"string","description":"Company website domain"},"industries":{"type":"array","description":"Company industry classification by Intellizence","items":{"type":"string"}},"location":{"type":"string","description":"Company HQ location"},"ticker":{"type":"array","description":"Company stock ticker (if public)","items":{"type":"string"}},"type":{"type":"string","description":"Company type"}}}}}}
```

## The inline\_response\_200\_company object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Startup Funding Signals API","version":"1.0"},"components":{"schemas":{"inline_response_200_company":{"type":"object","properties":{"name":{"type":"string","description":"Company or Venture name"},"domain":{"type":"string","description":"Company website domain"},"industries":{"type":"array","description":"Company industry classification by Intellizence","items":{"type":"string"}},"location":{"type":"string","description":"Company HQ location"},"ticker":{"type":"array","description":"Company stock ticker (if public)","items":{"type":"string"}},"type":{"type":"string","description":"Company type"}}}}}}
```


# Intellizence Startup Funding API Sample Requests

Explore sample requests for the Intellizence Startup Funding API. Learn how to retrieve startup funding and venture capital records by date, company domain, investor, industry, location, funding round

## Startup Funding API Sample Requests

Use these sample API requests to retrieve startup funding, venture capital, and investment deal records from the Intellizence Startup Funding Dataset.

These examples show common ways to filter startup funding records by date, company domain, investor, industry, location, funding round, deal amount, valuation, and currency.

{% hint style="info" %}
All request parameters are optional. You can use a single filter or combine multiple filters based on your use case.
{% endhint %}

***

### Endpoint

```http
POST https://connect.intellizence.com/api/dataset/fundraising
```

### Authentication

Include your API key in the request header.

```http
x-api-key: YOUR_API_KEY
```

### Content Type

```http
Content-Type: application/json
```

***

## Sample API Requests

### 1. Get Daily Updated Records

Use `dateType: "LAST-MODIFIED"` to retrieve records that were created or updated on a specific date.

This is recommended for daily syncs, alerts, enrichment workflows, and automated data pipelines.

#### Request Body

```json
{
  "dateType": "LAST-MODIFIED",
  "date": "2025-03-03",
  "limit": 5
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/fundraising \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "LAST-MODIFIED",
    "date": "2025-03-03",
    "limit": 5
  }'
```

***

### 2. Get Funding Deals Announced on a Specific Date

Use `dateType: "ANNOUNCED"` and `date` to retrieve startup funding deals announced on a specific date.

#### Request Body

```json
{
  "dateType": "ANNOUNCED",
  "date": "2025-03-03",
  "limit": 10
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/fundraising \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "ANNOUNCED",
    "date": "2025-03-03",
    "limit": 10
  }'
```

***

### 3. Get Funding Deals Within a Date Range

Use `startDate` and `endDate` to retrieve startup funding deals announced during a specific period.

#### Request Body

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-03-01",
  "endDate": "2025-03-31",
  "limit": 25
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/fundraising \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "ANNOUNCED",
    "startDate": "2025-03-01",
    "endDate": "2025-03-31",
    "limit": 25
  }'
```

***

### 4. Search by Company Domain

Use `companyDomain` to retrieve funding records for a specific company website domain.

This is recommended for CRM enrichment, account matching, data pipelines, and workflow automation because domains are usually more precise than company names.

#### Request Body

```json
{
  "companyDomain": "anthropic.com",
  "limit": 10
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/fundraising \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyDomain": "anthropic.com",
    "limit": 10
  }'
```

***

### 5. Search by Investor

Use `investor` to retrieve funding deals involving a specific investor, venture capital firm, private equity firm, corporate investor, or strategic backer.

This is useful for investor tracking, competitive intelligence, deal sourcing analysis, and market research.

#### Request Body

```json
{
  "investor": "Lightspeed Venture Partners",
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/fundraising \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "investor": "Lightspeed Venture Partners",
    "limit": 20
  }'
```

***

### 6. Search by Company Industry

Use `companyIndustry` to retrieve funding deals for companies in one or more industries.

This is useful for sector research, market mapping, investment research, and prospecting.

#### Request Body

```json
{
  "companyIndustry": [
    "technology",
    "healthcare"
  ],
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/fundraising \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyIndustry": [
      "technology",
      "healthcare"
    ],
    "limit": 20
  }'
```

***

### 7. Search by Company Location

Use `companyLocation` to find funding deals involving companies headquartered in a specific city, state, province, country, or region.

#### Request Body

```json
{
  "companyLocation": "San Francisco,California,United States of America",
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/fundraising \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyLocation": "San Francisco,California,United States of America",
    "limit": 20
  }'
```

***

### 8. Search by Funding Round

Use `fundingRound` to retrieve deals by funding stage.

Examples include `Seed`, `Series A`, `Series B`, `Series C`, `Series D`, `Series E`, `Private Equity`, `Debt Financing`, and `Corporate Round`.

#### Request Body

```json
{
  "fundingRound": [
    "Series A",
    "Series B"
  ],
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/fundraising \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "fundingRound": [
      "Series A",
      "Series B"
    ],
    "limit": 20
  }'
```

***

### 9. Search by Funding Amount

Use `dealAmount` to filter funding deals by transaction value.

You can use comparison operators such as `>`, `>=`, `<`, `<=`, `=`, and `!=`.

When filtering by deal amount, include `currency` for more precise results.

#### Request Body

```json
{
  "dealAmount": ">100000000",
  "currency": "USD",
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/fundraising \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dealAmount": ">100000000",
    "currency": "USD",
    "limit": 20
  }'
```

***

### 10. Use Multiple Filters Together

Combine filters to narrow results by date range, industry, funding round, funding amount, investor, company type, and currency.

#### Request Body

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-01-01",
  "endDate": "2025-03-31",
  "companyIndustry": [
    "technology"
  ],
  "companyType": [
    "Private"
  ],
  "fundingRound": [
    "Series B",
    "Series C"
  ],
  "dealAmount": ">50000000",
  "currency": "USD",
  "limit": 50
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/fundraising \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "ANNOUNCED",
    "startDate": "2025-01-01",
    "endDate": "2025-03-31",
    "companyIndustry": [
      "technology"
    ],
    "companyType": [
      "Private"
    ],
    "fundingRound": [
      "Series B",
      "Series C"
    ],
    "dealAmount": ">50000000",
    "currency": "USD",
    "limit": 50
  }'
```

***

## Use Case Examples

### 1. Daily Data Sync

Use this example when you want to pull newly added or updated startup funding records into your application, database, CRM, or analytics workflow.

#### Recommended Filters

```json
{
  "dateType": "LAST-MODIFIED",
  "date": "2025-03-03",
  "limit": 100
}
```

#### Best For

* Data pipelines
* Daily refreshes
* Internal dashboards
* Alerts and workflow automation
* CRM and data warehouse enrichment

***

### 2. CRM or Account Enrichment

Use this example to check whether a company in your CRM has recent funding activity.

#### Recommended Filters

```json
{
  "companyDomain": "anthropic.com",
  "dateType": "LAST-MODIFIED",
  "startDate": "2025-01-01",
  "endDate": "2025-03-31",
  "limit": 10
}
```

#### Best For

* CRM enrichment
* Account scoring
* Sales intelligence
* Customer intelligence
* Signal-based selling workflows

***

### 3. Investment Research

Use this example to track large funding rounds in a specific sector.

#### Recommended Filters

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-01-01",
  "endDate": "2025-12-31",
  "companyIndustry": [
    "healthcare"
  ],
  "dealAmount": ">100000000",
  "currency": "USD",
  "limit": 50
}
```

#### Best For

* Market mapping
* Sector research
* Funding trend analysis
* Venture capital research
* Private equity and growth equity research

***

### 4. Investor Tracking

Use this example to monitor funding deals involving a specific investor.

#### Recommended Filters

```json
{
  "investor": "Lightspeed Venture Partners",
  "dateType": "ANNOUNCED",
  "startDate": "2025-01-01",
  "endDate": "2025-12-31",
  "limit": 25
}
```

#### Best For

* Investor activity tracking
* Competitive intelligence
* Venture capital market research
* Deal sourcing analysis
* Relationship mapping

***

### 5. Sales and Prospecting

Use this example to identify recently funded companies that may have new budgets, hiring plans, expansion needs, or vendor requirements.

#### Recommended Filters

```json
{
  "dateType": "LAST-MODIFIED",
  "startDate": "2025-01-01",
  "endDate": "2025-03-31",
  "companyIndustry": [
    "technology"
  ],
  "fundingRound": [
    "Series A",
    "Series B",
    "Series C"
  ],
  "dealAmount": ">10000000",
  "currency": "USD",
  "limit": 25
}
```

#### Best For

* Prospecting
* Account prioritization
* Trigger-based outreach
* Sales and marketing campaigns
* Go-to-market workflows

***

## Recommended Use Cases

| Use Case              | Recommended Filters                                         |
| --------------------- | ----------------------------------------------------------- |
| Daily data sync       | `dateType`, `date`, `limit`                                 |
| CRM enrichment        | `companyDomain`, `dateType`, `startDate`, `endDate`         |
| Investment research   | `companyIndustry`, date range, `dealAmount`, `currency`     |
| Investor tracking     | `investor`, date range, `limit`                             |
| Sales and prospecting | `companyIndustry`, `fundingRound`, `dealAmount`, `currency` |

***

## Best Practices

### Prefer company domain for company matching

For CRM enrichment, data pipelines, account matching, and automated workflows, use `companyDomain` when available.

Company domains are usually more precise than company names and help reduce duplicate or ambiguous matches.

```json
{
  "companyDomain": "anthropic.com",
  "limit": 10
}
```

### Use company name for manual lookup

You can also use `companyName` to search for funding records by company name.

Company name search is useful for manual lookup, but for automated workflows, CRM enrichment, and account matching, use `companyDomain` when available.

```json
{
  "companyName": "Anthropic",
  "limit": 10
}
```

### Use `LAST-MODIFIED` for daily syncs

For recurring syncs, alerts, and automated workflows, use `LAST-MODIFIED`.

```json
{
  "dateType": "LAST-MODIFIED",
  "date": "2025-03-03"
}
```

This helps retrieve records that were newly added or updated on that date.

### Use `ANNOUNCED` for event-date research

For research based on when a funding deal was announced, use `ANNOUNCED`.

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-01-01",
  "endDate": "2025-03-31"
}
```

### Use funding rounds for stage-based filtering

Use `fundingRound` when you want to filter companies by investment stage.

```json
{
  "fundingRound": [
    "Seed",
    "Series A",
    "Series B"
  ],
  "limit": 25
}
```

### Use `dealAmount` with `currency`

When filtering by funding amount, include `currency` for more precise results.

```json
{
  "dealAmount": ">50000000",
  "currency": "USD",
  "limit": 25
}
```

### Use `valuation` for high-valuation company research

Valuation data may not be available for every record. It is typically available for selected companies, especially larger funding rounds or companies with billion-dollar valuations.

```json
{
  "valuation": ">1000000000",
  "currency": "USD",
  "limit": 25
}
```

### Use `limit` to control result size

The default limit is `100` records if no limit is provided.

```json
{
  "limit": 100
}
```

### Combine filters for more precise results

You can combine multiple filters in a single request to narrow your results.

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-01-01",
  "endDate": "2025-03-31",
  "companyIndustry": [
    "technology"
  ],
  "fundingRound": [
    "Series B"
  ],
  "dealAmount": ">50000000",
  "currency": "USD",
  "limit": 50
}
```

***

## Notes

* All parameters are optional.
* Dates should be provided in `YYYY-MM-DD` format.
* Use `LAST-MODIFIED` when you want newly added or updated records.
* Use `ANNOUNCED` when you want records based on the funding announcement date.
* Use `companyDomain` for CRM matching, account enrichment, and workflow automation.
* Use `companyName` for manual lookup when the company domain is not available.
* Include `currency` when filtering by `dealAmount` or `valuation`.
* Use `companyIndustry`, `companyLocation`, and `fundingRound` for market research, investment research, and prospecting.
* Startup funding data is generally available for VC-funded private companies only.


# Intellizence Layoffs Signals API

This REST API provides continuous access to ongoing and historical layoffs, downsizing and  job cuts signals from the Intellizence Layoffs Dataset.

{% hint style="info" %}
Best  suited for :

* Continuous monitoring of layoff and downsizing announcements
* Trigger alerts and automated workflows
* Layoff trends & analysis
* Power AI agents and internal intelligence platforms
  {% endhint %}

> **Ready to get started?** [**Request your API key**](https://intellizence.com/api-trial/) and start building.\
> **Questions?** [**Schedule a call**](https://intellizence.com/schedule-a-demo/) or email us at <sales@intellizence.com>.

**Security Notice:**  Please keep API Key secure. Do not share your API key in publicly accessible areas such as GitHub, client-side code, and so forth.

## Submit a request to get the Layoff records

> This REST API endpoint provides access to both ongoing and historical layoff data from the Intellizence Layoffs Dataset. Data access is limited to records within your subscription's entitled date range.\
> \
> Users can search data using the following parameters:\
> \
> \`dateType\`, \`startDate\`, \`endDate\`, \`date\`, \`companyDomain\`, \`companyName\`, \`companyIndustry\`, \`companyLocation\`, \`companyType\`, \`companyTicker\`, \`layoffType\`, \`layoffLocation\`, and \`layoffReason\`.\
> \
> Users can limit the number of records returned using the \`limit\` parameter. All parameters are optional.\
> \
> The API key must be passed in the HTTP header as \`x-api-key\`.

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Layoffs Signals API","version":"1.0"},"servers":[{"url":"https://connect.intellizence.com"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","name":"x-api-key","in":"header"}},"schemas":{"dataset_layoff_body":{"type":"object","properties":{"dateType":{"type":"string","description":"Choose the date type used to filter records.The default value is 'ANNOUNCED'. To get the daily update of records created or modified, 'LAST-MODIFIED' is recommended.","enum":["ANNOUNCED","LAST-MODIFIED"]},"startDate":{"type":"string","description":"The start date (YYYY-MM-DD) from which layoff data is needed. The Intellizence Layoff Dataset contains data beginning from 2020-01-01.","format":"date"},"endDate":{"type":"string","description":"The end date (YYYY-MM-DD) up to which layoff data is needed.","format":"date"},"date":{"type":"string","description":"Exact date (YYYY-MM-DD) for which the layoff data is needed.","format":"date"},"companyName":{"type":"string","description":"Name(s) of the company for which layoff data is needed.Partial name matching is supported.Multiple values can be provided either as a comma-separated string or as an array."},"companyDomain":{"type":"string","description":"The website domain(s) of the company for which the layoff data is needed. Partial domain matching is supported. Multiple values can be provided either as a comma-separated string or as an array."},"companyIndustry":{"type":"string","description":"The industry or industries of the companies for which layoff data is requested. Industries are predefined by Intellizence, and only the values listed below are supported. Multiple values can be provided as an array.","enum":["accounting, audit & tax","advertising & communication","agriculture, animal husbandry & forestry","angels/ venture capital/ private equity","automobile","aviation","banking","bio-technology","business services","chemicals & fertilizers","clean technology","conglomerate","consulting","consumer products","consumer services","defence","distribution","e-commerce","economic development","education","energy & utilities","engineering, procurement & construction","financial services","gambling","gaming","government","healthcare","human resources","insurance","it services & outsourcing","legal","logistics & supply chain","manufacturing","media & entertainment","medical device","metals & mining","not-for-profit/ ngo","others","pharmaceuticals","publishing","railways","real estate","regulatory","restaurants & food services","retail","security","shipping & ports","spac/blank check","sports","technology","telecommunication","textiles","tourism & hospitality","trading","transportation"]},"companyLocation":{"type":"string","description":"The location of the company headquarters for which layoff data is needed. The location can be specified as a city, state/province, or country. Multiple values can be provided either as a comma-separated string or as an array."},"companyType":{"type":"string","description":"The type of company or organization for which layoff data is needed. The company types are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Public","Private","Government/Regulator","Not-for-profit","Others"]},"companyTicker":{"type":"string","description":"Stock ticker of the company"},"layoffType":{"type":"string","description":"The type of layoff/job cut. The layoff types are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Downsizing/Layoff","Furlough/Temporary","Hiring Freeze","Voluntary Retirement","Temporary Plant Closure","Permanent Plant Closure","Voluntary Separation Program","Other"]},"layoffReason":{"type":"string","description":"Layoff reason mentioned in the source. The layoff reasons are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Economic Crisis","Pandemic","Restructuring","Cost-cutting","M&A","Automation","Outsourcing","Privatization","Trade Tariff/Treaty","Business Closure","Relocation","Not Specified","Divestment","Contract Loss","Loss of Funding","Sales Decline","Other","Bankruptcy","Financial Distress","Production Cut","Employee Strike","IPO","Staff Redundancies","Voluntary Dismissal","Employees Performance Metrics","Strategic and Business Changes","Annual Review Process","AI Automation","Natural Disaster"]},"layoffLocation":{"type":"string","description":"The location of the company where layoff was announced. The location can be city or state/province or country. Multiple values can be provided either as a comma-separated string or as an array."},"limit":{"type":"integer","description":"The maximum number of records to be returned."}}},"LayoffSearchResponse":{"required":["code","count","dataset"],"type":"object","properties":{"code":{"type":"integer"},"count":{"type":"integer"},"dataset":{"type":"array","items":{"$ref":"#/components/schemas/inline_response_200"}},"openingBalance":{"type":"integer","nullable":true},"closingBalance":{"type":"integer","nullable":true},"creditsConsumed":{"type":"integer","nullable":true}}},"inline_response_200":{"type":"object","properties":{"id":{"type":"string","description":"Unique ID of the record"},"announcedDate":{"type":"string","description":"Date of layoff announcement","format":"date"},"company":{"$ref":"#/components/schemas/inline_response_200_company"},"count":{"type":"number","description":"Number of employees laid off, if disclosed as absolute number.","format":"float"},"percent":{"type":"string","description":"Percentage of employees laid off, if disclosed as percentage.","format":"float"},"location":{"$ref":"#/components/schemas/inline_response_200_location"},"layoffType":{"type":"array","description":"Type of layoff/job cut","items":{"type":"string"}},"layoffReason":{"type":"array","description":"Layoff reason mentioned in the source","items":{"type":"string"}},"businessDivision":{"type":"string","description":"Business Division where the layoff was announced"},"sourceType":{"type":"string","description":"Source type of the layoff announcement - WARN Filings, News/Press Wires. The values for this data point are available only for records that were created after May 1st, 2025."},"lastModified":{"type":"string","description":"The last modified date of the record.","format":"date"},"title":{"type":"string","description":"Source title - News or press release or WARN Notice headline"},"url":{"type":"string","description":"URL of the source document"}}},"inline_response_200_company":{"type":"object","properties":{"name":{"type":"string","description":"Company name"},"domain":{"type":"string","description":"Company website domain"},"industries":{"type":"array","description":"Company industry classification by Intellizence","items":{"type":"string"}},"location":{"type":"string","description":"Company HQ location"},"type":{"type":"string","description":"Company type"},"ticker":{"type":"array","description":"Company stock ticker (if public)","items":{"type":"string"}},"stockExchange":{"type":"array","description":"Stock exchange where the company is listed (if public)","items":{"type":"string"}}}},"inline_response_200_location":{"type":"object","properties":{"country":{"type":"string"},"state":{"type":"string"},"city":{"type":"string"}},"description":"Layoff location"}}},"paths":{"/api/dataset/layoff":{"post":{"summary":"Submit a request to get the Layoff records","description":"This REST API endpoint provides access to both ongoing and historical layoff data from the Intellizence Layoffs Dataset. Data access is limited to records within your subscription's entitled date range.\n\nUsers can search data using the following parameters:\n\n`dateType`, `startDate`, `endDate`, `date`, `companyDomain`, `companyName`, `companyIndustry`, `companyLocation`, `companyType`, `companyTicker`, `layoffType`, `layoffLocation`, and `layoffReason`.\n\nUsers can limit the number of records returned using the `limit` parameter. All parameters are optional.\n\nThe API key must be passed in the HTTP header as `x-api-key`.","operationId":"getLayoffDataset","parameters":[{"name":"x-api-key","in":"header","description":"Intellizence API key for authenticating the request.","required":true,"schema":{"type":"string"}}],"requestBody":{"description":"Intellizence Layoff Dataset request body","content":{"application/json":{"schema":{"$ref":"#/components/schemas/dataset_layoff_body"}}}},"responses":{"200":{"description":"Successful response.\n\nNote: Credit fields (openingBalance, closingBalance, creditsConsumed) are returned only for Pay-Per-Use billing.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/LayoffSearchResponse"}}}},"400":{"description":"400 - Bad Request\n\nBad request, possibly missing required parameters, invalid data, invalid or missing API key.\n\n- 701 - Start Date is not in YYYY-MM-DD format.\n- 702 - End Date is not in YYYY-MM-DD format.\n- 703 - Plan or resource not subscribed\n- 709 - No companies configured for this account.\n- 710 - No triggers configured for this account."},"402":{"description":"402 - Payment Required\n\n- 704 - Payment is pending.\n- 712 - Insufficient credits for this request."},"403":{"description":"403 - Forbidden\n\n- 707 - Subscription has expired.\n- 708 - Start date is outside your subscription's allowed date range."},"500":{"description":"500 - Internal Server Error\n\n- 715 - A technical error occurred.\n- 799 - A technical error occurred."}}}}}}
```

## The dataset\_layoff\_body object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Layoffs Signals API","version":"1.0"},"components":{"schemas":{"dataset_layoff_body":{"type":"object","properties":{"dateType":{"type":"string","description":"Choose the date type used to filter records.The default value is 'ANNOUNCED'. To get the daily update of records created or modified, 'LAST-MODIFIED' is recommended.","enum":["ANNOUNCED","LAST-MODIFIED"]},"startDate":{"type":"string","description":"The start date (YYYY-MM-DD) from which layoff data is needed. The Intellizence Layoff Dataset contains data beginning from 2020-01-01.","format":"date"},"endDate":{"type":"string","description":"The end date (YYYY-MM-DD) up to which layoff data is needed.","format":"date"},"date":{"type":"string","description":"Exact date (YYYY-MM-DD) for which the layoff data is needed.","format":"date"},"companyName":{"type":"string","description":"Name(s) of the company for which layoff data is needed.Partial name matching is supported.Multiple values can be provided either as a comma-separated string or as an array."},"companyDomain":{"type":"string","description":"The website domain(s) of the company for which the layoff data is needed. Partial domain matching is supported. Multiple values can be provided either as a comma-separated string or as an array."},"companyIndustry":{"type":"string","description":"The industry or industries of the companies for which layoff data is requested. Industries are predefined by Intellizence, and only the values listed below are supported. Multiple values can be provided as an array.","enum":["accounting, audit & tax","advertising & communication","agriculture, animal husbandry & forestry","angels/ venture capital/ private equity","automobile","aviation","banking","bio-technology","business services","chemicals & fertilizers","clean technology","conglomerate","consulting","consumer products","consumer services","defence","distribution","e-commerce","economic development","education","energy & utilities","engineering, procurement & construction","financial services","gambling","gaming","government","healthcare","human resources","insurance","it services & outsourcing","legal","logistics & supply chain","manufacturing","media & entertainment","medical device","metals & mining","not-for-profit/ ngo","others","pharmaceuticals","publishing","railways","real estate","regulatory","restaurants & food services","retail","security","shipping & ports","spac/blank check","sports","technology","telecommunication","textiles","tourism & hospitality","trading","transportation"]},"companyLocation":{"type":"string","description":"The location of the company headquarters for which layoff data is needed. The location can be specified as a city, state/province, or country. Multiple values can be provided either as a comma-separated string or as an array."},"companyType":{"type":"string","description":"The type of company or organization for which layoff data is needed. The company types are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Public","Private","Government/Regulator","Not-for-profit","Others"]},"companyTicker":{"type":"string","description":"Stock ticker of the company"},"layoffType":{"type":"string","description":"The type of layoff/job cut. The layoff types are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Downsizing/Layoff","Furlough/Temporary","Hiring Freeze","Voluntary Retirement","Temporary Plant Closure","Permanent Plant Closure","Voluntary Separation Program","Other"]},"layoffReason":{"type":"string","description":"Layoff reason mentioned in the source. The layoff reasons are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Economic Crisis","Pandemic","Restructuring","Cost-cutting","M&A","Automation","Outsourcing","Privatization","Trade Tariff/Treaty","Business Closure","Relocation","Not Specified","Divestment","Contract Loss","Loss of Funding","Sales Decline","Other","Bankruptcy","Financial Distress","Production Cut","Employee Strike","IPO","Staff Redundancies","Voluntary Dismissal","Employees Performance Metrics","Strategic and Business Changes","Annual Review Process","AI Automation","Natural Disaster"]},"layoffLocation":{"type":"string","description":"The location of the company where layoff was announced. The location can be city or state/province or country. Multiple values can be provided either as a comma-separated string or as an array."},"limit":{"type":"integer","description":"The maximum number of records to be returned."}}}}}}
```

## The inline\_response\_200 object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Layoffs Signals API","version":"1.0"},"components":{"schemas":{"inline_response_200":{"type":"object","properties":{"id":{"type":"string","description":"Unique ID of the record"},"announcedDate":{"type":"string","description":"Date of layoff announcement","format":"date"},"company":{"$ref":"#/components/schemas/inline_response_200_company"},"count":{"type":"number","description":"Number of employees laid off, if disclosed as absolute number.","format":"float"},"percent":{"type":"string","description":"Percentage of employees laid off, if disclosed as percentage.","format":"float"},"location":{"$ref":"#/components/schemas/inline_response_200_location"},"layoffType":{"type":"array","description":"Type of layoff/job cut","items":{"type":"string"}},"layoffReason":{"type":"array","description":"Layoff reason mentioned in the source","items":{"type":"string"}},"businessDivision":{"type":"string","description":"Business Division where the layoff was announced"},"sourceType":{"type":"string","description":"Source type of the layoff announcement - WARN Filings, News/Press Wires. The values for this data point are available only for records that were created after May 1st, 2025."},"lastModified":{"type":"string","description":"The last modified date of the record.","format":"date"},"title":{"type":"string","description":"Source title - News or press release or WARN Notice headline"},"url":{"type":"string","description":"URL of the source document"}}},"inline_response_200_company":{"type":"object","properties":{"name":{"type":"string","description":"Company name"},"domain":{"type":"string","description":"Company website domain"},"industries":{"type":"array","description":"Company industry classification by Intellizence","items":{"type":"string"}},"location":{"type":"string","description":"Company HQ location"},"type":{"type":"string","description":"Company type"},"ticker":{"type":"array","description":"Company stock ticker (if public)","items":{"type":"string"}},"stockExchange":{"type":"array","description":"Stock exchange where the company is listed (if public)","items":{"type":"string"}}}},"inline_response_200_location":{"type":"object","properties":{"country":{"type":"string"},"state":{"type":"string"},"city":{"type":"string"}},"description":"Layoff location"}}}}
```

## The inline\_response\_200\_company object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Layoffs Signals API","version":"1.0"},"components":{"schemas":{"inline_response_200_company":{"type":"object","properties":{"name":{"type":"string","description":"Company name"},"domain":{"type":"string","description":"Company website domain"},"industries":{"type":"array","description":"Company industry classification by Intellizence","items":{"type":"string"}},"location":{"type":"string","description":"Company HQ location"},"type":{"type":"string","description":"Company type"},"ticker":{"type":"array","description":"Company stock ticker (if public)","items":{"type":"string"}},"stockExchange":{"type":"array","description":"Stock exchange where the company is listed (if public)","items":{"type":"string"}}}}}}}
```

## The inline\_response\_200\_location object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Layoffs Signals API","version":"1.0"},"components":{"schemas":{"inline_response_200_location":{"type":"object","properties":{"country":{"type":"string"},"state":{"type":"string"},"city":{"type":"string"}},"description":"Layoff location"}}}}
```


# Intellizence Layoffs API Sample Requests

Sample requests for the Intellizence Layoffs API, including filters for date, company domain, industry, company location, layoff location, company type, ticker, layoff type, layoff reason, and limit.

## Layoffs API Sample Requests

Use these sample API requests to retrieve layoff, downsizing, workforce reduction, plant closure, furlough, and job cut records from the Intellizence Layoffs Dataset.

These examples show common ways to filter layoff records by date, company domain, industry, company location, layoff location, company type, ticker, layoff type, layoff reason, and limit.

{% hint style="info" %}
All request parameters are optional. You can use a single filter or combine multiple filters based on your use case.
{% endhint %}

***

### Endpoint

```http
POST https://connect.intellizence.com/api/dataset/layoff
```

### Authentication

Include your API key in the request header.

```http
x-api-key: YOUR_API_KEY
```

### Content Type

```http
Content-Type: application/json
```

***

## Sample API Requests

### 1. Get Daily Updated Records

Use `dateType: "LAST-MODIFIED"` to retrieve records that were created or updated on a specific date.

This is recommended for daily syncs, alerts, enrichment workflows, and automated data pipelines.

#### Request Body

```json
{
  "dateType": "LAST-MODIFIED",
  "date": "2026-03-03",
  "limit": 5
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/layoff \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "LAST-MODIFIED",
    "date": "2026-03-03",
    "limit": 5
  }'
```

***

### 2. Get Layoffs Announced on a Specific Date

Use `dateType: "ANNOUNCED"` and `date` to retrieve layoff records announced on a specific date.

#### Request Body

```json
{
  "dateType": "ANNOUNCED",
  "date": "2026-03-03",
  "limit": 10
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/layoff \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "ANNOUNCED",
    "date": "2026-03-03",
    "limit": 10
  }'
```

***

### 3. Get Layoffs Within a Date Range

Use `startDate` and `endDate` to retrieve layoffs announced during a specific period.

The Intellizence Layoffs Dataset contains data beginning from `2020-01-01`.

#### Request Body

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2026-03-01",
  "endDate": "2026-03-31",
  "limit": 25
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/layoff \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "ANNOUNCED",
    "startDate": "2026-03-01",
    "endDate": "2026-03-31",
    "limit": 25
  }'
```

***

### 4. Search by Company Domain

Use `companyDomain` to retrieve layoff records for a specific company website domain.

This is recommended for CRM enrichment, account matching, risk monitoring, data pipelines, and workflow automation because domains are usually more precise than company names.

#### Request Body

```json
{
  "companyDomain": "dteenergy.com",
  "limit": 10
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/layoff \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyDomain": "dteenergy.com",
    "limit": 10
  }'
```

***

### 5. Search by Company Industry

Use `companyIndustry` to retrieve layoff records for companies in one or more industries.

This is useful for market research, sector monitoring, risk analysis, workforce trend analysis, and investment research.

#### Request Body

```json
{
  "companyIndustry": [
    "technology",
    "retail"
  ],
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/layoff \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyIndustry": [
      "technology",
      "retail"
    ],
    "limit": 20
  }'
```

***

### 6. Search by Company Location

Use `companyLocation` to find layoff records for companies headquartered in a specific city, state, province, country, or region.

#### Request Body

```json
{
  "companyLocation": "Detroit,Michigan,United States of America",
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/layoff \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyLocation": "Detroit,Michigan,United States of America",
    "limit": 20
  }'
```

***

### 7. Search by Layoff Location

Use `layoffLocation` to find layoff events announced for a specific location.

This is useful when you want to track workforce reductions by plant, office, city, state, province, country, or region.

#### Request Body

```json
{
  "layoffLocation": "Superior,Wisconsin,United States of America",
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/layoff \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "layoffLocation": "Superior,Wisconsin,United States of America",
    "limit": 20
  }'
```

***

### 8. Search by Layoff Type

Use `layoffType` to retrieve layoffs by event type.

Examples include `Downsizing/Layoff`, `Furlough/Temporary`, `Hiring Freeze`, `Permanent Plant Closure`, `Temporary Plant Closure`, `Voluntary Retirement`, `Voluntary Separation Program`, and `Other`.

#### Request Body

```json
{
  "layoffType": [
    "Downsizing/Layoff",
    "Permanent Plant Closure"
  ],
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/layoff \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "layoffType": [
      "Downsizing/Layoff",
      "Permanent Plant Closure"
    ],
    "limit": 20
  }'
```

***

### 9. Search by Layoff Reason

Use `layoffReason` to retrieve layoffs by the reason mentioned in the source.

Examples include `Restructuring`, `Cost-cutting`, `M&A`, `Automation`, `Business Closure`, `Relocation`, `Bankruptcy`, `Financial Distress`, `AI Automation`, and `Not Specified`.

#### Request Body

```json
{
  "layoffReason": [
    "Restructuring",
    "Cost-cutting"
  ],
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/layoff \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "layoffReason": [
      "Restructuring",
      "Cost-cutting"
    ],
    "limit": 20
  }'
```

***

### 10. Use Multiple Filters Together

Combine filters to narrow results by date range, industry, company type, layoff type, layoff reason, and location.

#### Request Body

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2026-01-01",
  "endDate": "2026-03-31",
  "companyIndustry": [
    "technology"
  ],
  "companyType": [
    "Public"
  ],
  "layoffType": [
    "Downsizing/Layoff"
  ],
  "layoffReason": [
    "Restructuring",
    "Cost-cutting"
  ],
  "layoffLocation": "United States of America",
  "limit": 50
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/layoff \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "ANNOUNCED",
    "startDate": "2026-01-01",
    "endDate": "2026-03-31",
    "companyIndustry": [
      "technology"
    ],
    "companyType": [
      "Public"
    ],
    "layoffType": [
      "Downsizing/Layoff"
    ],
    "layoffReason": [
      "Restructuring",
      "Cost-cutting"
    ],
    "layoffLocation": "United States of America",
    "limit": 50
  }'
```

***

## Use Case Examples

### 1. Daily Data Sync

Use this example when you want to pull newly added or updated layoff records into your application, database, CRM, dashboard, or analytics workflow.

#### Recommended Filters

```json
{
  "dateType": "LAST-MODIFIED",
  "date": "2026-03-03",
  "limit": 100
}
```

#### Best For

* Data pipelines
* Daily refreshes
* Internal dashboards
* Alerts and workflow automation
* CRM and data warehouse enrichment

***

### 2. CRM or Account Risk Enrichment

Use this example to check whether a company in your CRM has recent layoff activity.

#### Recommended Filters

```json
{
  "companyDomain": "dteenergy.com",
  "dateType": "LAST-MODIFIED",
  "startDate": "2026-01-01",
  "endDate": "2026-03-31",
  "limit": 10
}
```

#### Best For

* CRM enrichment
* Account risk scoring
* Customer health monitoring
* Sales and customer success workflows
* Renewal and churn risk monitoring

***

### 3. Sector Workforce Trend Analysis

Use this example to track layoff activity across a specific industry.

#### Recommended Filters

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2026-01-01",
  "endDate": "2026-03-31",
  "companyIndustry": [
    "technology"
  ],
  "limit": 50
}
```

#### Best For

* Workforce trend analysis
* Market research
* Sector monitoring
* Investment research
* Competitive intelligence

***

### 4. WARN and Plant Closure Monitoring

Use this example to monitor plant closures, facility shutdowns, and location-specific workforce reductions.

#### Recommended Filters

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2026-01-01",
  "endDate": "2026-03-31",
  "layoffType": [
    "Permanent Plant Closure",
    "Temporary Plant Closure"
  ],
  "layoffLocation": "United States of America",
  "limit": 50
}
```

#### Best For

* WARN notice monitoring
* Plant closure tracking
* Economic development research
* Supply chain risk monitoring
* Location-based workforce analysis

***

### 5. Sales and Customer Success Monitoring

Use this example to identify accounts going through restructuring, cost-cutting, or workforce reductions.

#### Recommended Filters

```json
{
  "dateType": "LAST-MODIFIED",
  "startDate": "2026-01-01",
  "endDate": "2026-03-31",
  "companyIndustry": [
    "technology"
  ],
  "layoffReason": [
    "Restructuring",
    "Cost-cutting",
    "Financial Distress"
  ],
  "limit": 25
}
```

#### Best For

* Account prioritization
* Customer risk monitoring
* Renewal risk detection
* Signal-based outreach
* Churn and downsell risk workflows

***

## Recommended Use Cases

| Use Case                              | Recommended Filters                                 |
| ------------------------------------- | --------------------------------------------------- |
| Daily data sync                       | `dateType`, `date`, `limit`                         |
| CRM or account risk enrichment        | `companyDomain`, `dateType`, `startDate`, `endDate` |
| Sector workforce trend analysis       | `companyIndustry`, date range, `limit`              |
| WARN and plant closure monitoring     | `layoffType`, `layoffLocation`, date range          |
| Sales and customer success monitoring | `companyIndustry`, `layoffReason`, date range       |

***

## Best Practices

### Prefer company domain for company matching

For CRM enrichment, data pipelines, account matching, and automated workflows, use `companyDomain` when available.

Company domains are usually more precise than company names and help reduce duplicate or ambiguous matches.

```json
{
  "companyDomain": "dteenergy.com",
  "limit": 10
}
```

### Use company name for manual lookup

You can also use `companyName` to search for layoff records by company name.

Company name search is useful for manual lookup, but for automated workflows, CRM enrichment, and account matching, use `companyDomain` when available.

```json
{
  "companyName": "DTE Energy",
  "limit": 10
}
```

### Use ticker for public company monitoring

For public companies, use `companyTicker` when you want to search by stock ticker.

```json
{
  "companyTicker": "DTE",
  "limit": 10
}
```

### Use `LAST-MODIFIED` for daily syncs

For recurring syncs, alerts, and automated workflows, use `LAST-MODIFIED`.

```json
{
  "dateType": "LAST-MODIFIED",
  "date": "2026-03-03"
}
```

This helps retrieve records that were newly added or updated on that date.

### Use `ANNOUNCED` for event-date research

For research based on when a layoff was announced, use `ANNOUNCED`.

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2026-01-01",
  "endDate": "2026-03-31"
}
```

### Use company location for headquarters-based analysis

Use `companyLocation` when you want to filter by where the company is headquartered.

```json
{
  "companyLocation": "Detroit,Michigan,United States of America",
  "limit": 20
}
```

### Use layoff location for event-location analysis

Use `layoffLocation` when you want to filter by where the layoff, closure, or workforce reduction occurred.

```json
{
  "layoffLocation": "Superior,Wisconsin,United States of America",
  "limit": 20
}
```

### Use layoff type to classify workforce events

Use `layoffType` to distinguish between layoffs, furloughs, hiring freezes, plant closures, and voluntary separation programs.

```json
{
  "layoffType": [
    "Downsizing/Layoff",
    "Permanent Plant Closure"
  ],
  "limit": 25
}
```

### Use layoff reason for risk and trend analysis

Use `layoffReason` to analyze why workforce reductions are happening.

```json
{
  "layoffReason": [
    "Restructuring",
    "Cost-cutting",
    "Financial Distress"
  ],
  "limit": 25
}
```

### Use `limit` to control result size

The default limit is `100` records if no limit is provided.

```json
{
  "limit": 100
}
```

### Combine filters for more precise results

You can combine multiple filters in a single request to narrow your results.

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2026-01-01",
  "endDate": "2026-03-31",
  "companyIndustry": [
    "technology"
  ],
  "companyType": [
    "Public"
  ],
  "layoffReason": [
    "Restructuring",
    "Cost-cutting"
  ],
  "limit": 50
}
```

***

## Notes

* All parameters are optional.
* Dates should be provided in `YYYY-MM-DD` format.
* The Intellizence Layoffs Dataset contains data beginning from `2020-01-01`.
* Use `LAST-MODIFIED` when you want newly added or updated records.
* Use `ANNOUNCED` when you want records based on the layoff announcement date.
* Use `companyDomain` for CRM matching, account enrichment, risk monitoring, and workflow automation.
* Use `companyName` for manual lookup when the company domain is not available.
* Use `companyTicker` for public company monitoring.
* Use `companyLocation` for headquarters-based filtering.
* Use `layoffLocation` for event-location filtering.
* Use `layoffType` to filter by workforce event type.
* Use `layoffReason` to filter by the reason mentioned in the source.


# Intellizence Business Expansion & Major Hiring Signals API

This REST API provides continuous access to ongoing and historical business expansion data from the Intellizence Business Expansion & Major Hiring Dataset.

{% hint style="info" %}
Best  suited for :

* Continuous monitoring of business expansion & major hiring announcements
* Trigger alerts and automated workflows
* Major business investment trends & analysis
* Power AI agents and internal intelligence platforms
  {% endhint %}

> **Ready to get started?** [**Request your API key**](https://intellizence.com/api-trial/) and start building.\
> **Questions?** [**Schedule a call**](https://intellizence.com/schedule-a-demo/) or email us at <sales@intellizence.com>.

**Security Notice:**  Please keep API Key secure. Do not share your API key in publicly accessible areas such as GitHub, client-side code, and so forth.

## Submit Business Expansion Dataset Request

> This REST API endpoint provides access to both ongoing and historical business expansion (opening up of offices, factories, headquarters, etc), major hiring and investment data from the Intellizence Business Expansion & Major Hiring Dataset.\
> \
> Users can search data using various parameters- \`dateType\`,\`startDate\`,\`endDate\`,\`date\`,\`companyDomain\`,\`companyName\`,\`companyIndustry\`,\`companyLocation\`,\`companyType\`,\`companyTicker\`,\`expansionType\`,\`expansionLocation\`,\`investment\`,\`currency\` and \`jobs\` . \
> \
> Users can limit the number of records returned using the \`limit\` parameter. All parameters are optional.\
> \
> The API key has to be passed in HTTP header with the name \`x-api-key\`."

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Business Expansion & Major Hiring Signals API","version":"1.0"},"servers":[{"url":"https://connect.intellizence.com"}],"paths":{"/api/dataset/business-expansion":{"post":{"summary":"Submit Business Expansion Dataset Request","description":"This REST API endpoint provides access to both ongoing and historical business expansion (opening up of offices, factories, headquarters, etc), major hiring and investment data from the Intellizence Business Expansion & Major Hiring Dataset.\n\nUsers can search data using various parameters- `dateType`,`startDate`,`endDate`,`date`,`companyDomain`,`companyName`,`companyIndustry`,`companyLocation`,`companyType`,`companyTicker`,`expansionType`,`expansionLocation`,`investment`,`currency` and `jobs` . \n\nUsers can limit the number of records returned using the `limit` parameter. All parameters are optional.\n\nThe API key has to be passed in HTTP header with the name `x-api-key`.\"","operationId":"getBusiness-ExpansionDataset","parameters":[{"name":"x-api-key","in":"header","description":"Intellizence API key for authenticating the request.","required":true,"schema":{"type":"string"}}],"requestBody":{"description":"Intellizence Business Expansion Dataset request body","content":{"application/json":{"schema":{"$ref":"#/components/schemas/dataset_businessexpansion_body"}}}},"responses":{"200":{"description":"Successful response.\n\nNote: Credit fields (openingBalance, closingBalance, creditsConsumed) are returned only for Pay-Per-Use billing.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/BusinessExpansionSearchResponse"}}}},"400":{"description":"400 - Bad Request\n\nBad request, possibly missing required parameters, invalid data, invalid or missing API key.\n\n- 701 - Start Date is not in YYYY-MM-DD format.\n- 702 - End Date is not in YYYY-MM-DD format.\n- 703 - Plan or resource not subscribed\n- 709 - No companies configured for this account.\n- 710 - No triggers configured for this account."},"402":{"description":"402 - Payment Required\n\n- 704 - Payment is pending.\n- 712 - Insufficient credits for this request."},"403":{"description":"403 - Forbidden\n\n- 707 - Subscription has expired.\n- 708 - Start date is outside your subscription's allowed date range."},"406":{"description":"Invalid Deal Amount Filter Format"},"500":{"description":"500 - Internal Server Error\n\n- 715 - A technical error occurred.\n- 799 - A technical error occurred."}}}}},"components":{"schemas":{"dataset_businessexpansion_body":{"type":"object","properties":{"dateType":{"type":"string","description":"Choose the date type used to filter records.The default value is 'ANNOUNCED'. To get the daily update of records created or modified, 'LAST-MODIFIED' is recommended.","enum":["ANNOUNCED","LAST-MODIFIED"]},"startDate":{"type":"string","description":"The start date (YYYY-MM-DD) from which business expansion data is needed. The Intellizence Business Expansion Dataset contains data beginning from 2021-01-01.","format":"date"},"endDate":{"type":"string","description":"The end date (YYYY-MM-DD) up to which business expansion data is needed.","format":"date"},"date":{"type":"string","description":"Exact date (YYYY-MM-DD) for which the business expansion data is needed.","format":"date"},"companyName":{"type":"string","description":"The name(s) of the company for which the business expansion data is needed. Partial name matches are supported. Multiple values can be provided either as a comma-separated string or as an array."},"companyDomain":{"type":"string","description":"The website domain(s) of the company for which the business expansion  data is needed. Partial website domain matches are supported. Multiple values can be provided either as a comma-separated string or as an array."},"companyIndustry":{"type":"string","description":"The industry or industries of companies for which business expansion data is needed. The industries are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values should be provided as an array.","enum":["accounting, audit & tax","advertising & communication","agriculture, animal husbandry & forestry","angels/ venture capital/ private equity","automobile","aviation","banking","bio-technology","business services","chemicals & fertilizers","clean technology","conglomerate","consulting","consumer products","consumer services","defence","distribution","e-commerce","economic development","education","energy & utilities","engineering, procurement & construction","financial services","gambling","gaming","government","healthcare","human resources","insurance","it services & outsourcing","legal","logistics & supply chain","manufacturing","media & entertainment","medical device","metals & mining","not-for-profit/ ngo","others","pharmaceuticals","publishing","railways","real estate","regulatory","restaurants & food services","retail","security","shipping & ports","spac/blank check","sports","technology","telecommunication","textiles","tourism & hospitality","trading","transportation"]},"companyLocation":{"type":"string","description":"The location of the company headquarters for which business expansion data is needed. The location can be city or state/province or country. Multiple values can be provided either as a comma-separated string or as an array."},"companyType":{"type":"string","description":"The type of company for which business expansion  data is needed. The company types are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Public","Private","Government/Regulator","Not-for-profit","Others"]},"companyTicker":{"type":"string","description":"Company Ticker if it's a public company."},"expansionType":{"type":"string","description":"Type of expansion for which data is needed. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Store","Restaurant","Data Centre","Factory/Plant","Country Expansion","HQ","Mine","Branch/Office","Oil/Gas Well","Other","Product/Service Availability","Research/Lab/Innovation","Renewables","Fulfillment/Distribution Centre/Warehouse","New Business","Fleet","Route","Airport/Airline Hub/Cargo Facility","Healthcare Facility","Hotel/Resort","Delivery/Pickup","Education","Lease/Land Purchase"]},"expansionLocation":{"type":"string","description":"Location where the expansion is announced. Multiple values can be provided either as a comma-separated string or as an array."},"investment":{"pattern":"^(>|>=|<|<=|=|!=)?\\d+(,\\d+)?$","type":"number","description":"Filter the records by expansion investment amount. Pass the `currency` whenver `investment` is used. If `currency` is not provided along with `investment`, all the records that matches the deal amount of any currency will be returned. The allowed operators are >, >=, <, <=,=,!=, (MinimumValue),(Maximum Value). Examples: >1000000, >=1000000, <1000000, <=1000000,=1000000,!=1000000, (1000000,400000)","format":"float"},"currency":{"type":"string","description":"The currency of the investment amount.","enum":["USD","CAD","EUR","GBP","INR","AUD","CHF","CNY","JPY","SEK"]},"jobs":{"pattern":"^(>|>=|<|<=|=|!=)?\\d+(,\\d+)?$","type":"number","description":"Number of jobs created. The allowed operators are >, >=, <, <=,=,!=, (MinimumValue),(Maximum Value). Examples: >1000, >=1000, <1000, <=1000,=1000,!=1000, (1000,4000)","format":"float"},"limit":{"type":"integer","description":"The maximum number of records to be returned."}}},"BusinessExpansionSearchResponse":{"required":["code","count","dataset"],"type":"object","properties":{"code":{"type":"integer"},"count":{"type":"integer"},"dataset":{"type":"array","items":{"$ref":"#/components/schemas/inline_response_200"}},"openingBalance":{"type":"integer","nullable":true},"closingBalance":{"type":"integer","nullable":true},"creditsConsumed":{"type":"integer","nullable":true}}},"inline_response_200":{"type":"object","properties":{"id":{"type":"string","description":"Unique ID of the record"},"announcedDate":{"type":"string","description":"Business expansion announced date","format":"date"},"company":{"$ref":"#/components/schemas/inline_response_200_company"},"expansionType":{"type":"array","description":"Type of expansion","items":{"type":"string"}},"location":{"$ref":"#/components/schemas/inline_response_200_location"},"investment":{"type":"number","description":"Expansion investment amount","format":"float"},"currency":{"type":"string","description":"The currency of the investment amount"},"jobs":{"type":"number","description":"Number of jobs created.","format":"float"},"url":{"type":"string","description":"URL of the source document."},"title":{"type":"string","description":"Source title - News or press release headline"},"lastModified":{"type":"string","description":"The last modified date of the record.","format":"date"}}},"inline_response_200_company":{"type":"object","properties":{"name":{"type":"string","description":"Company name"},"domain":{"type":"string","description":"Company website domain"},"industries":{"type":"array","description":"Company industry classification by Intellizence","items":{"type":"string"}},"location":{"type":"string","description":"Company HQ location"},"type":{"type":"string","description":"Company type"},"ticker":{"type":"array","description":"Company stock ticker (if public)","items":{"type":"string"}},"stockExchange":{"type":"array","description":"Stock exchange where the company is listed (if public)","items":{"type":"string"}}}},"inline_response_200_location":{"type":"object","properties":{"country":{"type":"string"},"state":{"type":"string"},"city":{"type":"string"}},"description":"Location where the expansion is announced"}}}}
```

## The dataset\_businessexpansion\_body object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Business Expansion & Major Hiring Signals API","version":"1.0"},"components":{"schemas":{"dataset_businessexpansion_body":{"type":"object","properties":{"dateType":{"type":"string","description":"Choose the date type used to filter records.The default value is 'ANNOUNCED'. To get the daily update of records created or modified, 'LAST-MODIFIED' is recommended.","enum":["ANNOUNCED","LAST-MODIFIED"]},"startDate":{"type":"string","description":"The start date (YYYY-MM-DD) from which business expansion data is needed. The Intellizence Business Expansion Dataset contains data beginning from 2021-01-01.","format":"date"},"endDate":{"type":"string","description":"The end date (YYYY-MM-DD) up to which business expansion data is needed.","format":"date"},"date":{"type":"string","description":"Exact date (YYYY-MM-DD) for which the business expansion data is needed.","format":"date"},"companyName":{"type":"string","description":"The name(s) of the company for which the business expansion data is needed. Partial name matches are supported. Multiple values can be provided either as a comma-separated string or as an array."},"companyDomain":{"type":"string","description":"The website domain(s) of the company for which the business expansion  data is needed. Partial website domain matches are supported. Multiple values can be provided either as a comma-separated string or as an array."},"companyIndustry":{"type":"string","description":"The industry or industries of companies for which business expansion data is needed. The industries are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values should be provided as an array.","enum":["accounting, audit & tax","advertising & communication","agriculture, animal husbandry & forestry","angels/ venture capital/ private equity","automobile","aviation","banking","bio-technology","business services","chemicals & fertilizers","clean technology","conglomerate","consulting","consumer products","consumer services","defence","distribution","e-commerce","economic development","education","energy & utilities","engineering, procurement & construction","financial services","gambling","gaming","government","healthcare","human resources","insurance","it services & outsourcing","legal","logistics & supply chain","manufacturing","media & entertainment","medical device","metals & mining","not-for-profit/ ngo","others","pharmaceuticals","publishing","railways","real estate","regulatory","restaurants & food services","retail","security","shipping & ports","spac/blank check","sports","technology","telecommunication","textiles","tourism & hospitality","trading","transportation"]},"companyLocation":{"type":"string","description":"The location of the company headquarters for which business expansion data is needed. The location can be city or state/province or country. Multiple values can be provided either as a comma-separated string or as an array."},"companyType":{"type":"string","description":"The type of company for which business expansion  data is needed. The company types are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Public","Private","Government/Regulator","Not-for-profit","Others"]},"companyTicker":{"type":"string","description":"Company Ticker if it's a public company."},"expansionType":{"type":"string","description":"Type of expansion for which data is needed. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Store","Restaurant","Data Centre","Factory/Plant","Country Expansion","HQ","Mine","Branch/Office","Oil/Gas Well","Other","Product/Service Availability","Research/Lab/Innovation","Renewables","Fulfillment/Distribution Centre/Warehouse","New Business","Fleet","Route","Airport/Airline Hub/Cargo Facility","Healthcare Facility","Hotel/Resort","Delivery/Pickup","Education","Lease/Land Purchase"]},"expansionLocation":{"type":"string","description":"Location where the expansion is announced. Multiple values can be provided either as a comma-separated string or as an array."},"investment":{"pattern":"^(>|>=|<|<=|=|!=)?\\d+(,\\d+)?$","type":"number","description":"Filter the records by expansion investment amount. Pass the `currency` whenver `investment` is used. If `currency` is not provided along with `investment`, all the records that matches the deal amount of any currency will be returned. The allowed operators are >, >=, <, <=,=,!=, (MinimumValue),(Maximum Value). Examples: >1000000, >=1000000, <1000000, <=1000000,=1000000,!=1000000, (1000000,400000)","format":"float"},"currency":{"type":"string","description":"The currency of the investment amount.","enum":["USD","CAD","EUR","GBP","INR","AUD","CHF","CNY","JPY","SEK"]},"jobs":{"pattern":"^(>|>=|<|<=|=|!=)?\\d+(,\\d+)?$","type":"number","description":"Number of jobs created. The allowed operators are >, >=, <, <=,=,!=, (MinimumValue),(Maximum Value). Examples: >1000, >=1000, <1000, <=1000,=1000,!=1000, (1000,4000)","format":"float"},"limit":{"type":"integer","description":"The maximum number of records to be returned."}}}}}}
```

## The inline\_response\_200 object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Business Expansion & Major Hiring Signals API","version":"1.0"},"components":{"schemas":{"inline_response_200":{"type":"object","properties":{"id":{"type":"string","description":"Unique ID of the record"},"announcedDate":{"type":"string","description":"Business expansion announced date","format":"date"},"company":{"$ref":"#/components/schemas/inline_response_200_company"},"expansionType":{"type":"array","description":"Type of expansion","items":{"type":"string"}},"location":{"$ref":"#/components/schemas/inline_response_200_location"},"investment":{"type":"number","description":"Expansion investment amount","format":"float"},"currency":{"type":"string","description":"The currency of the investment amount"},"jobs":{"type":"number","description":"Number of jobs created.","format":"float"},"url":{"type":"string","description":"URL of the source document."},"title":{"type":"string","description":"Source title - News or press release headline"},"lastModified":{"type":"string","description":"The last modified date of the record.","format":"date"}}},"inline_response_200_company":{"type":"object","properties":{"name":{"type":"string","description":"Company name"},"domain":{"type":"string","description":"Company website domain"},"industries":{"type":"array","description":"Company industry classification by Intellizence","items":{"type":"string"}},"location":{"type":"string","description":"Company HQ location"},"type":{"type":"string","description":"Company type"},"ticker":{"type":"array","description":"Company stock ticker (if public)","items":{"type":"string"}},"stockExchange":{"type":"array","description":"Stock exchange where the company is listed (if public)","items":{"type":"string"}}}},"inline_response_200_location":{"type":"object","properties":{"country":{"type":"string"},"state":{"type":"string"},"city":{"type":"string"}},"description":"Location where the expansion is announced"}}}}
```

## The inline\_response\_200\_company object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Business Expansion & Major Hiring Signals API","version":"1.0"},"components":{"schemas":{"inline_response_200_company":{"type":"object","properties":{"name":{"type":"string","description":"Company name"},"domain":{"type":"string","description":"Company website domain"},"industries":{"type":"array","description":"Company industry classification by Intellizence","items":{"type":"string"}},"location":{"type":"string","description":"Company HQ location"},"type":{"type":"string","description":"Company type"},"ticker":{"type":"array","description":"Company stock ticker (if public)","items":{"type":"string"}},"stockExchange":{"type":"array","description":"Stock exchange where the company is listed (if public)","items":{"type":"string"}}}}}}}
```


# Intellizence Business Expansion API Sample Requests

Sample requests for the Intellizence Business Expansion API, including filters for date, company domain, industry, company location, expansion location, company type, expansion type, investment, etc.

## Business Expansion API Sample Requests

Use these sample API requests to retrieve business expansion, major hiring, facility opening, investment, and growth activity records from the Intellizence Business Expansion & Major Hiring Dataset.

These examples show common ways to filter business expansion records by date, company domain, industry, company location, expansion location, company type, ticker, expansion type, investment amount, jobs created, and limit.

{% hint style="info" %}
All request parameters are optional. You can use a single filter or combine multiple filters based on your use case.
{% endhint %}

***

### Endpoint

```http
POST https://connect.intellizence.com/api/dataset/business-expansion
```

### Authentication

Include your API key in the request header.

```http
x-api-key: YOUR_API_KEY
```

### Content Type

```http
Content-Type: application/json
```

***

## Sample API Requests

### 1. Get Daily Updated Records

Use `dateType: "LAST-MODIFIED"` to retrieve records that were created or updated on a specific date.

This is recommended for daily syncs, alerts, enrichment workflows, and automated data pipelines.

#### Request Body

```json
{
  "dateType": "LAST-MODIFIED",
  "date": "2025-05-01",
  "limit": 5
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/business-expansion \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "LAST-MODIFIED",
    "date": "2025-05-01",
    "limit": 5
  }'
```

***

### 2. Get Expansions Announced on a Specific Date

Use `dateType: "ANNOUNCED"` and `date` to retrieve business expansion records announced on a specific date.

#### Request Body

```json
{
  "dateType": "ANNOUNCED",
  "date": "2025-05-01",
  "limit": 10
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/business-expansion \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "ANNOUNCED",
    "date": "2025-05-01",
    "limit": 10
  }'
```

***

### 3. Get Expansions Within a Date Range

Use `startDate` and `endDate` to retrieve business expansion records announced during a specific period.

The Intellizence Business Expansion Dataset contains data beginning from `2021-01-01`.

#### Request Body

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-05-01",
  "endDate": "2025-05-31",
  "limit": 25
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/business-expansion \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "ANNOUNCED",
    "startDate": "2025-05-01",
    "endDate": "2025-05-31",
    "limit": 25
  }'
```

***

### 4. Search by Company Domain

Use `companyDomain` to retrieve business expansion records for a specific company website domain.

This is recommended for CRM enrichment, account matching, data pipelines, account monitoring, and workflow automation because domains are usually more precise than company names.

#### Request Body

```json
{
  "companyDomain": "kimberly-clark.com",
  "limit": 10
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/business-expansion \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyDomain": "kimberly-clark.com",
    "limit": 10
  }'
```

***

### 5. Search by Company Industry

Use `companyIndustry` to retrieve business expansion records for companies in one or more industries.

This is useful for market research, sector monitoring, investment research, sales prospecting, and competitive intelligence.

#### Request Body

```json
{
  "companyIndustry": [
    "manufacturing",
    "technology"
  ],
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/business-expansion \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyIndustry": [
      "manufacturing",
      "technology"
    ],
    "limit": 20
  }'
```

***

### 6. Search by Expansion Type

Use `expansionType` to retrieve records by the type of business expansion.

Examples include `Factory/Plant`, `Branch/Office`, `HQ`, `Store`, `Restaurant`, `Data Centre`, `Fulfillment/Distribution Centre/Warehouse`, `Research/Lab/Innovation`, `Country Expansion`, `Healthcare Facility`, and `Hotel/Resort`.

#### Request Body

```json
{
  "expansionType": [
    "Factory/Plant",
    "Fulfillment/Distribution Centre/Warehouse"
  ],
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/business-expansion \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "expansionType": [
      "Factory/Plant",
      "Fulfillment/Distribution Centre/Warehouse"
    ],
    "limit": 20
  }'
```

***

### 7. Search by Expansion Location

Use `expansionLocation` to find expansion events announced for a specific location.

This is useful when you want to track new facilities, offices, stores, warehouses, data centers, or hiring plans by city, state, province, country, or region.

#### Request Body

```json
{
  "expansionLocation": "United States of America",
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/business-expansion \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "expansionLocation": "United States of America",
    "limit": 20
  }'
```

***

### 8. Search by Investment Amount

Use `investment` to filter business expansion records by announced investment amount.

You can use comparison operators such as `>`, `>=`, `<`, `<=`, `=`, and `!=`.

When filtering by investment amount, include `currency` for more precise results.

#### Request Body

```json
{
  "investment": ">1000000000",
  "currency": "USD",
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/business-expansion \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "investment": ">1000000000",
    "currency": "USD",
    "limit": 20
  }'
```

***

### 9. Search by Jobs Created

Use `jobs` to filter business expansion records by the number of announced jobs created.

You can use comparison operators such as `>`, `>=`, `<`, `<=`, `=`, and `!=`.

#### Request Body

```json
{
  "jobs": ">500",
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/business-expansion \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "jobs": ">500",
    "limit": 20
  }'
```

***

### 10. Use Multiple Filters Together

Combine filters to narrow results by date range, industry, company type, expansion type, expansion location, investment amount, currency, and jobs created.

#### Request Body

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-01-01",
  "endDate": "2025-05-31",
  "companyIndustry": [
    "manufacturing"
  ],
  "companyType": [
    "Public"
  ],
  "expansionType": [
    "Factory/Plant",
    "Fulfillment/Distribution Centre/Warehouse"
  ],
  "expansionLocation": "United States of America",
  "investment": ">500000000",
  "currency": "USD",
  "jobs": ">250",
  "limit": 50
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/business-expansion \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "ANNOUNCED",
    "startDate": "2025-01-01",
    "endDate": "2025-05-31",
    "companyIndustry": [
      "manufacturing"
    ],
    "companyType": [
      "Public"
    ],
    "expansionType": [
      "Factory/Plant",
      "Fulfillment/Distribution Centre/Warehouse"
    ],
    "expansionLocation": "United States of America",
    "investment": ">500000000",
    "currency": "USD",
    "jobs": ">250",
    "limit": 50
  }'
```

***

## Use Case Examples

### 1. Daily Data Sync

Use this example when you want to pull newly added or updated business expansion records into your application, database, CRM, dashboard, or analytics workflow.

#### Recommended Filters

```json
{
  "dateType": "LAST-MODIFIED",
  "date": "2025-05-01",
  "limit": 100
}
```

#### Best For

* Data pipelines
* Daily refreshes
* Internal dashboards
* Alerts and workflow automation
* CRM and data warehouse enrichment

***

### 2. CRM or Account Enrichment

Use this example to check whether a company in your CRM has recent business expansion, facility opening, or major hiring activity.

#### Recommended Filters

```json
{
  "companyDomain": "kimberly-clark.com",
  "dateType": "LAST-MODIFIED",
  "startDate": "2025-01-01",
  "endDate": "2025-05-31",
  "limit": 10
}
```

#### Best For

* CRM enrichment
* Account scoring
* Sales intelligence
* Customer intelligence
* Signal-based selling workflows

***

### 3. Investment Research

Use this example to track major capital investment and expansion activity in a specific sector.

#### Recommended Filters

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-01-01",
  "endDate": "2025-12-31",
  "companyIndustry": [
    "manufacturing"
  ],
  "investment": ">1000000000",
  "currency": "USD",
  "limit": 50
}
```

#### Best For

* Market mapping
* Sector research
* Capital expenditure tracking
* Investment research
* Corporate development research

***

### 4. Economic Development and Location Monitoring

Use this example to monitor expansion activity, new facilities, and job creation in a specific geography.

#### Recommended Filters

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-01-01",
  "endDate": "2025-12-31",
  "expansionLocation": "United States of America",
  "jobs": ">250",
  "limit": 50
}
```

#### Best For

* Economic development research
* Regional investment tracking
* Job creation monitoring
* Site selection intelligence
* Location-based market analysis

***

### 5. Sales and Prospecting

Use this example to identify companies that are expanding, opening new locations, investing in facilities, or creating new jobs.

#### Recommended Filters

```json
{
  "dateType": "LAST-MODIFIED",
  "startDate": "2025-01-01",
  "endDate": "2025-05-31",
  "companyIndustry": [
    "technology",
    "manufacturing"
  ],
  "expansionType": [
    "Branch/Office",
    "Factory/Plant",
    "Fulfillment/Distribution Centre/Warehouse"
  ],
  "jobs": ">100",
  "limit": 25
}
```

#### Best For

* Prospecting
* Account prioritization
* Trigger-based outreach
* Sales and marketing campaigns
* Go-to-market workflows

***

## Recommended Use Cases

| Use Case                                     | Recommended Filters                                     |
| -------------------------------------------- | ------------------------------------------------------- |
| Daily data sync                              | `dateType`, `date`, `limit`                             |
| CRM or account enrichment                    | `companyDomain`, `dateType`, `startDate`, `endDate`     |
| Investment research                          | `companyIndustry`, date range, `investment`, `currency` |
| Economic development and location monitoring | `expansionLocation`, `jobs`, date range                 |
| Sales and prospecting                        | `companyIndustry`, `expansionType`, `jobs`, date range  |

***

## Best Practices

### Prefer company domain for company matching

For CRM enrichment, data pipelines, account matching, and automated workflows, use `companyDomain` when available.

Company domains are usually more precise than company names and help reduce duplicate or ambiguous matches.

```json
{
  "companyDomain": "kimberly-clark.com",
  "limit": 10
}
```

### Use company name for manual lookup

You can also use `companyName` to search for business expansion records by company name.

Company name search is useful for manual lookup, but for automated workflows, CRM enrichment, and account matching, use `companyDomain` when available.

```json
{
  "companyName": "Kimberly-Clark",
  "limit": 10
}
```

### Use ticker for public company monitoring

For public companies, use `companyTicker` when you want to search by stock ticker.

```json
{
  "companyTicker": "KMB",
  "limit": 10
}
```

### Use `LAST-MODIFIED` for daily syncs

For recurring syncs, alerts, and automated workflows, use `LAST-MODIFIED`.

```json
{
  "dateType": "LAST-MODIFIED",
  "date": "2025-05-01"
}
```

This helps retrieve records that were newly added or updated on that date.

### Use `ANNOUNCED` for event-date research

For research based on when a business expansion was announced, use `ANNOUNCED`.

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-01-01",
  "endDate": "2025-05-31"
}
```

### Use company location for headquarters-based analysis

Use `companyLocation` when you want to filter by where the company is headquartered.

```json
{
  "companyLocation": "Irving,Texas,United States of America",
  "limit": 20
}
```

### Use expansion location for event-location analysis

Use `expansionLocation` when you want to filter by where the expansion, facility opening, or major hiring event occurred.

```json
{
  "expansionLocation": "United States of America",
  "limit": 20
}
```

### Use expansion type to classify growth events

Use `expansionType` to distinguish between factories, offices, stores, warehouses, data centers, headquarters, research facilities, country expansion, and other expansion types.

```json
{
  "expansionType": [
    "Factory/Plant",
    "Branch/Office",
    "Data Centre"
  ],
  "limit": 25
}
```

### Use investment with currency

When filtering by investment amount, include `currency` for more precise results.

```json
{
  "investment": ">500000000",
  "currency": "USD",
  "limit": 25
}
```

### Use jobs for major hiring signals

Use `jobs` to filter records by announced job creation.

```json
{
  "jobs": ">500",
  "limit": 25
}
```

### Use `limit` to control result size

The default limit is `100` records if no limit is provided.

```json
{
  "limit": 100
}
```

### Combine filters for more precise results

You can combine multiple filters in a single request to narrow your results.

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-01-01",
  "endDate": "2025-05-31",
  "companyIndustry": [
    "manufacturing"
  ],
  "expansionType": [
    "Factory/Plant"
  ],
  "investment": ">500000000",
  "currency": "USD",
  "jobs": ">250",
  "limit": 50
}
```

***

## Notes

* All parameters are optional.
* Dates should be provided in `YYYY-MM-DD` format.
* The Intellizence Business Expansion Dataset contains data beginning from `2021-01-01`.
* Use `LAST-MODIFIED` when you want newly added or updated records.
* Use `ANNOUNCED` when you want records based on the business expansion announcement date.
* Use `companyDomain` for CRM matching, account enrichment, account monitoring, and workflow automation.
* Use `companyName` for manual lookup when the company domain is not available.
* Use `companyTicker` for public company monitoring.
* Use `companyLocation` for headquarters-based filtering.
* Use `expansionLocation` for event-location filtering.
* Use `expansionType` to filter by the type of expansion or growth event.
* Include `currency` when filtering by `investment`.
* Use `jobs` to filter by announced job creation.


# Intellizence C-Suite Changes Signals API

This REST API provides continuous access to ongoing and historical leadership and executive changes data from the Intellizence C-Suite Changes Dataset.

{% hint style="info" %}
Best  suited for :

* Continuous monitoring of C-Suite & Senior Management changes
* Trigger alerts and automated workflows
* Power AI agents and internal intelligence platforms
  {% endhint %}

> **Ready to get started?** [**Request your API key**](https://intellizence.com/api-trial/) and start building.\
> **Questions?** [**Schedule a call**](https://intellizence.com/schedule-a-demo/) or email us at <sales@intellizence.com>.

**Security Notice:** Please keep API Key secure. Do not share your API key in publicly accessible areas such as GitHub, client-side code, and so forth.

## Submit C-Suite Changes Dataset Request

> This REST API endpoint provides access to both ongoing and historical C-Level changes (appointment, promotion, retirement, resignation & termination) data from the Intellizence C-Suite Changes Dataset. Data access is limited to records within your subscription’s entitled date range.\
> \
> Users can search data using various parameters- \`dateType\`,\`startDate\`,\`endDate\`,\`date\`,\`companyDomain\`,\`companyName\`,\`companyIndustry\`,\`companyLocation\`,\`companyType\`,\`companyTicker\`,\`executiveName\`,\`executiveTitle\`,\`executiveTitleCategory\`, and \`reason\` . \
> \
> Users can limit the number of records returned using the \`limit\` parameter. All the parameters are optional. \
> \
> The API key has to be passed in HTTP header with the name \`x-api-key\`.'

```json
{"openapi":"3.0.3","info":{"title":"Intellizence C-Suite Changes Signals API","version":"1.0"},"servers":[{"url":"https://connect.intellizence.com"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","name":"x-api-key","in":"header"}},"schemas":{"dataset_executivechange_body":{"type":"object","properties":{"dateType":{"type":"string","description":"Choose the date type used to filter records.The default value is 'ANNOUNCED'. To get the daily update of records created or modified, 'LAST-MODIFIED' is recommended.","enum":["ANNOUNCED","LAST-MODIFIED"]},"startDate":{"type":"string","description":"The start date (YYYY-MM-DD) from which C-Suite changes data is needed. The Intellizence C-Suite Changes Dataset contains data from 2021-01-01.","format":"date"},"endDate":{"type":"string","description":"The end date (YYYY-MM-DD) up to which C-Suite changes data is needed.","format":"date"},"date":{"type":"string","description":"Exact date (YYYY-MM-DD) for which the C-Suite changes data is needed.","format":"date"},"companyName":{"type":"string","description":"The name(s) of the company for which the C-Suite changes data is needed. Partial name matches are supported. Multiple values can be provided either as a comma-separated string or as an array."},"companyDomain":{"type":"string","description":"The website domain(s) of the company for which the C-Suite changes data is needed. Partial website domain matches are supported. Multiple values can be provided either as a comma-separated string or as an array."},"companyIndustry":{"type":"string","description":"The industry or industries of companies for which C-Suite changes data is needed. The industries are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided as an array.","enum":["accounting, audit & tax","advertising & communication","agriculture, animal husbandry & forestry","angels/ venture capital/ private equity","automobile","aviation","banking","bio-technology","business services","chemicals & fertilizers","clean technology","conglomerate","consulting","consumer products","consumer services","defence","distribution","e-commerce","economic development","education","energy & utilities","engineering, procurement & construction","financial services","gambling","gaming","government","healthcare","human resources","insurance","it services & outsourcing","legal","logistics & supply chain","manufacturing","media & entertainment","medical device","metals & mining","not-for-profit/ ngo","others","pharmaceuticals","publishing","railways","real estate","regulatory","restaurants & food services","retail","security","shipping & ports","spac/blank check","sports","technology","telecommunication","textiles","tourism & hospitality","trading","transportation"]},"companyLocation":{"type":"string","description":"The location of the company headquarters for which C-Suite changes data is needed. The location can be city or state/province or country. Multiple values can be provided either as a comma-separated string or as an array."},"companyType":{"type":"string","description":"The type of company for which C-Suite changes data is needed. The company types are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Public","Private","Government/Regulator","Not-for-profit","Others"]},"companyTicker":{"type":"string","description":"Company Ticker if it's a public company.Multiple values can be provided either as a comma-separated string or as an array."},"executiveName":{"type":"string","description":"Name of the C-Level executive whose role is changed. Multiple values can be provided either as a comma-separated string or as an array."},"executiveTitle":{"type":"string","description":"Title of the C-Level executive whose role is changed. Multiple values can be provided either as a comma-separated string or as an array."},"executiveTitleCategory":{"type":"string","description":"Title category of the C-Level executive whose role is changed. The title categories are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Chief Executive Officer ( CEO)/President/Managing Director","Chair/Vice-Chair","Board of Director","Chief Operating Officer ( COO)","Chief Financial Officer ( CFO) / Head of Finance","Chief Investment Officer ( CIO)","Chief Information Officer ( CIO) / Head of IT","Chief Technology Officer ( CTO)","Chief Product Officer ( CPO) / Head of Product","Chief Risk Officer ( CRO) / Head of Risk","Chief Information Security Officer ( CISO)\"","Chief Human Resource / People Officer\"","Chief Marketing Officer ( CMO)","Chief Revenue Officer ( CRO) / Head of Sales","Head of Customer Success/Support","Other"]},"reason":{"type":"string","description":"The reason for the executive change.","enum":["New Appointment","Promoted/Role Change","Retired","Terminated","Health","Resigned","Demise","Others"]},"limit":{"type":"integer","description":"The maximum number of records to be returned."}}},"ExecutiveChangeSearchResponse":{"required":["code","count","dataset"],"type":"object","properties":{"code":{"type":"integer"},"count":{"type":"integer"},"dataset":{"type":"array","items":{"$ref":"#/components/schemas/inline_response_200"}},"openingBalance":{"type":"integer","nullable":true},"closingBalance":{"type":"integer","nullable":true},"creditsConsumed":{"type":"integer","nullable":true}}},"inline_response_200":{"type":"object","properties":{"id":{"type":"string","description":"Unique ID of the record"},"announcedDate":{"type":"string","description":"C-Level executive change announced date","format":"date"},"company":{"$ref":"#/components/schemas/inline_response_200_company"},"executiveName":{"type":"string","description":"Name of the C-Level executive whose role is changed"},"executiveTitle":{"type":"string","description":"Title of the C-Level executive whose role is changed"},"executiveTitleCategory":{"type":"string","description":"Title category of the C-Level executive whose role is changed"},"reason":{"type":"string","description":"The reason for the executive change."},"effectiveDate":{"type":"string","description":"Effective date of the role change","format":"date"},"lastModified":{"type":"string","description":"The last modified date of the record.","format":"date"},"title":{"type":"string","description":"Source title - News or press release headline"},"url":{"type":"string","description":"URL of the source document."}}},"inline_response_200_company":{"type":"object","properties":{"name":{"type":"string","description":"Company name"},"domain":{"type":"string","description":"Company website domain"},"industries":{"type":"array","description":"Company industry classification by Intellizence","items":{"type":"string"}},"location":{"type":"string","description":"Company HQ location"},"type":{"type":"string","description":"Company type"},"ticker":{"type":"array","description":"Company stock ticker (if public)","items":{"type":"string"}}}}}},"paths":{"/api/dataset/executive-change":{"post":{"summary":"Submit C-Suite Changes Dataset Request","description":"This REST API endpoint provides access to both ongoing and historical C-Level changes (appointment, promotion, retirement, resignation & termination) data from the Intellizence C-Suite Changes Dataset. Data access is limited to records within your subscription’s entitled date range.\n\nUsers can search data using various parameters- `dateType`,`startDate`,`endDate`,`date`,`companyDomain`,`companyName`,`companyIndustry`,`companyLocation`,`companyType`,`companyTicker`,`executiveName`,`executiveTitle`,`executiveTitleCategory`, and `reason` . \n\nUsers can limit the number of records returned using the `limit` parameter. All the parameters are optional. \n\nThe API key has to be passed in HTTP header with the name `x-api-key`.'","operationId":"getExecutive-ChangeDataset","parameters":[{"name":"x-api-key","in":"header","description":"Intellizence API key for authenticating the request.","required":true,"schema":{"type":"string"}}],"requestBody":{"description":"Intellizence C-Suite Changes Dataset request body","content":{"application/json":{"schema":{"$ref":"#/components/schemas/dataset_executivechange_body"}}}},"responses":{"200":{"description":"Successful response.\n\nNote: Credit fields (openingBalance, closingBalance, creditsConsumed) are returned only for Pay-Per-Use billing.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ExecutiveChangeSearchResponse"}}}},"400":{"description":"400 - Bad Request\n\nBad request, possibly missing required parameters, invalid data, invalid or missing API key.\n\n- 701 - Start Date is not in YYYY-MM-DD format.\n- 702 - End Date is not in YYYY-MM-DD format.\n- 703 - Plan or resource not subscribed\n- 709 - No companies configured for this account.\n- 710 - No triggers configured for this account.\n"},"402":{"description":"402 - Payment Required\n\n- 704 - Payment is pending.\n- 712 - Insufficient credits for this request.\n"},"403":{"description":"403 - Forbidden\n\n- 707 - Subscription has expired.\n- 708 - Start date is outside your subscription's allowed date range.\n"},"500":{"description":"500 - Internal Server Error\n\n- 715 - A technical error occurred.\n- 799 - A technical error occurred.\n"}}}}}}
```

## The dataset\_executivechange\_body object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence C-Suite Changes Signals API","version":"1.0"},"components":{"schemas":{"dataset_executivechange_body":{"type":"object","properties":{"dateType":{"type":"string","description":"Choose the date type used to filter records.The default value is 'ANNOUNCED'. To get the daily update of records created or modified, 'LAST-MODIFIED' is recommended.","enum":["ANNOUNCED","LAST-MODIFIED"]},"startDate":{"type":"string","description":"The start date (YYYY-MM-DD) from which C-Suite changes data is needed. The Intellizence C-Suite Changes Dataset contains data from 2021-01-01.","format":"date"},"endDate":{"type":"string","description":"The end date (YYYY-MM-DD) up to which C-Suite changes data is needed.","format":"date"},"date":{"type":"string","description":"Exact date (YYYY-MM-DD) for which the C-Suite changes data is needed.","format":"date"},"companyName":{"type":"string","description":"The name(s) of the company for which the C-Suite changes data is needed. Partial name matches are supported. Multiple values can be provided either as a comma-separated string or as an array."},"companyDomain":{"type":"string","description":"The website domain(s) of the company for which the C-Suite changes data is needed. Partial website domain matches are supported. Multiple values can be provided either as a comma-separated string or as an array."},"companyIndustry":{"type":"string","description":"The industry or industries of companies for which C-Suite changes data is needed. The industries are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided as an array.","enum":["accounting, audit & tax","advertising & communication","agriculture, animal husbandry & forestry","angels/ venture capital/ private equity","automobile","aviation","banking","bio-technology","business services","chemicals & fertilizers","clean technology","conglomerate","consulting","consumer products","consumer services","defence","distribution","e-commerce","economic development","education","energy & utilities","engineering, procurement & construction","financial services","gambling","gaming","government","healthcare","human resources","insurance","it services & outsourcing","legal","logistics & supply chain","manufacturing","media & entertainment","medical device","metals & mining","not-for-profit/ ngo","others","pharmaceuticals","publishing","railways","real estate","regulatory","restaurants & food services","retail","security","shipping & ports","spac/blank check","sports","technology","telecommunication","textiles","tourism & hospitality","trading","transportation"]},"companyLocation":{"type":"string","description":"The location of the company headquarters for which C-Suite changes data is needed. The location can be city or state/province or country. Multiple values can be provided either as a comma-separated string or as an array."},"companyType":{"type":"string","description":"The type of company for which C-Suite changes data is needed. The company types are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Public","Private","Government/Regulator","Not-for-profit","Others"]},"companyTicker":{"type":"string","description":"Company Ticker if it's a public company.Multiple values can be provided either as a comma-separated string or as an array."},"executiveName":{"type":"string","description":"Name of the C-Level executive whose role is changed. Multiple values can be provided either as a comma-separated string or as an array."},"executiveTitle":{"type":"string","description":"Title of the C-Level executive whose role is changed. Multiple values can be provided either as a comma-separated string or as an array."},"executiveTitleCategory":{"type":"string","description":"Title category of the C-Level executive whose role is changed. The title categories are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Chief Executive Officer ( CEO)/President/Managing Director","Chair/Vice-Chair","Board of Director","Chief Operating Officer ( COO)","Chief Financial Officer ( CFO) / Head of Finance","Chief Investment Officer ( CIO)","Chief Information Officer ( CIO) / Head of IT","Chief Technology Officer ( CTO)","Chief Product Officer ( CPO) / Head of Product","Chief Risk Officer ( CRO) / Head of Risk","Chief Information Security Officer ( CISO)\"","Chief Human Resource / People Officer\"","Chief Marketing Officer ( CMO)","Chief Revenue Officer ( CRO) / Head of Sales","Head of Customer Success/Support","Other"]},"reason":{"type":"string","description":"The reason for the executive change.","enum":["New Appointment","Promoted/Role Change","Retired","Terminated","Health","Resigned","Demise","Others"]},"limit":{"type":"integer","description":"The maximum number of records to be returned."}}}}}}
```

## The inline\_response\_200 object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence C-Suite Changes Signals API","version":"1.0"},"components":{"schemas":{"inline_response_200":{"type":"object","properties":{"id":{"type":"string","description":"Unique ID of the record"},"announcedDate":{"type":"string","description":"C-Level executive change announced date","format":"date"},"company":{"$ref":"#/components/schemas/inline_response_200_company"},"executiveName":{"type":"string","description":"Name of the C-Level executive whose role is changed"},"executiveTitle":{"type":"string","description":"Title of the C-Level executive whose role is changed"},"executiveTitleCategory":{"type":"string","description":"Title category of the C-Level executive whose role is changed"},"reason":{"type":"string","description":"The reason for the executive change."},"effectiveDate":{"type":"string","description":"Effective date of the role change","format":"date"},"lastModified":{"type":"string","description":"The last modified date of the record.","format":"date"},"title":{"type":"string","description":"Source title - News or press release headline"},"url":{"type":"string","description":"URL of the source document."}}},"inline_response_200_company":{"type":"object","properties":{"name":{"type":"string","description":"Company name"},"domain":{"type":"string","description":"Company website domain"},"industries":{"type":"array","description":"Company industry classification by Intellizence","items":{"type":"string"}},"location":{"type":"string","description":"Company HQ location"},"type":{"type":"string","description":"Company type"},"ticker":{"type":"array","description":"Company stock ticker (if public)","items":{"type":"string"}}}}}}}
```

## The inline\_response\_200\_company object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence C-Suite Changes Signals API","version":"1.0"},"components":{"schemas":{"inline_response_200_company":{"type":"object","properties":{"name":{"type":"string","description":"Company name"},"domain":{"type":"string","description":"Company website domain"},"industries":{"type":"array","description":"Company industry classification by Intellizence","items":{"type":"string"}},"location":{"type":"string","description":"Company HQ location"},"type":{"type":"string","description":"Company type"},"ticker":{"type":"array","description":"Company stock ticker (if public)","items":{"type":"string"}}}}}}}
```


# Intellizence C-Suite Changes API Sample Requests

Sample requests for the Intellizence C-Suite Changes API, including filters for date, company domain, industry, company location, company type, ticker, executive name, executive title, executive title

## C-Suite Changes API Sample Requests

Use these sample API requests to retrieve executive appointments, departures, promotions, retirements, resignations, and other leadership change records from the Intellizence C-Suite Changes Dataset.

These examples show common ways to filter C-Suite change records by date, company domain, industry, company location, company type, ticker, executive name, executive title, executive title category, reason, and limit.

{% hint style="info" %}
All request parameters are optional. You can use a single filter or combine multiple filters based on your use case.
{% endhint %}

***

### Endpoint

```http
POST https://connect.intellizence.com/api/dataset/executive-change
```

### Authentication

Include your API key in the request header.

```http
x-api-key: YOUR_API_KEY
```

### Content Type

```http
Content-Type: application/json
```

***

## Sample API Requests

### 1. Get Daily Updated Records

Use `dateType: "LAST-MODIFIED"` to retrieve records that were created or updated on a specific date.

This is recommended for daily syncs, alerts, enrichment workflows, and automated data pipelines.

#### Request Body

```json
{
  "dateType": "LAST-MODIFIED",
  "date": "2025-05-03",
  "limit": 5
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/executive-change \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "LAST-MODIFIED",
    "date": "2025-05-03",
    "limit": 5
  }'
```

***

### 2. Get C-Suite Changes Announced on a Specific Date

Use `dateType: "ANNOUNCED"` and `date` to retrieve C-Suite change records announced on a specific date.

#### Request Body

```json
{
  "dateType": "ANNOUNCED",
  "date": "2025-05-03",
  "limit": 10
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/executive-change \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "ANNOUNCED",
    "date": "2025-05-03",
    "limit": 10
  }'
```

***

### 3. Get C-Suite Changes Within a Date Range

Use `startDate` and `endDate` to retrieve executive change records announced during a specific period.

The Intellizence C-Suite Changes Dataset contains data beginning from `2021-01-01`.

#### Request Body

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-05-01",
  "endDate": "2025-05-31",
  "limit": 25
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/executive-change \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "ANNOUNCED",
    "startDate": "2025-05-01",
    "endDate": "2025-05-31",
    "limit": 25
  }'
```

***

### 4. Search by Company Domain

Use `companyDomain` to retrieve C-Suite change records for a specific company website domain.

This is recommended for CRM enrichment, account matching, account monitoring, data pipelines, and workflow automation because domains are usually more precise than company names.

#### Request Body

```json
{
  "companyDomain": "berkshirehathaway.com",
  "limit": 10
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/executive-change \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyDomain": "berkshirehathaway.com",
    "limit": 10
  }'
```

***

### 5. Search by Executive Title Category

Use `executiveTitleCategory` to retrieve executive changes by leadership function or role category.

Examples include `Chief Executive Officer ( CEO)/President/Managing Director`, `Chief Financial Officer ( CFO) / Head of Finance`, `Chief Operating Officer ( COO)`, `Chief Technology Officer ( CTO)`, `Chief Marketing Officer ( CMO)`, `Chief Revenue Officer ( CRO) / Head of Sales`, `Chief Information Security Officer ( CISO)"`, and `Board of Director`.

#### Request Body

```json
{
  "executiveTitleCategory": [
    "Chief Executive Officer ( CEO)/President/Managing Director",
    "Chief Financial Officer ( CFO) / Head of Finance"
  ],
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/executive-change \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "executiveTitleCategory": [
      "Chief Executive Officer ( CEO)/President/Managing Director",
      "Chief Financial Officer ( CFO) / Head of Finance"
    ],
    "limit": 20
  }'
```

***

### 6. Search by Executive Title

Use `executiveTitle` to retrieve records for a specific executive title.

This is useful when you want to search for exact or near-exact role titles such as Chief Executive Officer, Chief Financial Officer, Chief Operating Officer, Chief Technology Officer, or Chief Revenue Officer.

#### Request Body

```json
{
  "executiveTitle": "Chief Executive Officer",
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/executive-change \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "executiveTitle": "Chief Executive Officer",
    "limit": 20
  }'
```

***

### 7. Search by Executive Name

Use `executiveName` to retrieve C-Suite change records for a specific executive.

#### Request Body

```json
{
  "executiveName": "Greg Abel",
  "limit": 10
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/executive-change \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "executiveName": "Greg Abel",
    "limit": 10
  }'
```

***

### 8. Search by Reason

Use `reason` to retrieve executive changes by change reason.

Examples include `New Appointment`, `Promoted/Role Change`, `Retired`, `Terminated`, `Health`, `Resigned`, `Demise`, and `Others`.

#### Request Body

```json
{
  "reason": [
    "New Appointment",
    "Promoted/Role Change"
  ],
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/executive-change \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "reason": [
      "New Appointment",
      "Promoted/Role Change"
    ],
    "limit": 20
  }'
```

***

### 9. Search by Company Industry

Use `companyIndustry` to retrieve C-Suite changes for companies in one or more industries.

This is useful for sector monitoring, executive movement analysis, investment research, sales intelligence, and competitive intelligence.

#### Request Body

```json
{
  "companyIndustry": [
    "technology",
    "financial services"
  ],
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/executive-change \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyIndustry": [
      "technology",
      "financial services"
    ],
    "limit": 20
  }'
```

***

### 10. Use Multiple Filters Together

Combine filters to narrow results by date range, company type, industry, executive title category, reason, and company location.

#### Request Body

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-01-01",
  "endDate": "2025-05-31",
  "companyIndustry": [
    "technology"
  ],
  "companyType": [
    "Public"
  ],
  "executiveTitleCategory": [
    "Chief Executive Officer ( CEO)/President/Managing Director",
    "Chief Financial Officer ( CFO) / Head of Finance"
  ],
  "reason": [
    "New Appointment",
    "Promoted/Role Change"
  ],
  "companyLocation": "United States of America",
  "limit": 50
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/executive-change \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "ANNOUNCED",
    "startDate": "2025-01-01",
    "endDate": "2025-05-31",
    "companyIndustry": [
      "technology"
    ],
    "companyType": [
      "Public"
    ],
    "executiveTitleCategory": [
      "Chief Executive Officer ( CEO)/President/Managing Director",
      "Chief Financial Officer ( CFO) / Head of Finance"
    ],
    "reason": [
      "New Appointment",
      "Promoted/Role Change"
    ],
    "companyLocation": "United States of America",
    "limit": 50
  }'
```

***

## Use Case Examples

### 1. Daily Data Sync

Use this example when you want to pull newly added or updated C-Suite change records into your application, database, CRM, dashboard, or analytics workflow.

#### Recommended Filters

```json
{
  "dateType": "LAST-MODIFIED",
  "date": "2025-05-03",
  "limit": 100
}
```

#### Best For

* Data pipelines
* Daily refreshes
* Internal dashboards
* Alerts and workflow automation
* CRM and data warehouse enrichment

***

### 2. CRM or Account Enrichment

Use this example to check whether a company in your CRM has recent leadership changes.

#### Recommended Filters

```json
{
  "companyDomain": "berkshirehathaway.com",
  "dateType": "LAST-MODIFIED",
  "startDate": "2025-01-01",
  "endDate": "2025-05-31",
  "limit": 10
}
```

#### Best For

* CRM enrichment
* Account scoring
* Sales intelligence
* Customer intelligence
* Signal-based selling workflows

***

### 3. Sales and Prospecting

Use this example to identify accounts with new executives, role changes, or leadership transitions that may create new buying windows.

#### Recommended Filters

```json
{
  "dateType": "LAST-MODIFIED",
  "startDate": "2025-01-01",
  "endDate": "2025-05-31",
  "companyIndustry": [
    "technology"
  ],
  "executiveTitleCategory": [
    "Chief Executive Officer ( CEO)/President/Managing Director",
    "Chief Revenue Officer ( CRO) / Head of Sales",
    "Chief Marketing Officer ( CMO)"
  ],
  "reason": [
    "New Appointment",
    "Promoted/Role Change"
  ],
  "limit": 25
}
```

#### Best For

* Prospecting
* Account prioritization
* Trigger-based outreach
* Sales and marketing campaigns
* Go-to-market workflows

***

### 4. Executive Search and Talent Intelligence

Use this example to monitor senior leadership changes by role category, industry, and geography.

#### Recommended Filters

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-01-01",
  "endDate": "2025-12-31",
  "companyIndustry": [
    "healthcare",
    "technology"
  ],
  "executiveTitleCategory": [
    "Chief Executive Officer ( CEO)/President/Managing Director",
    "Chief Financial Officer ( CFO) / Head of Finance",
    "Chief Operating Officer ( COO)"
  ],
  "companyLocation": "United States of America",
  "limit": 50
}
```

#### Best For

* Executive search
* Leadership intelligence
* Talent market mapping
* Mandate discovery
* Board and senior leadership tracking

***

### 5. Risk and Customer Success Monitoring

Use this example to identify leadership exits, resignations, retirements, or executive changes that may signal account risk, strategic change, or organizational uncertainty.

#### Recommended Filters

```json
{
  "dateType": "LAST-MODIFIED",
  "startDate": "2025-01-01",
  "endDate": "2025-05-31",
  "reason": [
    "Resigned",
    "Retired",
    "Terminated"
  ],
  "executiveTitleCategory": [
    "Chief Executive Officer ( CEO)/President/Managing Director",
    "Chief Financial Officer ( CFO) / Head of Finance",
    "Chief Operating Officer ( COO)"
  ],
  "limit": 25
}
```

#### Best For

* Customer risk monitoring
* Renewal risk detection
* Account health scoring
* Vendor reassessment signals
* Strategic change monitoring

***

## Recommended Use Cases

| Use Case                                 | Recommended Filters                                                        |
| ---------------------------------------- | -------------------------------------------------------------------------- |
| Daily data sync                          | `dateType`, `date`, `limit`                                                |
| CRM or account enrichment                | `companyDomain`, `dateType`, `startDate`, `endDate`                        |
| Sales and prospecting                    | `companyIndustry`, `executiveTitleCategory`, `reason`, date range          |
| Executive search and talent intelligence | `executiveTitleCategory`, `companyIndustry`, `companyLocation`, date range |
| Risk and customer success monitoring     | `reason`, `executiveTitleCategory`, date range                             |

***

## Best Practices

### Prefer company domain for company matching

For CRM enrichment, data pipelines, account matching, and automated workflows, use `companyDomain` when available.

Company domains are usually more precise than company names and help reduce duplicate or ambiguous matches.

```json
{
  "companyDomain": "berkshirehathaway.com",
  "limit": 10
}
```

### Use company name for manual lookup

You can also use `companyName` to search for C-Suite change records by company name.

Company name search is useful for manual lookup, but for automated workflows, CRM enrichment, and account matching, use `companyDomain` when available.

```json
{
  "companyName": "Berkshire Hathaway",
  "limit": 10
}
```

### Use ticker for public company monitoring

For public companies, use `companyTicker` when you want to search by stock ticker.

```json
{
  "companyTicker": "BRK.A",
  "limit": 10
}
```

### Use executive title category for role-based filtering

Use `executiveTitleCategory` when you want to filter by standardized leadership role categories.

```json
{
  "executiveTitleCategory": [
    "Chief Executive Officer ( CEO)/President/Managing Director",
    "Chief Financial Officer ( CFO) / Head of Finance"
  ],
  "limit": 25
}
```

### Use executive title for exact title search

Use `executiveTitle` when you want to search for a specific executive title.

```json
{
  "executiveTitle": "Chief Executive Officer",
  "limit": 25
}
```

### Use reason to classify leadership changes

Use `reason` to filter by the reason for the executive change.

```json
{
  "reason": [
    "New Appointment",
    "Promoted/Role Change",
    "Resigned"
  ],
  "limit": 25
}
```

### Use `LAST-MODIFIED` for daily syncs

For recurring syncs, alerts, and automated workflows, use `LAST-MODIFIED`.

```json
{
  "dateType": "LAST-MODIFIED",
  "date": "2025-05-03"
}
```

This helps retrieve records that were newly added or updated on that date.

### Use `ANNOUNCED` for event-date research

For research based on when a C-Suite change was announced, use `ANNOUNCED`.

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-01-01",
  "endDate": "2025-05-31"
}
```

### Use `limit` to control result size

The default limit is `100` records if no limit is provided.

```json
{
  "limit": 100
}
```

### Combine filters for more precise results

You can combine multiple filters in a single request to narrow your results.

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-01-01",
  "endDate": "2025-05-31",
  "companyIndustry": [
    "technology"
  ],
  "executiveTitleCategory": [
    "Chief Executive Officer ( CEO)/President/Managing Director"
  ],
  "reason": [
    "New Appointment"
  ],
  "companyLocation": "United States of America",
  "limit": 50
}
```

***

## Notes

* All parameters are optional.
* Dates should be provided in `YYYY-MM-DD` format.
* The Intellizence C-Suite Changes Dataset contains data beginning from `2021-01-01`.
* Use `LAST-MODIFIED` when you want newly added or updated records.
* Use `ANNOUNCED` when you want records based on the executive change announcement date.
* Use `companyDomain` for CRM matching, account enrichment, account monitoring, and workflow automation.
* Use `companyName` for manual lookup when the company domain is not available.
* Use `companyTicker` for public company monitoring.
* Use `executiveName` to search for a specific executive.
* Use `executiveTitle` to search by exact or near-exact job title.
* Use `executiveTitleCategory` for standardized role-category filtering.
* Use `reason` to filter by change type, such as new appointment, promotion, resignation, retirement, termination, or other leadership changes.


# Intellizence Data & Security Breaches Signals API

This REST API provides continuous access to data & security breaches & other cyber security related incidents data from the Intellizence Data & Security Breaches Dataset.

{% hint style="info" %}
Best  suited for :

* Continuous monitoring of data & security breaches and cyber incidents in companies
* Trigger alerts and automated workflows
* Cyber incident trends and analysis
* Power AI agents and internal intelligence platforms
  {% endhint %}

> **Ready to get started?** [**Request your API key**](https://intellizence.com/api-trial/) and start building.\
> **Questions?** [**Schedule a call**](https://intellizence.com/schedule-a-demo/) or email us at <sales@intellizence.com>.

**Security Notice:** Please keep the API Key secure. Do not share your API key in publicly accessible areas such as GitHub, client-side code, and so forth.

## Submit Data and Security Breaches Dataset Request

> This REST API endpoint provides access to both ongoing and historical data and security breaches data from the Intellizence Data and Security Breaches Dataset. \
> \
> Users can search data using various parameters- \`dateType\`,\`startDate\`,\`endDate\`,\`date\`,\`companyDomain\`,\`companyName\`,\`companyIndustry\`,\`companyLocation\`,\`companyType\`, \`companyTicker\`,\`incidentType\`, and \`peopleImpacted\`. \
> \
> Users can limit the number of records returned using the \`limit\` parameter. All parameters are optional.\
> \
> The API key has to be passed in HTTP header with the name \`x-api-key\`.

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Data and Security Breaches Signals API","version":"1.0"},"servers":[{"url":"https://connect.intellizence.com"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","name":"x-api-key","in":"header"}},"schemas":{"dataset_databreach_body":{"type":"object","properties":{"dateType":{"type":"string","description":"Choose the date type used to filter records.The default value is 'ANNOUNCED'. To get the daily update of records created or modified, 'LAST-MODIFIED' is recommended.","enum":["ANNOUNCED","LAST-MODIFIED"]},"startDate":{"type":"string","description":"The start date (YYYY-MM-DD) from which data & security breaches data is needed. Intellizence Data and Security Breaches Dataset contains data beginning from 2022-01-01.","format":"date"},"endDate":{"type":"string","description":"The end date (YYYY-MM-DD) up to which data & security breaches data is needed.","format":"date"},"date":{"type":"string","description":"Exact date (YYYY-MM-DD) for which the data & security breaches data is needed.","format":"date"},"companyName":{"type":"string","description":"Name(s) of the company for which data & security breaches data is needed.Partial name matching is supported.Multiple values can be provided either as a comma-separated string or as an array."},"companyDomain":{"type":"string","description":"The website domain(s) of the company for which the data & security breaches data is needed. Partial domain matching is supported. Multiple values can be provided either as a comma-separated string or as an array."},"companyIndustry":{"type":"string","description":"The industry or industries of the companies for which data & security breaches data is requested. Industries are predefined by Intellizence, and only the values listed below are supported. Multiple values can be provided as an array.","enum":["accounting, audit & tax","advertising & communication","agriculture, animal husbandry & forestry","angels/ venture capital/ private equity","automobile","aviation","banking","bio-technology","business services","chemicals & fertilizers","clean technology","conglomerate","consulting","consumer products","consumer services","defence","distribution","e-commerce","economic development","education","energy & utilities","engineering, procurement & construction","financial services","gambling","gaming","government","healthcare","human resources","insurance","it services & outsourcing","legal","logistics & supply chain","manufacturing","media & entertainment","medical device","metals & mining","not-for-profit/ ngo","others","pharmaceuticals","publishing","railways","real estate","regulatory","restaurants & food services","retail","security","shipping & ports","spac/blank check","sports","technology","telecommunication","textiles","tourism & hospitality","trading","transportation"]},"companyLocation":{"type":"string","description":"The location of the company headquarters for which data & security breaches data is needed. The location can be specified as a city, state/province, or country. Multiple values can be provided either as a comma-separated string or as an array."},"companyType":{"type":"string","description":"The type of company or organization for which data & security breaches data is needed. The company types are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Public","Private","Government/Regulator","Not-for-profit","Others"]},"companyTicker":{"type":"string","description":"Stock ticker of the company"},"incidentType":{"type":"string","description":"The type of cyber security incident. The incident types are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Data Breach/Theft/Leak","Security Breach","Ransomware","Malware","DDOS","POS Attack","Hack","Others"]},"peopleImpacted":{"type":"number","description":"Number of people impacted due to the cyber security incident.","format":"float"},"limit":{"type":"integer","description":"The maximum number of records to be returned."}}},"DataBreachSearchResponse":{"required":["code","count","dataset"],"type":"object","properties":{"code":{"type":"integer"},"count":{"type":"integer"},"dataset":{"type":"array","items":{"$ref":"#/components/schemas/inline_response_200"}},"openingBalance":{"type":"integer","nullable":true},"closingBalance":{"type":"integer","nullable":true},"creditsConsumed":{"type":"integer","nullable":true}}},"inline_response_200":{"type":"object","properties":{"id":{"type":"string","description":"Unique ID of the record"},"announcedDate":{"type":"string","description":"Date of incident announcement","format":"date"},"company":{"$ref":"#/components/schemas/inline_response_200_company"},"peopleImpacted":{"pattern":"^(>|>=|<|<=|=|!=)?\\d+(,\\d+)?$","type":"number","description":"Number of people impacted due to the cyber security incident. The allowed operators are >, >=, <, <=,=,!=, (MinimumValue),(Maximum Value). Examples: >1000, >=1000, <1000, <=1000,=1000,!=1000, (1000,4000)","format":"float"},"incidentType":{"type":"string","description":"Type of cyber security incident"},"noticeDate":{"type":"string","description":"Date of notification about the incident to the regulators","format":"date"},"thirdPartyCompany":{"$ref":"#/components/schemas/inline_response_200_thirdPartyCompany"},"sourceType":{"type":"string","description":"Source type of the cyber security incident announcement - News/Press Wires,Regulatory Filings. The values for this data point are available only for records that were created after May 1st, 2025."},"lastModified":{"type":"string","description":"The last modified date of the record.","format":"date"},"title":{"type":"string","description":"Source title - News or press release or regulatory filing headline"},"url":{"type":"string","description":"URL of the source document"}}},"inline_response_200_company":{"type":"object","properties":{"name":{"type":"string","description":"Company name"},"domain":{"type":"string","description":"Company website domain"},"industries":{"type":"array","description":"Company industry classification by Intellizence","items":{"type":"string"}},"location":{"type":"string","description":"Company HQ location"},"type":{"type":"string","description":"Company type"},"ticker":{"type":"array","description":"Company stock ticker (if public)","items":{"type":"string"}},"stockExchange":{"type":"array","description":"Stock exchange where the company is listed (if public)","items":{"type":"string"}}}},"inline_response_200_thirdPartyCompany":{"type":"object","properties":{"name":{"type":"string"},"domain":{"type":"string"}},"description":"Third-party company whose product/services caused this cyber security incident ( if disclosed). The values for this data point are available only for records that were created after May 1st, 2025."}}},"paths":{"/api/dataset/data-breach":{"post":{"summary":"Submit Data and Security Breaches Dataset Request","description":"This REST API endpoint provides access to both ongoing and historical data and security breaches data from the Intellizence Data and Security Breaches Dataset. \n\nUsers can search data using various parameters- `dateType`,`startDate`,`endDate`,`date`,`companyDomain`,`companyName`,`companyIndustry`,`companyLocation`,`companyType`, `companyTicker`,`incidentType`, and `peopleImpacted`. \n\nUsers can limit the number of records returned using the `limit` parameter. All parameters are optional.\n\nThe API key has to be passed in HTTP header with the name `x-api-key`.","operationId":"getDataBreachDataset","parameters":[{"name":"x-api-key","in":"header","description":"Intellizence API key for authenticating the request.","required":true,"schema":{"type":"string"}}],"requestBody":{"description":"Intellizence Data and Security Breaches Dataset request body","content":{"application/json":{"schema":{"$ref":"#/components/schemas/dataset_databreach_body"}}}},"responses":{"200":{"description":"Successful response.\n\nNote: Credit fields (openingBalance, closingBalance, creditsConsumed) are returned only for Pay-Per-Use billing.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/DataBreachSearchResponse"}}}},"400":{"description":"400 - Bad Request\n\nBad request, possibly missing required parameters, invalid data, invalid or missing API key.\n\n- 701 - Start Date is not in YYYY-MM-DD format.\n- 702 - End Date is not in YYYY-MM-DD format.\n- 703 - Plan or resource not subscribed\n- 709 - No companies configured for this account.\n- 710 - No triggers configured for this account."},"402":{"description":"402 - Payment Required\n\n- 704 - Payment is pending.\n- 712 - Insufficient credits for this request."},"403":{"description":"403 - Forbidden\n\n- 707 - Subscription has expired.\n- 708 - Start date is outside your subscription's allowed date range."},"500":{"description":"500 - Internal Server Error\n\n- 715 - A technical error occurred.\n- 799 - A technical error occurred."}}}}}}
```

## The dataset\_databreach\_body object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Data and Security Breaches Signals API","version":"1.0"},"components":{"schemas":{"dataset_databreach_body":{"type":"object","properties":{"dateType":{"type":"string","description":"Choose the date type used to filter records.The default value is 'ANNOUNCED'. To get the daily update of records created or modified, 'LAST-MODIFIED' is recommended.","enum":["ANNOUNCED","LAST-MODIFIED"]},"startDate":{"type":"string","description":"The start date (YYYY-MM-DD) from which data & security breaches data is needed. Intellizence Data and Security Breaches Dataset contains data beginning from 2022-01-01.","format":"date"},"endDate":{"type":"string","description":"The end date (YYYY-MM-DD) up to which data & security breaches data is needed.","format":"date"},"date":{"type":"string","description":"Exact date (YYYY-MM-DD) for which the data & security breaches data is needed.","format":"date"},"companyName":{"type":"string","description":"Name(s) of the company for which data & security breaches data is needed.Partial name matching is supported.Multiple values can be provided either as a comma-separated string or as an array."},"companyDomain":{"type":"string","description":"The website domain(s) of the company for which the data & security breaches data is needed. Partial domain matching is supported. Multiple values can be provided either as a comma-separated string or as an array."},"companyIndustry":{"type":"string","description":"The industry or industries of the companies for which data & security breaches data is requested. Industries are predefined by Intellizence, and only the values listed below are supported. Multiple values can be provided as an array.","enum":["accounting, audit & tax","advertising & communication","agriculture, animal husbandry & forestry","angels/ venture capital/ private equity","automobile","aviation","banking","bio-technology","business services","chemicals & fertilizers","clean technology","conglomerate","consulting","consumer products","consumer services","defence","distribution","e-commerce","economic development","education","energy & utilities","engineering, procurement & construction","financial services","gambling","gaming","government","healthcare","human resources","insurance","it services & outsourcing","legal","logistics & supply chain","manufacturing","media & entertainment","medical device","metals & mining","not-for-profit/ ngo","others","pharmaceuticals","publishing","railways","real estate","regulatory","restaurants & food services","retail","security","shipping & ports","spac/blank check","sports","technology","telecommunication","textiles","tourism & hospitality","trading","transportation"]},"companyLocation":{"type":"string","description":"The location of the company headquarters for which data & security breaches data is needed. The location can be specified as a city, state/province, or country. Multiple values can be provided either as a comma-separated string or as an array."},"companyType":{"type":"string","description":"The type of company or organization for which data & security breaches data is needed. The company types are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Public","Private","Government/Regulator","Not-for-profit","Others"]},"companyTicker":{"type":"string","description":"Stock ticker of the company"},"incidentType":{"type":"string","description":"The type of cyber security incident. The incident types are pre-defined by Intellizence and only the values listed below will be accepted. Multiple values can be provided either as a comma-separated string or as an array.","enum":["Data Breach/Theft/Leak","Security Breach","Ransomware","Malware","DDOS","POS Attack","Hack","Others"]},"peopleImpacted":{"type":"number","description":"Number of people impacted due to the cyber security incident.","format":"float"},"limit":{"type":"integer","description":"The maximum number of records to be returned."}}}}}}
```

## The inline\_response\_200 object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Data and Security Breaches Signals API","version":"1.0"},"components":{"schemas":{"inline_response_200":{"type":"object","properties":{"id":{"type":"string","description":"Unique ID of the record"},"announcedDate":{"type":"string","description":"Date of incident announcement","format":"date"},"company":{"$ref":"#/components/schemas/inline_response_200_company"},"peopleImpacted":{"pattern":"^(>|>=|<|<=|=|!=)?\\d+(,\\d+)?$","type":"number","description":"Number of people impacted due to the cyber security incident. The allowed operators are >, >=, <, <=,=,!=, (MinimumValue),(Maximum Value). Examples: >1000, >=1000, <1000, <=1000,=1000,!=1000, (1000,4000)","format":"float"},"incidentType":{"type":"string","description":"Type of cyber security incident"},"noticeDate":{"type":"string","description":"Date of notification about the incident to the regulators","format":"date"},"thirdPartyCompany":{"$ref":"#/components/schemas/inline_response_200_thirdPartyCompany"},"sourceType":{"type":"string","description":"Source type of the cyber security incident announcement - News/Press Wires,Regulatory Filings. The values for this data point are available only for records that were created after May 1st, 2025."},"lastModified":{"type":"string","description":"The last modified date of the record.","format":"date"},"title":{"type":"string","description":"Source title - News or press release or regulatory filing headline"},"url":{"type":"string","description":"URL of the source document"}}},"inline_response_200_company":{"type":"object","properties":{"name":{"type":"string","description":"Company name"},"domain":{"type":"string","description":"Company website domain"},"industries":{"type":"array","description":"Company industry classification by Intellizence","items":{"type":"string"}},"location":{"type":"string","description":"Company HQ location"},"type":{"type":"string","description":"Company type"},"ticker":{"type":"array","description":"Company stock ticker (if public)","items":{"type":"string"}},"stockExchange":{"type":"array","description":"Stock exchange where the company is listed (if public)","items":{"type":"string"}}}},"inline_response_200_thirdPartyCompany":{"type":"object","properties":{"name":{"type":"string"},"domain":{"type":"string"}},"description":"Third-party company whose product/services caused this cyber security incident ( if disclosed). The values for this data point are available only for records that were created after May 1st, 2025."}}}}
```

## The inline\_response\_200\_company object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Data and Security Breaches Signals API","version":"1.0"},"components":{"schemas":{"inline_response_200_company":{"type":"object","properties":{"name":{"type":"string","description":"Company name"},"domain":{"type":"string","description":"Company website domain"},"industries":{"type":"array","description":"Company industry classification by Intellizence","items":{"type":"string"}},"location":{"type":"string","description":"Company HQ location"},"type":{"type":"string","description":"Company type"},"ticker":{"type":"array","description":"Company stock ticker (if public)","items":{"type":"string"}},"stockExchange":{"type":"array","description":"Stock exchange where the company is listed (if public)","items":{"type":"string"}}}}}}}
```

## The inline\_response\_200\_thirdPartyCompany object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Data and Security Breaches Signals API","version":"1.0"},"components":{"schemas":{"inline_response_200_thirdPartyCompany":{"type":"object","properties":{"name":{"type":"string"},"domain":{"type":"string"}},"description":"Third-party company whose product/services caused this cyber security incident ( if disclosed). The values for this data point are available only for records that were created after May 1st, 2025."}}}}
```


# Intellizence Data & Security Breaches API Sample Requests

Sample requests for the Intellizence Data & Security Breaches API, including filters for date, company domain, industry, company location, company type, ticker, incident type, people impacted, and lim

## Data & Security Breaches API Sample Requests

Use these sample API requests to retrieve data breach, security breach, ransomware, malware, DDoS, POS attack, hack, and other cybersecurity incident records from the Intellizence Data & Security Breaches Dataset.

These examples show common ways to filter data and security breach records by date, company domain, industry, company location, company type, ticker, incident type, people impacted, and limit.

{% hint style="info" %}
All request parameters are optional. You can use a single filter or combine multiple filters based on your use case.
{% endhint %}

***

### Endpoint

```http
POST https://connect.intellizence.com/api/dataset/data-breach
```

### Authentication

Include your API key in the request header.

```http
x-api-key: YOUR_API_KEY
```

### Content Type

```http
Content-Type: application/json
```

***

## 10 Sample API Requests

### 1. Get Daily Updated Records

Use `dateType: "LAST-MODIFIED"` to retrieve records that were created or updated on a specific date.

This is recommended for daily syncs, alerts, enrichment workflows, and automated data pipelines.

#### Request Body

```json
{
  "dateType": "LAST-MODIFIED",
  "date": "2025-05-05",
  "limit": 5
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/data-breach \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "LAST-MODIFIED",
    "date": "2025-05-05",
    "limit": 5
  }'
```

***

### 2. Get Incidents Announced on a Specific Date

Use `dateType: "ANNOUNCED"` and `date` to retrieve data and security breach records announced on a specific date.

#### Request Body

```json
{
  "dateType": "ANNOUNCED",
  "date": "2025-05-05",
  "limit": 10
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/data-breach \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "ANNOUNCED",
    "date": "2025-05-05",
    "limit": 10
  }'
```

***

### 3. Get Incidents Within a Date Range

Use `startDate` and `endDate` to retrieve data and security breach records announced during a specific period.

The Intellizence Data & Security Breaches Dataset contains data beginning from `2022-01-01`.

#### Request Body

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-05-01",
  "endDate": "2025-05-31",
  "limit": 25
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/data-breach \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "ANNOUNCED",
    "startDate": "2025-05-01",
    "endDate": "2025-05-31",
    "limit": 25
  }'
```

***

### 4. Search by Company Domain

Use `companyDomain` to retrieve data and security breach records for a specific company website domain.

This is recommended for CRM enrichment, vendor risk monitoring, account matching, data pipelines, and workflow automation because domains are usually more precise than company names.

#### Request Body

```json
{
  "companyDomain": "ameriprise.com",
  "limit": 10
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/data-breach \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyDomain": "ameriprise.com",
    "limit": 10
  }'
```

***

### 5. Search by Company Industry

Use `companyIndustry` to retrieve data and security breach records for companies in one or more industries.

This is useful for cyber risk analysis, sector monitoring, market research, vendor risk intelligence, and investment research.

#### Request Body

```json
{
  "companyIndustry": [
    "financial services",
    "healthcare"
  ],
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/data-breach \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyIndustry": [
      "financial services",
      "healthcare"
    ],
    "limit": 20
  }'
```

***

### 6. Search by Company Location

Use `companyLocation` to retrieve data and security breach records for companies headquartered in a specific city, state, province, country, or region.

#### Request Body

```json
{
  "companyLocation": "Minneapolis,Minnesota,United States of America",
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/data-breach \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyLocation": "Minneapolis,Minnesota,United States of America",
    "limit": 20
  }'
```

***

### 7. Search by Incident Type

Use `incidentType` to retrieve cybersecurity incidents by type.

Examples include `Data Breach/Theft/Leak`, `Security Breach`, `Ransomware`, `Malware`, `DDOS`, `POS Attack`, `Hack`, and `Others`.

#### Request Body

```json
{
  "incidentType": [
    "Data Breach/Theft/Leak",
    "Ransomware"
  ],
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/data-breach \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "incidentType": [
      "Data Breach/Theft/Leak",
      "Ransomware"
    ],
    "limit": 20
  }'
```

***

### 8. Search by People Impacted

Use `peopleImpacted` to filter data and security breach records by the number of affected individuals.

You can use comparison operators such as `>`, `>=`, `<`, `<=`, `=`, and `!=`.

#### Request Body

```json
{
  "peopleImpacted": ">100000",
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/data-breach \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "peopleImpacted": ">100000",
    "limit": 20
  }'
```

***

### 9. Search by Public Company Ticker

Use `companyTicker` to retrieve data and security breach records for a public company.

#### Request Body

```json
{
  "companyTicker": "AMP",
  "limit": 10
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/data-breach \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyTicker": "AMP",
    "limit": 10
  }'
```

***

### 10. Use Multiple Filters Together

Combine filters to narrow results by date range, industry, company type, incident type, people impacted, and company location.

#### Request Body

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-01-01",
  "endDate": "2025-05-31",
  "companyIndustry": [
    "financial services",
    "healthcare"
  ],
  "companyType": [
    "Public"
  ],
  "incidentType": [
    "Data Breach/Theft/Leak",
    "Ransomware"
  ],
  "peopleImpacted": ">100000",
  "companyLocation": "United States of America",
  "limit": 50
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/data-breach \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "ANNOUNCED",
    "startDate": "2025-01-01",
    "endDate": "2025-05-31",
    "companyIndustry": [
      "financial services",
      "healthcare"
    ],
    "companyType": [
      "Public"
    ],
    "incidentType": [
      "Data Breach/Theft/Leak",
      "Ransomware"
    ],
    "peopleImpacted": ">100000",
    "companyLocation": "United States of America",
    "limit": 50
  }'
```

***

## 5 Use Case Examples

### 1. Daily Data Sync

Use this example when you want to pull newly added or updated data and security breach records into your application, database, CRM, dashboard, or analytics workflow.

#### Recommended Filters

```json
{
  "dateType": "LAST-MODIFIED",
  "date": "2025-05-05",
  "limit": 100
}
```

#### Best For

* Data pipelines
* Daily refreshes
* Internal dashboards
* Alerts and workflow automation
* CRM and data warehouse enrichment

***

### 2. Vendor Risk and Third-Party Monitoring

Use this example to check whether a vendor, supplier, partner, or third-party company has recent cybersecurity incident activity.

#### Recommended Filters

```json
{
  "companyDomain": "ameriprise.com",
  "dateType": "LAST-MODIFIED",
  "startDate": "2025-01-01",
  "endDate": "2025-05-31",
  "limit": 10
}
```

#### Best For

* Vendor risk monitoring
* Third-party risk management
* Supplier monitoring
* Compliance workflows
* Risk scoring

***

### 3. Sector Cyber Risk Analysis

Use this example to track data breaches and cybersecurity incidents across a specific industry.

#### Recommended Filters

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-01-01",
  "endDate": "2025-05-31",
  "companyIndustry": [
    "financial services",
    "healthcare"
  ],
  "incidentType": [
    "Data Breach/Theft/Leak",
    "Ransomware"
  ],
  "limit": 50
}
```

#### Best For

* Sector risk monitoring
* Cyber risk intelligence
* Market research
* Investment research
* Compliance and security research

***

### 4. Large Breach Monitoring

Use this example to monitor incidents affecting a large number of individuals.

#### Recommended Filters

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-01-01",
  "endDate": "2025-12-31",
  "peopleImpacted": ">1000000",
  "incidentType": [
    "Data Breach/Theft/Leak",
    "Security Breach"
  ],
  "limit": 50
}
```

#### Best For

* Major incident tracking
* Risk intelligence
* Regulatory monitoring
* Insurance and cyber underwriting research
* Executive reporting

***

### 5. Sales and Account Monitoring

Use this example to identify accounts with recent cybersecurity incidents that may signal risk, compliance needs, incident response needs, or vendor reassessment.

#### Recommended Filters

```json
{
  "dateType": "LAST-MODIFIED",
  "startDate": "2025-01-01",
  "endDate": "2025-05-31",
  "companyIndustry": [
    "financial services",
    "healthcare",
    "technology"
  ],
  "incidentType": [
    "Data Breach/Theft/Leak",
    "Ransomware",
    "Security Breach"
  ],
  "limit": 25
}
```

#### Best For

* Account monitoring
* Risk-based outreach
* Cybersecurity sales intelligence
* Customer risk monitoring
* Compliance and security workflows

***

## Recommended Use Cases

| Use Case                               | Recommended Filters                                 |
| -------------------------------------- | --------------------------------------------------- |
| Daily data sync                        | `dateType`, `date`, `limit`                         |
| Vendor risk and third-party monitoring | `companyDomain`, `dateType`, `startDate`, `endDate` |
| Sector cyber risk analysis             | `companyIndustry`, `incidentType`, date range       |
| Large breach monitoring                | `peopleImpacted`, `incidentType`, date range        |
| Sales and account monitoring           | `companyIndustry`, `incidentType`, date range       |

***

## Best Practices

### Prefer company domain for company matching

For CRM enrichment, vendor risk monitoring, data pipelines, account matching, and automated workflows, use `companyDomain` when available.

Company domains are usually more precise than company names and help reduce duplicate or ambiguous matches.

```json
{
  "companyDomain": "ameriprise.com",
  "limit": 10
}
```

### Use company name for manual lookup

You can also use `companyName` to search for data and security breach records by company name.

Company name search is useful for manual lookup, but for automated workflows, CRM enrichment, and account matching, use `companyDomain` when available.

```json
{
  "companyName": "Ameriprise Financial",
  "limit": 10
}
```

### Use ticker for public company monitoring

For public companies, use `companyTicker` when you want to search by stock ticker.

```json
{
  "companyTicker": "AMP",
  "limit": 10
}
```

### Use `LAST-MODIFIED` for daily syncs

For recurring syncs, alerts, and automated workflows, use `LAST-MODIFIED`.

```json
{
  "dateType": "LAST-MODIFIED",
  "date": "2025-05-05"
}
```

This helps retrieve records that were newly added or updated on that date.

### Use `ANNOUNCED` for event-date research

For research based on when a data or security breach was announced, use `ANNOUNCED`.

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-01-01",
  "endDate": "2025-05-31"
}
```

### Use incident type to classify cybersecurity events

Use `incidentType` to distinguish between data breaches, security breaches, ransomware, malware, DDoS, POS attacks, hacks, and other incident types.

```json
{
  "incidentType": [
    "Data Breach/Theft/Leak",
    "Ransomware",
    "Security Breach"
  ],
  "limit": 25
}
```

### Use people impacted for severity-based filtering

Use `peopleImpacted` to filter incidents by the number of affected individuals.

```json
{
  "peopleImpacted": ">100000",
  "limit": 25
}
```

### Use company location for headquarters-based analysis

Use `companyLocation` when you want to filter by where the affected company is headquartered.

```json
{
  "companyLocation": "Minneapolis,Minnesota,United States of America",
  "limit": 20
}
```

### Use `limit` to control result size

The default limit is `100` records if no limit is provided.

```json
{
  "limit": 100
}
```

### Combine filters for more precise results

You can combine multiple filters in a single request to narrow your results.

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2025-01-01",
  "endDate": "2025-05-31",
  "companyIndustry": [
    "financial services"
  ],
  "incidentType": [
    "Data Breach/Theft/Leak",
    "Ransomware"
  ],
  "peopleImpacted": ">100000",
  "limit": 50
}
```

***

## Notes

* All parameters are optional.
* Dates should be provided in `YYYY-MM-DD` format.
* The Intellizence Data & Security Breaches Dataset contains data beginning from `2022-01-01`.
* Use `LAST-MODIFIED` when you want newly added or updated records.
* Use `ANNOUNCED` when you want records based on the breach or incident announcement date.
* Use `companyDomain` for CRM matching, vendor risk monitoring, account enrichment, account monitoring, and workflow automation.
* Use `companyName` for manual lookup when the company domain is not available.
* Use `companyTicker` for public company monitoring.
* Use `companyIndustry` for sector-level cyber risk analysis.
* Use `companyLocation` for headquarters-based filtering.
* Use `incidentType` to filter by cybersecurity incident type.
* Use `peopleImpacted` to filter by the number of individuals affected.


# Intellizence Company News Signals API

The Intellizence Company News Signals API provides latest, curated news intelligence for specified company domains and trigger events.

> **Ready to get started?** [**Request your API key**](https://intellizence.com/api-trial/) and start building.&#x20;
>
> **Questions?** [**Schedule a call**](https://intellizence.com/schedule-a-demo/) or email us at <sales@intellizence.com>.

**Security Notice:** Please keep the API Key secure. Do not share your API key in publicly accessible areas such as GitHub, client-side code, and so forth.

## Search for news signals by Company Domain(s), Intellizence Trigger Code(s) & News Published Date range

> Returns curated news articles for the given company domain(s), trigger code(s), and published date range. A news record may include clustered or related articles under \`similarNews\`.\
> \
> Users can search data using the following parameters: \`companyDomains\`, \`triggerCodes\`, \`startDate\`, \`endDate\`, and \`limit\`\
> \
> Users can limit the number of records returned using the \`limit\` parameter. The default limit is \`100\`. All parameters are optional.\
> \
> The API key must be passed in the HTTP header as \`x-api-key\`.

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Company News Signals API","version":"1.0"},"servers":[{"url":"https://connect.intellizence.com","description":"Intellizence API"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","name":"x-api-key","in":"header"}},"schemas":{"NewsSearchRequest":{"type":"object","properties":{"companyDomains":{"type":"array","description":"Website domain of the Companies for which news signal are required. Multiple domains can be passed as an array.","items":{"type":"string"}},"triggerCodes":{"type":"array","description":"Intellizence Trigger Codes used to filter relevant news signals. Multiple Trigger Code(s) can be passed as an array. For a categorized reference of all codes, [click here](https://docs.intellizence.com/company-news-signal-api/trigger-codes-reference)","items":{"type":"string","enum":["KW_518","KW_519","KW_520","KW_534","KW_535","KW_666","KW_502","KW_536","KW_591","KW_741","KW_514","KW_708","KW_516","KW_527","KW_529","KW_640","KW_713","KW_510","KW_583","KW_688","KW_521","KW_566","KW_642","KW_537","KW_801","KW_512","KW_513","KW_528","KW_687","KW_584","KW_586","KW_641","KW_532","KW_610","KW_143","KW_533","KW_709","KW_556","KW_571","KW_647","KW_14","KW_526","KW_711","KW_522","KW_523","KW_585","KW_613","KW_699","KW_589","KW_654","KW_665","KW_678","KW_530","KW_601","KW_677","KW_531","KW_616","KW_524","KW_673","KW_700","KW_737"]}},"startDate":{"type":"string","description":"News published start date. Enter the date in YYYY-MM-DD format.","format":"date"},"endDate":{"type":"string","description":"News published end date. Enter the date in YYYY-MM-DD format.","format":"date"},"limit":{"type":"integer","description":"Maximum number of records to return","default":100}}},"NewsSearchResponse":{"required":["code","count","news"],"type":"object","properties":{"code":{"type":"integer"},"count":{"type":"integer"},"news":{"type":"array","items":{"$ref":"#/components/schemas/NewsItem"}},"openingBalance":{"type":"integer","description":"Returned only for the 'Pay-Per-Use' billing type."},"closingBalance":{"type":"integer","description":"Returned only for the 'Pay-Per-Use' billing type."},"creditsConsumed":{"type":"integer","description":"Returned only for the 'Pay-Per-Use' billing type."}}},"NewsItem":{"type":"object","properties":{"publisher":{"type":"string"},"title":{"type":"string"},"url":{"type":"string","format":"uri"},"desc":{"type":"string"},"hash":{"type":"string"},"triggerNames":{"type":"array","items":{"type":"string"}},"companyNames":{"type":"array","items":{"type":"string"}},"triggerCodes":{"type":"array","items":{"type":"string"}},"companyDomains":{"type":"array","items":{"type":"string"}},"publishDate":{"type":"string","format":"date"},"similarNews":{"type":"array","items":{"$ref":"#/components/schemas/SimilarNewsItem"}}}},"SimilarNewsItem":{"type":"object","properties":{"hash":{"type":"string"},"title":{"type":"string"},"desc":{"type":"string"},"publisher":{"type":"string"},"url":{"type":"string","format":"uri"},"publishDate":{"type":"string","format":"date-time"}}}}},"paths":{"/api/news":{"post":{"summary":"Search for news signals by Company Domain(s), Intellizence Trigger Code(s) & News Published Date range","description":"Returns curated news articles for the given company domain(s), trigger code(s), and published date range. A news record may include clustered or related articles under `similarNews`.\n\nUsers can search data using the following parameters: `companyDomains`, `triggerCodes`, `startDate`, `endDate`, and `limit`\n\nUsers can limit the number of records returned using the `limit` parameter. The default limit is `100`. All parameters are optional.\n\nThe API key must be passed in the HTTP header as `x-api-key`.","operationId":"serachCompanyNewsSignals","parameters":[{"name":"x-api-key","in":"header","description":"Intellizence API key","required":true,"schema":{"type":"string"}}],"requestBody":{"content":{"application/json":{"schema":{"$ref":"#/components/schemas/NewsSearchRequest"}}},"required":true},"responses":{"200":{"description":"Successful response.\n\nNote: Credit fields (openingBalance, closingBalance, creditsConsumed) are returned only for Pay-Per-Use billing.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/NewsSearchResponse"}}}},"400":{"description":"400 - Bad Request\n\nBad request, possibly missing required parameters, invalid data, invalid or missing API key.\n\n- 701 - Invalid Start Date format (YYYY-MM-DD required)\n- 702 - Invalid End Date format (YYYY-MM-DD required)\n- 706 - Requested resource/data product is not included in the current subscription plan\n- 709 - No companies configured for this account\n- 710 - No triggers configured for this account"},"402":{"description":"402 - Payment Required\n- 704 - Payment is pending\n- 712 - Insufficient credits for this request"},"403":{"description":"403 - Forbidden\n- 703 - Plan or resource not subscribed\n- 707 - Subscription has expired\n- 708 - Start date is outside your subscription’s allowed date range"},"500":{"description":"500 - Internal Server Error\n- 715 - A technical error occurred\n- 799 - A technical error occurred"}}}}}}
```

## The NewsSearchRequest object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Company News Signals API","version":"1.0"},"components":{"schemas":{"NewsSearchRequest":{"type":"object","properties":{"companyDomains":{"type":"array","description":"Website domain of the Companies for which news signal are required. Multiple domains can be passed as an array.","items":{"type":"string"}},"triggerCodes":{"type":"array","description":"Intellizence Trigger Codes used to filter relevant news signals. Multiple Trigger Code(s) can be passed as an array. For a categorized reference of all codes, [click here](https://docs.intellizence.com/company-news-signal-api/trigger-codes-reference)","items":{"type":"string","enum":["KW_518","KW_519","KW_520","KW_534","KW_535","KW_666","KW_502","KW_536","KW_591","KW_741","KW_514","KW_708","KW_516","KW_527","KW_529","KW_640","KW_713","KW_510","KW_583","KW_688","KW_521","KW_566","KW_642","KW_537","KW_801","KW_512","KW_513","KW_528","KW_687","KW_584","KW_586","KW_641","KW_532","KW_610","KW_143","KW_533","KW_709","KW_556","KW_571","KW_647","KW_14","KW_526","KW_711","KW_522","KW_523","KW_585","KW_613","KW_699","KW_589","KW_654","KW_665","KW_678","KW_530","KW_601","KW_677","KW_531","KW_616","KW_524","KW_673","KW_700","KW_737"]}},"startDate":{"type":"string","description":"News published start date. Enter the date in YYYY-MM-DD format.","format":"date"},"endDate":{"type":"string","description":"News published end date. Enter the date in YYYY-MM-DD format.","format":"date"},"limit":{"type":"integer","description":"Maximum number of records to return","default":100}}}}}}
```

## The NewsSearchResponse object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Company News Signals API","version":"1.0"},"components":{"schemas":{"NewsSearchResponse":{"required":["code","count","news"],"type":"object","properties":{"code":{"type":"integer"},"count":{"type":"integer"},"news":{"type":"array","items":{"$ref":"#/components/schemas/NewsItem"}},"openingBalance":{"type":"integer","description":"Returned only for the 'Pay-Per-Use' billing type."},"closingBalance":{"type":"integer","description":"Returned only for the 'Pay-Per-Use' billing type."},"creditsConsumed":{"type":"integer","description":"Returned only for the 'Pay-Per-Use' billing type."}}},"NewsItem":{"type":"object","properties":{"publisher":{"type":"string"},"title":{"type":"string"},"url":{"type":"string","format":"uri"},"desc":{"type":"string"},"hash":{"type":"string"},"triggerNames":{"type":"array","items":{"type":"string"}},"companyNames":{"type":"array","items":{"type":"string"}},"triggerCodes":{"type":"array","items":{"type":"string"}},"companyDomains":{"type":"array","items":{"type":"string"}},"publishDate":{"type":"string","format":"date"},"similarNews":{"type":"array","items":{"$ref":"#/components/schemas/SimilarNewsItem"}}}},"SimilarNewsItem":{"type":"object","properties":{"hash":{"type":"string"},"title":{"type":"string"},"desc":{"type":"string"},"publisher":{"type":"string"},"url":{"type":"string","format":"uri"},"publishDate":{"type":"string","format":"date-time"}}}}}}
```

## The NewsItem object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Company News Signals API","version":"1.0"},"components":{"schemas":{"NewsItem":{"type":"object","properties":{"publisher":{"type":"string"},"title":{"type":"string"},"url":{"type":"string","format":"uri"},"desc":{"type":"string"},"hash":{"type":"string"},"triggerNames":{"type":"array","items":{"type":"string"}},"companyNames":{"type":"array","items":{"type":"string"}},"triggerCodes":{"type":"array","items":{"type":"string"}},"companyDomains":{"type":"array","items":{"type":"string"}},"publishDate":{"type":"string","format":"date"},"similarNews":{"type":"array","items":{"$ref":"#/components/schemas/SimilarNewsItem"}}}},"SimilarNewsItem":{"type":"object","properties":{"hash":{"type":"string"},"title":{"type":"string"},"desc":{"type":"string"},"publisher":{"type":"string"},"url":{"type":"string","format":"uri"},"publishDate":{"type":"string","format":"date-time"}}}}}}
```

## The SimilarNewsItem object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Company News Signals API","version":"1.0"},"components":{"schemas":{"SimilarNewsItem":{"type":"object","properties":{"hash":{"type":"string"},"title":{"type":"string"},"desc":{"type":"string"},"publisher":{"type":"string"},"url":{"type":"string","format":"uri"},"publishDate":{"type":"string","format":"date-time"}}}}}}
```

## The ErrorResponse object

```json
{"openapi":"3.0.3","info":{"title":"Intellizence Company News Signals API","version":"1.0"},"components":{"schemas":{"ErrorResponse":{"required":["code","message"],"type":"object","properties":{"code":{"type":"integer","description":"Business error code (701–799)."},"message":{"type":"string"}}}}}}
```


# Intellizence Company News Signals API Sample Requests

Sample requests for the Intellizence Company News Signals API, including filters for company domains, trigger codes, news published date range, and limit.

## Company News Signals API Sample Requests

Use these sample API requests to retrieve curated company news signals from the Intellizence Company News Signals API.

These examples show common ways to search company news by company domain, trigger code, news published date range, and limit.

{% hint style="info" %}
All request parameters are optional. You can use a single filter or combine multiple filters based on your use case.
{% endhint %}

***

### Endpoint

```http
POST https://connect.intellizence.com/api/news
```

### Authentication

Include your API key in the request header.

```http
x-api-key: YOUR_API_KEY
```

### Content Type

```http
Content-Type: application/json
```

***

## Sample API Requests

### 1. Search Latest News Signals for a Company Domain

Use `companyDomains` to retrieve curated company news signals for a specific company website domain.

This is recommended for CRM enrichment, account monitoring, signal-based selling, workflow automation, and AI agents because domains are usually more precise than company names.

#### Request Body

```json
{
  "companyDomains": [
    "openai.com"
  ],
  "limit": 10
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/news \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyDomains": [
      "openai.com"
    ],
    "limit": 10
  }'
```

***

### 2. Search News Signals for Multiple Company Domains

Use `companyDomains` to search news signals for multiple companies in a single request.

#### Request Body

```json
{
  "companyDomains": [
    "openai.com",
    "anthropic.com",
    "databricks.com"
  ],
  "limit": 25
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/news \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyDomains": [
      "openai.com",
      "anthropic.com",
      "databricks.com"
    ],
    "limit": 25
  }'
```

***

### 3. Search News Signals Within a Date Range

Use `startDate` and `endDate` to retrieve company news signals published during a specific period.

Dates should be provided in `YYYY-MM-DD` format.

#### Request Body

```json
{
  "companyDomains": [
    "openai.com"
  ],
  "startDate": "2026-01-01",
  "endDate": "2026-01-31",
  "limit": 25
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/news \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyDomains": [
      "openai.com"
    ],
    "startDate": "2026-01-01",
    "endDate": "2026-01-31",
    "limit": 25
  }'
```

***

### 4. Search M\&A News Signals

Use `triggerCodes` to filter company news by specific Intellizence signal types.

Use `KW_518` to retrieve Merger & Acquisition signals.

#### Request Body

```json
{
  "companyDomains": [
    "openai.com",
    "anthropic.com"
  ],
  "triggerCodes": [
    "KW_518"
  ],
  "startDate": "2026-01-01",
  "endDate": "2026-01-31",
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/news \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyDomains": [
      "openai.com",
      "anthropic.com"
    ],
    "triggerCodes": [
      "KW_518"
    ],
    "startDate": "2026-01-01",
    "endDate": "2026-01-31",
    "limit": 20
  }'
```

***

### 5. Search Startup Funding and Investment Signals

Use funding and investment trigger codes to retrieve company news related to fundraising and investments.

Common trigger codes:

* `KW_514`: Fundraising
* `KW_708`: Investment

#### Request Body

```json
{
  "companyDomains": [
    "anthropic.com",
    "databricks.com"
  ],
  "triggerCodes": [
    "KW_514",
    "KW_708"
  ],
  "startDate": "2026-01-01",
  "endDate": "2026-01-31",
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/news \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyDomains": [
      "anthropic.com",
      "databricks.com"
    ],
    "triggerCodes": [
      "KW_514",
      "KW_708"
    ],
    "startDate": "2026-01-01",
    "endDate": "2026-01-31",
    "limit": 20
  }'
```

***

### 6. Search Leadership Change Signals

Use leadership and management change trigger codes to retrieve executive change, appointment, and organizational restructuring news.

Common trigger codes:

* `KW_502`: Executive Change
* `KW_591`: Executive Appointment
* `KW_536`: Organizational Restructuring

#### Request Body

```json
{
  "companyDomains": [
    "microsoft.com",
    "salesforce.com"
  ],
  "triggerCodes": [
    "KW_502",
    "KW_591",
    "KW_536"
  ],
  "startDate": "2026-01-01",
  "endDate": "2026-01-31",
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/news \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyDomains": [
      "microsoft.com",
      "salesforce.com"
    ],
    "triggerCodes": [
      "KW_502",
      "KW_591",
      "KW_536"
    ],
    "startDate": "2026-01-01",
    "endDate": "2026-01-31",
    "limit": 20
  }'
```

***

### 7. Search Business Expansion and Hiring Signals

Use business expansion and hiring trigger codes to retrieve signals related to company growth, new locations, hiring, and relocation.

Common trigger codes:

* `KW_527`: Business Expansion
* `KW_529`: Hiring
* `KW_640`: Branch/Store Opening
* `KW_713`: Relocation

#### Request Body

```json
{
  "companyDomains": [
    "amazon.com",
    "tesla.com"
  ],
  "triggerCodes": [
    "KW_527",
    "KW_529",
    "KW_640",
    "KW_713"
  ],
  "startDate": "2026-01-01",
  "endDate": "2026-01-31",
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/news \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyDomains": [
      "amazon.com",
      "tesla.com"
    ],
    "triggerCodes": [
      "KW_527",
      "KW_529",
      "KW_640",
      "KW_713"
    ],
    "startDate": "2026-01-01",
    "endDate": "2026-01-31",
    "limit": 20
  }'
```

***

### 8. Search Layoff, Cost-Cutting, and Restructuring Signals

Use layoff and cost-cutting trigger codes to retrieve workforce reduction, downsizing, restructuring, and cost reduction signals.

Common trigger codes:

* `KW_528`: Downsizing / Layoff
* `KW_687`: Cost-Cutting
* `KW_536`: Organizational Restructuring

#### Request Body

```json
{
  "companyDomains": [
    "intel.com",
    "cisco.com"
  ],
  "triggerCodes": [
    "KW_528",
    "KW_687",
    "KW_536"
  ],
  "startDate": "2026-01-01",
  "endDate": "2026-01-31",
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/news \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyDomains": [
      "intel.com",
      "cisco.com"
    ],
    "triggerCodes": [
      "KW_528",
      "KW_687",
      "KW_536"
    ],
    "startDate": "2026-01-01",
    "endDate": "2026-01-31",
    "limit": 20
  }'
```

***

### 9. Search Product Launch Signals

Use product and service launch trigger codes to retrieve company news related to new products, services, platforms, features, and commercial launches.

Common trigger codes:

* `KW_521`: Product Launch
* `KW_566`: Service Launch
* `KW_642`: Platform Launch

#### Request Body

```json
{
  "companyDomains": [
    "hubspot.com",
    "shopify.com",
    "stripe.com"
  ],
  "triggerCodes": [
    "KW_521",
    "KW_566",
    "KW_642"
  ],
  "startDate": "2026-01-01",
  "endDate": "2026-01-31",
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/news \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyDomains": [
      "hubspot.com",
      "shopify.com",
      "stripe.com"
    ],
    "triggerCodes": [
      "KW_521",
      "KW_566",
      "KW_642"
    ],
    "startDate": "2026-01-01",
    "endDate": "2026-01-31",
    "limit": 20
  }'
```

***

### 10. Search Adverse and Negative News Signals

Use adverse and negative news trigger codes to monitor company risk signals such as layoffs, cost-cutting, bankruptcy, business shutdowns, restructuring, and financial distress.

Common trigger codes:

* `KW_528`: Downsizing / Layoff
* `KW_687`: Cost-Cutting
* `KW_536`: Organizational Restructuring
* `KW_584`: Bankruptcy
* `KW_586`: Business Shutdown
* `KW_641`: Financial Distress

#### Request Body

```json
{
  "companyDomains": [
    "salesforce.com",
    "workday.com",
    "servicenow.com"
  ],
  "triggerCodes": [
    "KW_528",
    "KW_687",
    "KW_536",
    "KW_584",
    "KW_586",
    "KW_641"
  ],
  "startDate": "2026-01-01",
  "endDate": "2026-01-31",
  "limit": 50
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/news \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyDomains": [
      "salesforce.com",
      "workday.com",
      "servicenow.com"
    ],
    "triggerCodes": [
      "KW_528",
      "KW_687",
      "KW_536",
      "KW_584",
      "KW_586",
      "KW_641"
    ],
    "startDate": "2026-01-01",
    "endDate": "2026-01-31",
    "limit": 50
  }'
```

***

## Use Case Examples

### 1. Daily Company News Monitoring

Use this example when you want to pull recent company news signals into your application, CRM, dashboard, or AI workflow.

#### Recommended Filters

```json
{
  "companyDomains": [
    "openai.com",
    "anthropic.com",
    "databricks.com"
  ],
  "startDate": "2026-01-01",
  "endDate": "2026-01-31",
  "limit": 100
}
```

#### Best For

* Daily company monitoring
* CRM enrichment
* Account intelligence
* Internal dashboards
* AI agent workflows

***

### 2. Sales and Prospecting Signals

Use this example to identify sales-relevant company events such as funding, M\&A, leadership changes, expansion, hiring, partnerships, and product launches.

#### Recommended Filters

```json
{
  "companyDomains": [
    "openai.com",
    "anthropic.com",
    "databricks.com"
  ],
  "triggerCodes": [
    "KW_514",
    "KW_708",
    "KW_518",
    "KW_502",
    "KW_591",
    "KW_527",
    "KW_529",
    "KW_512",
    "KW_513",
    "KW_521"
  ],
  "startDate": "2026-01-01",
  "endDate": "2026-01-31",
  "limit": 100
}
```

#### Best For

* Prospecting
* Signal-based selling
* Account prioritization
* Trigger-based outreach
* Sales and marketing campaigns

***

### 3. Customer / Account Intelligence: Growth and Risk Signals

Use this example to monitor both growth and risk signals across customers, target accounts, partners, competitors, or watchlists. Growth signals may indicate expansion, upsell, cross-sell, or competitive movement, while risk signals may indicate churn, downsell, renewal risk, or business uncertainty.

#### Recommended Filters

```json
{
  "companyDomains": [
    "hubspot.com",
    "shopify.com",
    "stripe.com"
  ],
  "triggerCodes": [
    "KW_514",
    "KW_708",
    "KW_527",
    "KW_529",
    "KW_521",
    "KW_512",
    "KW_502",
    "KW_528",
    "KW_687",
    "KW_536",
    "KW_584",
    "KW_586",
    "KW_641"
  ],
  "startDate": "2026-01-01",
  "endDate": "2026-01-31",
  "limit": 100
}
```

#### Best For

* Customer intelligence
* Account monitoring
* Expansion and upsell signals
* Renewal and churn risk monitoring
* Watchlist intelligence

***

### 4. Risk and Adverse News Monitoring

Use this example to monitor adverse company events such as layoffs, cost-cutting, restructuring, bankruptcy, financial distress, and business shutdowns.

#### Recommended Filters

```json
{
  "companyDomains": [
    "salesforce.com",
    "workday.com",
    "servicenow.com"
  ],
  "triggerCodes": [
    "KW_528",
    "KW_687",
    "KW_536",
    "KW_584",
    "KW_586",
    "KW_641"
  ],
  "startDate": "2026-01-01",
  "endDate": "2026-01-31",
  "limit": 100
}
```

#### Best For

* Risk monitoring
* Customer risk detection
* Vendor risk monitoring
* Churn and downsell risk workflows
* Financial distress and restructuring tracking

***

### 5. Investment and Market Research

Use this example to monitor investment-relevant company events such as M\&A, fundraising, IPOs, financial results, business outlook, business expansion, layoffs, and restructuring.

#### Recommended Filters

```json
{
  "companyDomains": [
    "tesla.com",
    "nvidia.com",
    "microsoft.com"
  ],
  "triggerCodes": [
    "KW_518",
    "KW_514",
    "KW_516",
    "KW_510",
    "KW_688",
    "KW_527",
    "KW_528",
    "KW_536"
  ],
  "startDate": "2026-01-01",
  "endDate": "2026-01-31",
  "limit": 100
}
```

#### Best For

* Investment research
* Market intelligence
* Competitive intelligence
* Portfolio monitoring
* Event-driven research

***

## Recommended Use Cases

| Use Case                         | Recommended Filters                                              |
| -------------------------------- | ---------------------------------------------------------------- |
| Daily company news monitoring    | `companyDomains`, `startDate`, `endDate`, `limit`                |
| Sales and prospecting signals    | `companyDomains`, sales-relevant `triggerCodes`, date range      |
| Customer / account intelligence  | `companyDomains`, growth and risk `triggerCodes`, date range     |
| Risk and adverse news monitoring | `companyDomains`, adverse / negative `triggerCodes`, date range  |
| Investment and market research   | `companyDomains`, investment-relevant `triggerCodes`, date range |

***

## Best Practices

### Prefer company domains for company matching

Use `companyDomains` to retrieve news signals for specific companies.

Company domains are usually more precise than company names and help reduce duplicate or ambiguous matches.

```json
{
  "companyDomains": [
    "openai.com"
  ],
  "limit": 10
}
```

### Use multiple company domains for account monitoring

You can pass multiple company domains in a single request.

```json
{
  "companyDomains": [
    "openai.com",
    "anthropic.com",
    "databricks.com"
  ],
  "limit": 25
}
```

### Use trigger codes to filter by signal type

Use `triggerCodes` to retrieve specific types of company events such as M\&A, fundraising, layoffs, business expansion, executive changes, partnerships, and product launches.

```json
{
  "triggerCodes": [
    "KW_518",
    "KW_514",
    "KW_528"
  ],
  "limit": 25
}
```

### Use date ranges for published news search

Use `startDate` and `endDate` to search news published during a specific period.

```json
{
  "startDate": "2026-01-01",
  "endDate": "2026-01-31",
  "limit": 25
}
```

### Use limit to control result size

The default limit is `100` records if no limit is provided.

```json
{
  "limit": 100
}
```

### Combine company domains, trigger codes, and dates

For more precise results, combine company domains, trigger codes, published date range, and limit.

```json
{
  "companyDomains": [
    "openai.com",
    "anthropic.com"
  ],
  "triggerCodes": [
    "KW_518",
    "KW_514"
  ],
  "startDate": "2026-01-01",
  "endDate": "2026-01-31",
  "limit": 50
}
```

***

## Common Trigger Codes

| Signal Category                 | Trigger Codes                                              |
| ------------------------------- | ---------------------------------------------------------- |
| Mergers & Acquisitions          | `KW_518`, `KW_519`, `KW_520`, `KW_534`, `KW_535`, `KW_666` |
| Fundraising & Investment        | `KW_514`, `KW_708`                                         |
| IPO                             | `KW_516`                                                   |
| Leadership / Management Changes | `KW_502`, `KW_536`, `KW_591`, `KW_741`                     |
| Business Expansion & Hiring     | `KW_527`, `KW_529`, `KW_640`, `KW_713`                     |
| Product & Service Launch        | `KW_521`, `KW_566`, `KW_642`                               |
| Partnerships & Joint Ventures   | `KW_512`, `KW_513`                                         |
| Layoffs & Cost-Cutting          | `KW_528`, `KW_687`                                         |
| Bankruptcy & Business Shutdown  | `KW_584`, `KW_586`, `KW_641`                               |

{% hint style="info" %}
For the full list of available trigger codes, see the Intellizence Trigger Codes Reference page.
{% endhint %}

***

## Notes

* All parameters are optional.
* Dates should be provided in `YYYY-MM-DD` format.
* Use `companyDomains` to search news signals for one or more companies.
* Use `triggerCodes` to filter news signals by company event type.
* Use `startDate` and `endDate` to filter by news published date.
* Use `limit` to control the number of records returned.
* A news record may include clustered or related articles under `similarNews`.
* Credit fields such as `openingBalance`, `closingBalance`, and `creditsConsumed` may be returned for Pay-Per-Use billing.


# Intellizence Signals (Trigger Codes) Reference

## Signals (Trigger Codes) Reference

This page provides a categorized list of all **Intellizence Signals (Trigger Codes)** used to filter curated news signals about company events. Use these codes in the `triggerCodes` parameter of the API request.

***

### 🧩 Mergers & Acquisitions

* `KW_518`: Merger & Acquisition
* `KW_519`: Divestment
* `KW_520`: Spin-off
* `KW_534`: Going Private
* `KW_535`: Buyout
* `KW_666`: Merger & Acquisition Termination\
  \
  **Trigger** **Codes:** “KW\_518”, “KW\_519”, “KW\_520”, “KW\_534”, “KW\_535”, “KW\_666”

### 👥 Leadership/Management Changes

* `KW_502`: Executive Change
* `KW_536`: Organizational Restructuring
* `KW_591`: Executive Appointment
* `KW_741`: Executive Demise

**Trigger** **Codes:** "KW\_502", "KW\_536", "KW\_591", "KW\_741"

***

### 💰 Fundraising & Investment

* `KW_514`: Fundraising
* `KW_708`: Investment

**Trigger** **Codes:** "KW\_514", "KW\_708"

***

### 🏛️ Initial Public Offering (IPO)

* `KW_516`: Initial Public Offering

**Trigger** **Codes:** "KW\_516"

### 🌍 Business Expansion

* `KW_527`: Business Expansion
* `KW_529`: Hiring
* `KW_640`: Branch/Store Opening
* `KW_713`: Relocation

**Trigger** **Codes:** "KW\_527", "KW\_640", "KW\_713", "KW\_529"

***

### 📊 Financial Results & Outlook

* `KW_510`: Financial Result
* `KW_583`: Executive Statement
* `KW_688`: Business Outlook & Projections

**Trigger** **Codes:** "KW\_510", "KW\_583", "KW\_688"

***

### 🚀 Product & Service Launch

* `KW_521`: New Product Launch
* `KW_566`: New Service Launch
* `KW_642`: Product Shutdown

**Trigger** **Codes:** “KW\_521”, “KW\_566”, “KW\_642”

***

### 🔬 Innovation & Initiatives

* `KW_801`: New Initiatives and Programs
* `KW_802`: Experiments / Trials / Pilots

**Trigger** **Codes:** "KW\_801", "KW\_802"

***

### 🤝 Partnerships & Joint Ventures

* `KW_512`: Alliance & Partnership
* `KW_513`: Joint Venture

**Trigger** **Codes:** "KW\_512", "KW\_513"

***

### 📉 Layoffs & Cost-Cutting

* `KW_528`: Downsizing (Layoff)
* `KW_687`: Cost-Cutting

**Trigger** **Codes:** “KW\_528”, “KW\_687”

***

### ⚖️ Bankruptcy & Business Shut-down

* `KW_584`: Bankruptcy
* `KW_586`: Business Shut-down
* `KW_641`: Branch/Store Closing

**Trigger** **Codes:** "KW\_584", "KW\_586", "KW\_641"

***

### 🏅 Awards & Recognition

* `KW_532`: Awards & Recognition
* `KW_610`: Certification

**Trigger** **Codes:** "KW\_532", "KW\_610"

***

### 📢 Advertising & Marketing

* `KW_143`: Advertisement / Branding / Campaign
* `KW_533`: Promotion & Sale
* `KW_709`: Re-branding / Re-naming

**Trigger** **Codes:** "KW\_143", "KW\_533", "KW\_709".

***

### 🧲 Customer Acquisition / Sourcing

* `KW_556`: Customer Acquisition / Growth
* `KW_571`: Sourcing & Procurement

**Trigger** **Codes:** "KW\_556", "KW\_571".

***

### 👎 Customer Churn

* `KW_647`: Customer Loss / Growth Decline

**Trigger** **Codes:** "KW\_647".

***

### 💲 Pricing

* `KW_14`: Pricing

**Trigger** **Codes:** "KW\_14".

***

### ⚖️ Legal

* `KW_526`: Lawsuit / Judgment / Settlement
* `KW_711`: Copyright / Patent / Trademark Dispute

**Trigger** **Codes:** "KW\_526", "KW\_711".

***

### 🏛️ Regulatory

* `KW_522`: Regulatory Approval
* `KW_523`: Regulatory Investigation
* `KW_585`: Legislation & Regulation
* `KW_613`: Regulatory Ban & Enforcement
* `KW_699`: Regulatory Settlement

**Trigger** **Codes:** "KW\_522", "KW\_523", "KW\_585", "KW\_613", "KW\_699"

***

#### 🌱 ESG Initiatives

* `KW_146`: Employee Benefit
* `KW_702`: Sustainability Initiatives
* `KW_592`: Donation & Sponsorship

**Trigger Codes:** "KW\_146", "KW\_702", "KW\_592"

***

### 📚 Research & Publications

* `KW_589`: Research & Publications

**Trigger** **Codes:** "KW\_589".

***

### 🕵️ Scandals, Rumours, Activism

* `KW_654`: Scandals & Frauds
* `KW_665`: Rumour & Speculation
* `KW_678`: Shareholder Activism

**Trigger** **Codes:** "KW\_654", "KW\_665", "KW\_678".

***

### 🔐 Security Breaches & Outages

* `KW_530`: Security Breach & Vulnerability
* `KW_601`: Outage

**Trigger** **Codes:** "KW\_530", "KW\_601"

***

### 🧑‍🏭 Employee/Labor Dispute

* `KW_677`: Employee Dispute & Strike

**Trigger** **Codes:** "KW\_677"

***

### 🌪️ Accidents & Disasters

* `KW_531`: Natural Disaster
* `KW_616`: Industrial Accident & Disaster

**Trigger** **Codes:** "KW\_531", "KW\_616".

***

### ⚠️ Recalls & Disruptions

* `KW_524`: Recall
* `KW_673`: Project & Operations Status
* `KW_700`: Production Cut
* `KW_737`: Supply Chain Disruption

**Trigger** **Codes:** "KW\_524", "KW\_673", "KW\_700", "KW\_737"


# Intellizence MCP Connector

Connect AI assistants and agents to Intellizence company signals using MCP.

\
The **Intellizence MCP Connector** allows AI assistants such as ChatGPT and Claude to access Intellizence company signals through Model Context Protocol (MCP). With the connector, users can search and retrieve business events such as mergers and acquisitions, startup funding, layoffs, executive changes, business expansions, cyber incidents, bankruptcies, IPOs, and other company signals directly from their AI workspace.

Instead of manually searching datasets or writing API queries, users can ask questions such as:

* What are the top M\&A deals announced this week?
* OpenAI Funding rounds
* Which tech companies announced layoffs recently?
* What are the latest CEO changes in retail companies?
* Latest product launches by Anthropic

### What is MCP?

MCP, or Model Context Protocol, is a standard that allows AI assistants to connect with external tools, systems, and data sources.

The Intellizence MCP Connector uses MCP to make Intellizence company signals available inside supported AI assistants.

### What You Can Do

Using the Intellizence MCP Connector, you can:

* Search company news signals by company name or domain
* Find M\&A deals by acquirer, target, date range, deal value, status, or deal type
* Search  funding deals by startup, funding round, investor, valuation, or amount
* Track layoffs and downsizing announcements
* Find business expansion and investment announcements
* Search CEO changes and executive appointments
* Monitor cybersecurity incidents and data breaches
* Retrieve full details of a specific company signal

### Supported Platforms

The Intellizence MCP Connector can be used with supported MCP-compatible AI assistants, including:

* Claude
* ChatGPT and Other MCP-compatible clients (Available soon)

Setup steps may vary depending on the platform.

### Common Use Cases

#### Account Intelligence

Sales, GTM, and customer-facing teams can use the connector to identify recent company signals for target accounts, customers, or prospects.

Example:

```
Find recent growth signals for salesforce.com from the last 90 days.
```

#### Deal Sourcing

Investment, private equity, corporate development, and consulting teams can use the connector to identify companies raising funding, acquiring companies, expanding operations, or showing strategic activity.

Example:

```
Find AI companies that raised funding in Q2 2026.
```

#### Market Intelligence

Research and strategy teams can use the connector to analyze company activity by sector, geography, date range, or signal category.

Example:

```
Get the top M&A deals announced in the healthcare sector this month.
```

#### Risk Monitoring

Risk, compliance, vendor management, and security teams can use the connector to track layoffs, bankruptcies, cyber incidents, restructuring events, and other risk signals.

Example:

```
Show recent cyber incidents involving healthcare companies.
```

### Supported Signal Categories

Access to signal categories depends on your Intellizence subscription.

Supported company signals may include:

* Mergers & Acquisitions
* Startup Funding
* Business Expansion
* Layoffs & Downsizing
* C-Suite Changes (Appointments, Promotion, Retirement, Termination, etc)
* Cyber Incidents & Data Breaches
* Bankruptcy & Restructuring
* IPO
* Partnerships
* Product Launches
* Divestments
* Regulatory Updates
* Other Company News Signals

### How It Works

* The user asks a question in a supported AI assistant.
* The AI assistant uses the Intellizence MCP Connector to call the relevant Intellizence tool.
* The connector searches Intellizence company signals based on the user’s request.
* The AI assistant returns the results in a readable format, such as a summary, list, or table.

### Next Steps

To start using the Intellizence MCP Connector:

1. Review the Prerequisites
2. Complete the Setup
3. Configure Authentication
4. Test the connector using Example Prompts


# Setup

Make sure you have the following before setting up the Intellizence MCP Connector.

### **Intellizence Access**

* **An active Intellizence account.** If you don't have an account yet, start your free trial.&#x20;
* **Login credentials** associated with your Intellizence account.<br>

{% hint style="info" %}
**Data Access & Subscription:** \
Data available through the MCP Connector is governed by your existing Intellizence subscription. Your access to datasets, records, and historical data will match the entitlements included in your Intellizence Trial, Essential, or Business plan. The Intellizence MCP Connector does not provide access beyond your current subscription.
{% endhint %}

### Supported AI Platforms

You need access to an AI assistant or workspace that supports MCP connectors.

Intellizence MCP Connector can be used with supported platforms such as:

* Claude
* ChatGPT or other MCP-compatible clients

The setup steps may vary by platform.

If you are using a team or enterprise workspace, your workspace admin may need to approve or enable custom MCP connectors.

This may apply to platforms such as ChatGPT Team, ChatGPT Enterprise, Claude Team, or Claude Enterprise.

Once these are ready, continue with the setup for your preferred platform.

### Claude Setup

Follow the steps below to connect the Intellizence MCP Connector to Claude.

#### **Step 1: Add a Custom Connector**

* In Claude, go to Settings → Customize → **Connectors**.
* Click **Add** in the top-right corner.
* Select **Add custom connector**.<br>

#### **Step 2: Enter the Connector Details**

On the '**Add custom connector**' screen, enter the following:

* **Name:** Intellizence
* **Remote MCP Server URL:** <https://mcp.intellizence.com/mcp>
* Under **Advance Settings** enter:
  * **OAuth Client ID:** V7Wy7WpQTcKJM06ptHjIH6wIE3jtlKic&#x20;
  * **OAuth Client Secret:** Leave this field blank
* Click '**Add**'<br>

<figure><img src="https://1902192103-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fyxb48oRcQIrFh2QDo88x%2Fuploads%2FuECjUKzDcsFFBEZ0wKx3%2FScreenshot%202026-08-13%20at%201.21.29%E2%80%AFPM.png?alt=media&amp;token=05bf3d91-0950-47ab-abcf-8fe58d3b17f6" alt="" width="375"><figcaption></figcaption></figure>

* **Step 3: Connect and Authorize**
  * Click **Connect**

<figure><img src="https://1902192103-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fyxb48oRcQIrFh2QDo88x%2Fuploads%2FyJwZy2EPPOSHQ4h4OBdo%2FScreenshot%202026-08-13%20at%201.22.56%E2%80%AFPM.png?alt=media&amp;token=130151d4-6b18-422a-9f60-e1413d66c55b" alt="" width="375"><figcaption></figcaption></figure>

* Sign in using the **login credentials associated with your Intellizence account**.

<figure><img src="https://1902192103-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fyxb48oRcQIrFh2QDo88x%2Fuploads%2FS4X8xf200POSxr7JjdRT%2FScreenshot%202026-08-13%20at%202.15.16%E2%80%AFPM.png?alt=media&amp;token=f476f281-255f-4016-ac03-afb86cd89b21" alt="" width="375"><figcaption></figcaption></figure>

* Authorize **Intellizence App** by clicking **Accept**<br>

<figure><img src="https://1902192103-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fyxb48oRcQIrFh2QDo88x%2Fuploads%2FdykpXcnkOrDOFvWEFSvi%2FScreenshot%202026-08-13%20at%202.41.41%E2%80%AFPM.png?alt=media&amp;token=ecb63064-7622-4e02-98e2-4a0d37b3399e" alt="" width="375"><figcaption></figcaption></figure>

* Once the connection is successful, the available Intellizence tools will appear in Claude.

<figure><img src="https://1902192103-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fyxb48oRcQIrFh2QDo88x%2Fuploads%2FdpGuKa5o5nTNNu507JBW%2FScreenshot%202026-08-13%20at%201.23.48%E2%80%AFPM.png?alt=media&amp;token=3d5026da-2c78-49aa-b50b-89b23e31c796" alt="" width="375"><figcaption></figcaption></figure>

Under Tool Permissions, you may choose Always Allow if you want Claude to use the Intellizence tools without requesting permission each time.

### ChatGPT Setup

Coming soon...

{% hint style="info" %}
**Do you need any assistance or help?** \
**Please send a mail to <support@intellizence.com> with screenshots**
{% endhint %}


# Tools

## Intellizence MCP Tools

The Intellizence MCP Server exposes **14 tools** — 7 search tools that return structured or narrative results, and 7 companion "get by ID" tools that pull the full detail record for a single result. Connect the server once, and Claude (or any MCP-compatible AI assistant) can query live company signals directly inside your conversation.

***

### Search Tools

#### `search_news`

Real-time, narrative news articles on companies across 30 growth, sales, and risk signal themes (M\&A, Fundraising, Layoffs, Leadership Changes, Product Launches, Bankruptcy, Legal, Regulatory, Security Breaches, and more). \
**Filters:** companies, themes, industries, stock markets, company type (Public/Private), locations, date range, limit. \
**Best for:** open-ended "what's happening with X" queries and unstructured context — not deduplicated deal records.

#### `search_funding_data`

Structured, deduplicated funding and investment event records — one record per deal. **Includes:** company, funding round (Angel through Series J, PE, Debt, Grant), deal amount, currency, date. **Filters:** company domain/name/ticker, industry, location, company type, funding round, deal amount (operators incl. between), currency, date range, limit. \
**Best for:** identifying recently funded companies, qualifying prospects by stage, tracking investment trends.

#### `search_mergers_acquisitions_data`

Structured, deduplicated M\&A deal records — one record per deal, with independent filtering across all three company roles: acquiring, acquired, and selling. **Includes:** deal type, deal status (Announced, Completed, Terminated, Rumours & Speculation, and more), deal amount, currency, date. \
**Filters:** company domain/name/ticker/industry/location per role, deal amount, M\&A status, M\&A type, currency, date range, limit. \
**Best for:** detecting acquisition activity, monitoring customers for M\&A events, identifying divestments.

#### `search_layoffs_data`

Structured, deduplicated workforce reduction event records — one record per event. **Includes:** company, layoff type, layoff reason (Restructuring, Cost-cutting, M\&A, AI Automation, Financial Distress, and more), location, date. \
**Filters:** company domain/name/ticker/industry/location/type, layoff reason, layoff type, date range, limit. \
**Best for:** organizational stress signals, budget-freeze risk, churn indicators, sector-wide trend tracking.

#### `search_expansion_data`

Structured, deduplicated business expansion event records — one record per event. **Includes:** company, expansion type (Office, Factory, Data Centre, HQ, Country Expansion, Research Lab, and more), expansion location, investment amount, jobs created, date. \
**Filters:** company domain/name/ticker/industry/location/type, expansion type, investment amount, jobs created, currency, date range, limit. \
**Best for:** identifying companies growing footprint, entering new markets, or making large capital investments.

#### `search_executive_changes_data`

Structured, deduplicated leadership transition records — one record per event. **Includes:** executive name, title, title category (CEO, CFO, CTO, CRO, CMO, CISO, Board, and more), company, change reason (New Appointment, Resigned, Retired, Terminated, and more), date. \
**Filters:** company domain/name/ticker/industry/location/type, executive name/title/title category, change reason, date range, limit. \
**Best for:** spotting leadership transitions that trigger new buying cycles, strategy shifts, budget reviews, or churn risk.

#### `search_security_breaches_data`

Structured, deduplicated security incident records — one record per event. **Includes:** company, incident type (Ransomware, Malware, Hack, Data Breach/Leak, DDoS, and more), people impacted, location, date. \
**Filters:** company domain/name/ticker/industry/location/type, incident type, people impacted (operators incl. between), date range, limit. \
**Best for:** cybersecurity risk exposure, breach-triggered buying signals for security/compliance vendors, portfolio incident monitoring.

***

### Detail Lookup Tools

Each search tool has a matching "get by ID" tool to fetch the full record for a specific result:

| Tool                           | Companion to                       |
| ------------------------------ | ---------------------------------- |
| `get_news_by_id`               | `search_news`                      |
| `get_fundraising_by_id`        | `search_funding_data`              |
| `get_merger_acquisition_by_id` | `search_mergers_acquisitions_data` |
| `get_layoff_by_id`             | `search_layoffs_data`              |
| `get_business_expansion_by_id` | `search_expansion_data`            |
| `get_executive_change_by_id`   | `search_executive_changes_data`    |
| `get_data_breach_by_id`        | `search_security_breaches_data`    |

***

### Coverage Notes

* **Geography:** North America → Europe → Asia Pacific → Middle East → Africa → Latin America
* **Language:** English-language sources only
* **Latency:** typically 1–2 business days from event to record availability
* **Currency:** monetary fields are returned in their originally reported currency unless you request FX conversion


# Example Prompts

## Sample Queries — Intellizence MCP Tools

Example prompts you can type directly in Claude once the Intellizence MCP Server is connected. Claude automatically routes each prompt to the right tool and filters.

***

#### `search_news`

* "What's the latest news on Stripe?"
* "Show me recent Security Breaches & Outages news"
* "Any Leadership & Management Changes news this week?"

#### `search_funding_data`

* "Which companies raised a Series B or later in the last 7 days?"
* "Show me funding rounds over $10M this week."
* "Has \[companyDomain] raised any funding recently?"

#### `search_mergers_acquisitions_data`

* "What acquisitions has Salesforce announced in the past year?"
* "Show me completed M\&A deals over $500M in the healthcare industry."
* "List recent terminated M\&A deals "

#### `search_layoffs_data`

* "Which tech companies announced layoffs in the last 30 days?"
* "Any layoffs at \[companyDomain] recently?"
* "List companies that cut more than 500 jobs."

#### `search_expansion_data`

* "Which companies are opening new data centers this quarter?"
* "Show me business expansions with investment over $50M in California."
* "List companies opening HQs in the last 6 months."

#### `search_executive_changes_data`

* "Who are the new CFOs appointed in the retail industry this month?"
* "Has \[companyDomain] had any C-suite departures recently?"
* "List executive resignations across the tech industry in the last 30 days."

#### `search_security_breaches_data`

* "Show me data breaches impacting over 10,000 people this month."
* "Has \[companyDomain] disclosed any security incidents recently?"
* "List security breaches in the healthcare industry in the US."

***

### Detail Lookup Examples

* "Give me the full details on that second funding deal." *(uses `get_fundraising_by_id`)*
* "Pull up the complete record for that M\&A deal you mentioned." *(uses `get_merger_acquisition_by_id`)*
* "Show me everything on that breach at \[company]." *(uses `get_data_breach_by_id`)*

These run automatically after a search — just ask Claude to expand on a specific result and it will call the matching detail tool.<br>

{% hint style="info" %}
The more specific your prompt is, the easier it is for the AI assistant to select the appropriate Intellizence tools and return relevant results.
{% endhint %}

<br>

***


# Add Group

Add a group

`POST /api/v1/group/{GROUP_NAME} HTTP/1.1`&#x20;

Replace GROUP\_NAME with the group name that you would like to add

### **Response body**

```
{
            "status": "status_code",
            "message": "status_message"
}                     
```

| Status code | Description               |
| ----------- | ------------------------- |
| 200         | Group added               |
| 201         | Group Name already exists |


# Add Company

Add a Company to track

`POST /api/v1/company/{GROUP_NAME}/{COMPANY_ID} HTTP/1.1`

Replace COMPANY\_ID with the Intellizence Company Id that you would like to add and GROUP\_NAME with the Group Name

**Response body**

```
{
            "status": "status_code",
            "message": "status_message"
}         
```

| Status code | Description                                            |
| ----------- | ------------------------------------------------------ |
| 200         | Company added                                          |
| 201         | Post a valid Company Id                                |
| 202         | Company Id does not exist in the Intellizence database |
| 203         | Company already been tracked                           |
| 404         | Group Name does not exist                              |

<br>


# List Companies

Returns a list of matching companies from the Intellizence database

`GET /api/v1/companies HTTP/1.1`

### Parameters

| Param  | Mandatory | Description                                                    |
| ------ | --------- | -------------------------------------------------------------- |
| name   | N         | Partial name of the Company, minimum 3 chars required.         |
| domain | N         | Partial Domain Name without http(s), minimum 6 chars required. |

Note : You have to pass either Company Name or Domain Name.

### Response Body

```
{
    "status":"status_code",
    "message":"status_message",
    "companies": [
        {
            "id": "intellizence_company_id_1",
            "name": "company_name_1",
            "domain": "company_domain_1"
        },
        {
            "id": "intellizence_company_id_2",
            "name": "company_name_2",
            "domain": "company_domain_2"
        }
    ]
}
```

| Status code | Description                                                             |
| ----------- | ----------------------------------------------------------------------- |
| 200         | Success                                                                 |
| 201         | Input minimum 3 chars of Company Name or minimum 6 chars of Domain Name |
| 202         | Minimum 3 chars of Company Name required                                |
| 203         | Minimum 6 chars of Domain Name required                                 |

<br>


# Bulk Add Companies

Add companies to track

`POST /api/v1/company/{GROUP_NAME} HTTP/1.1`

Replace GROUP\_NAME with the Group Name under which the companies have to be added

**Request body**

```
{
            "companyIds": ["company_id"]
}
```

| Param        | Mandatory | Description                                                                                                                                                     |
| ------------ | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| company\_ids | Y         | <p>Array of Intellizence Company Ids that you would like to add.<br><br>If the GROUP\_NAME does not exist, it would be created and companies will be added.</p> |

**Response body**

```
{
            "status": status,
            "addedCompanyIds": ["company_id"]
}                               
```

| Param           | Description                                                                                     |
| --------------- | ----------------------------------------------------------------------------------------------- |
| addedCompanyIds | Array of Company Ids which are added                                                            |
| status          | <p>status codes - </p><p>200 - Success<br>201 - You are adding more companies than allowed </p> |


# List Triggers

Returns list of all available triggers in the Intellizence database

`GET /api/v1/triggers HTTP/1.1`

**Response body**

```
{
    "triggers": [
        {
            "code": "trigger_code_1",
            "name": "trigger_name_1"
        },
        {
            "code": "trigger_code_2",
            "name": "trigger_name_2"
        }
    ]
}
```

<br>


# Add Trigger

Add a Trigger to track

`POST /api/v1/trigger/{GROUP_NAME}/{TRIGGER_CODE} HTTP/1.1`

Replace TRIGGER\_CODE with the Intellizence Trigger Code that you would like to add and GROUP\_NAME with the Group Name

**Response body**

```
{
            "status": "status_code"
}
```

| Status code | Description                                               |
| ----------- | --------------------------------------------------------- |
| 200         | Trigger added                                             |
| 201         | Limit reached. You will not be able to add more triggers. |
| 202         | Trigger Code does not exist in the Intellizence database  |
| 404         | Group Name does not exist                                 |


# Bulk Add Triggers

Add Triggers to track

`POST /api/v1/trigger/{GROUP_NAME} HTTP/1.1`

Replace GROUP\_NAME with the Group Name under which the triggers have to be added

**Request body**

```
{
            "triggerCodes": ["trigger_code"]
}
```

| Param         | Mandatory | Description                                                    |
| ------------- | --------- | -------------------------------------------------------------- |
| trigger\_code | Y         | Array of Intellizence Trigger Codes that you would like to add |

**Response body**

```
{
            "nonExistingTriggerCodes": ["trigger_code"],
            "alreadyTrackedTriggerCodes": ["trigger_code"],
            "addedTriggerCodes": ["trigger_code"]
}
```

<br>


# List of Tracked Triggers

Returns a list of all tracked triggers for the given API key

`GET /api/v1/tracked-triggers/{GROUP_NAME} HTTP/1.1`

Replace GROUP\_NAME with the Group Name

**Response body**

```
{
    "status":"status_code",
    "message":"status_message",
    "triggers": [
        {
            "id": "trigger_code_1",
            "name": "trigger_name_1"
        },
        {
            "id": "trigger_code_2",
            "name": "trigger_name_2"
        }
    ]
}
```

| Status code | Description               |
| ----------- | ------------------------- |
| 200         | Success                   |
| 404         | Group Name does not exist |

<br>


# Remove Company

Remove a Company from tracking

`DELETE /api/v1/company/{GROUP_NAME}/{COMPANY_ID} HTTP/1.1`

Replace COMPANY\_ID with the Intellizence Company Id that you would like to remove and GROUP\_NAME with the Group Name

**Response body**

```
{
            "status": "status_code",
            "message": "status_message"
}                              
```

| Status code | Description               |
| ----------- | ------------------------- |
| 200         | Company removed           |
| 201         | Post a valid Company Id   |
| 202         | Company not been tracked  |
| 404         | Group Name does not exist |

<br>


# Bulk Remove Companies

Remove companies from tracking

`DELETE /api/v1/company/{GROUP_NAME} HTTP/1.1`

Replace GROUP\_NAME with the Group Name under which the companies have to be removed

**Request body**

```
{
            "companyIds": ["company_id"]
}
```

| Param       | Mandatory | Description                                                     |
| ----------- | --------- | --------------------------------------------------------------- |
| company\_id | Y         | Array of Intellizence Company Ids that you would like to remove |

**Response body**

```
{
            "nonExistingCompanyIds": ["company_id"],
            "nonTrackedCompanyIds": ["company_id"],
            "removedCompanyIds": ["company_id"]
}                                       
```

| Param                 | Description                                                              |
| --------------------- | ------------------------------------------------------------------------ |
| nonExistingCompanyIds | Array of Company Ids which are not existing in the Intellizence database |
| nonTrackedCompanyIds  | Array of Company Ids which are not been tracked                          |
| removedCompanyIds     | Array of Company Ids which are removed                                   |

<br>


# Remove Trigger

Remove a Trigger from tracking

`DELETE /api/v1/trigger/{GROUP_NAME}/{TRIGGER_CODE} HTTP/1.1`

Replace TRIGGER\_CODE with the Intellizence Trigger Code that you would like to remove and GROUP\_NAME with the Group Name

**Response body**

```
{
            "status": "status_code"
}
```

| Status code | Description                 |
| ----------- | --------------------------- |
| 200         | Trigger removed             |
| 201         | Post a valid Trigger Code   |
| 202         | Trigger is not been tracked |
| 404         | Group Name does not exist   |

<br>


# Bulk Remove Triggers

Remove triggers from tracking

`DELETE /api/v1/trigger/{GROUP_NAME} HTTP/1.1`

Replace GROUP\_NAME with the Group Name under which the triggers have to be removed

**Request body**

```
{
            "triggerCodes": ["trigger_code"]
}
```

| Param         | Mandatory | Description                                                       |
| ------------- | --------- | ----------------------------------------------------------------- |
| trigger\_code | Y         | Array of Intellizence Trigger Codes that you would like to remove |

**Response body**

```
{
            "nonExistingTriggerCodes": ["trigger_code"],
            "nonTrackedTriggerCodes": ["trigger_code"],
            "removedTriggerCodes": ["trigger_code"]
}
                                        
```

| Param                   | Description                                                                |
| ----------------------- | -------------------------------------------------------------------------- |
| nonExistingTriggerCodes | Array of Trigger Codes which are not existing in the Intellizence database |
| nonTrackedTriggerCodes  | Array of Trigger Codes which are not been tracked                          |
| removedTriggerCodes     | Array of Trigger Codes which are removed                                   |


# Delete Group

Delete a group

`DELETE /api/v1/group/{GROUP_NAME} HTTP/1.1`&#x20;

Replace GROUP\_NAME with the group name that you would like to delete

### **Response body**

```
{
            "status": "status_code",
            "message": "status_message"
}                       
```

| Status code | Description               |
| ----------- | ------------------------- |
| 200         | Group deleted             |
| 404         | Group Name does not exist |

<br>


# Recommend Company

Recommend a Company Name to be added in the Intellizence database

POST /api/v1/recommend-company HTTP/1.1

**Request body**

```
{
            "name": "company_name",
            "domain": "company_domain_name",
            "notes": "notes"
}
```

| Param                                                 | Mandatory | Description                                                                               |
| ----------------------------------------------------- | --------- | ----------------------------------------------------------------------------------------- |
| name                                                  | N         | Company Name that you would recommended to be added in the Intellizence database          |
| domain                                                | N         | Company Domain Name that you would recommended to be added in the Intellizence database   |
| notes                                                 | N         | Any comments / notes that you want to add to help us in resolving the recommended company |
| Input either Company Name or/and Company Domain Name. |           |                                                                                           |

**Response body**

```
{
            "status": "status_code",
            "message": "status_message",
            "recommendation":{
                  "id": "recommendation_id",
                  "ETA": "ETA"
            }
}                                   
```

| Status code | Description                                      |
| ----------- | ------------------------------------------------ |
| 200         | Request to recommend a company is successful     |
| 201         | Post a valid Company Name or Company Domain Name |

| id  | Unique id given to this recommendation, which can be used to find the status of recommendation |
| --- | ---------------------------------------------------------------------------------------------- |
| ETA | ETA when this recommendation be acted upon                                                     |


# Check Company Recommendation Status

Check the status of the recommendation to add a Company Name in the Intellizence database

`GET /api/v1/company-recommendation/{RECOMMENDATION_ID} HTTP/1.1`

Replace RECOMMENDATION\_ID with the recommendation id that you received in response of posting the recommendation

**Response body**

```
{
            "status": "status_code",
            "message": "status_message",
            "matches":[
                   {
                        "id": "company_id",
                        "name": "company_name",
                        "domain": "company_domain"
                   }
            ]
}
                                        
```

| Status code                 | Description                                                                                                           |
| --------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| 201                         | Recommendation request is pending                                                                                     |
| 404                         | Invalid recommendation id                                                                                             |
| EXACT\_MATCH                | Exact match found for the recommended company name and the recommended company name is added in Intellizence database |
| REBRANDED\_MERGED\_ACQUIRED | The recommended company is been rebranded or merged or acquired.                                                      |
| MULTI\_MATCHES              | There are many matches exist for the recommended company name                                                         |
| INVALID                     | The recommended company name is invalid                                                                               |

| matches | <p>Array which contains:</p><ul><li>Intellizence company id, name and domain in case of EXACT\_MATCH and REBRANDED\_MERGED\_ACQUIRED</li><li>All matching company names and domains in case of MULTI\_MATCHES</li><li>Empty array in case of INVALID</li></ul> |
| ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |


# Search Signals - By Company ID

GET /api/v2/company-signals/{INTELLIZENCE\_COMPANY\_ID} HTTP/1.1

Replace INTELLIZENCE\_COMPANY\_ID with the company id that you would like to get the signals

**Parameters**

| Param     | Mandatory | Description             |
| --------- | --------- | ----------------------- |
| startDate | Yes       | Start Date (DD/MM/YYYY) |
| endDate   | Yes       | End Date (DD/MM/YYYY)   |

**Response body**

```
{
    "status": "status_code",
    "news": [
        {
            "_id": "new_id_1",
            "publisher": "news_publisher_1",
            "title": "new_title_1",
            "url": "new_url_1",
            "desc": "news_content_1",
            "publishDate": "news_published_date_1",
            "companyIds": ["Intellizence_company_id_1", "Intellizence_company_id_2"],
,           "companies": ["company_1", "company_2"],
            "triggerCodes": ["Intellizence_trigger_code_1", "Intellizence_trigger_code_2"],
            "triggers": ["trigger_1", "trigger_2"]
            "topics": ["topic_1", "topic_2"]
        }
    ]
}
```


# Search Signals - By Group and Company IDs

Returns news based on search parameters

POST /api/v2/search HTTP/1.1

**Request Body**

```
{
    "startDate": "start_date",
    "endDate": "end_date",
    "group": "group",
    "companyIds": "company_ids",
    "triggerCodes": "trigger_codes",
    "limit": "limit",
    "ts": "ts",
    "keyword": "keyword"
}
```

| Param        | Mandatory | Description                                                                                                                                             |
| ------------ | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| startDate    | N         | It will return news published from this date in format DD/MM/YYYY                                                                                       |
| endDate      | N         | It will return news published till this date in format DD/MM/YYYY                                                                                       |
| group        | N         | It will return news for the Companies and Triggers under this Group Name                                                                                |
| companyIds   | N         | Array of company ids. It will return news for these company ids. If companyIds is not passed, news for all the tracked companies will be returned.      |
| triggerCodes | N         | Array of trigger codes. It will return news for these trigger codes. If triggerCodes is not passed, news for all the tracked triggers will be returned. |
| limit        | N         | Default value is 100. Number of news items. If startDate and endDate are not passed, it will return latest 'N' news depending on limit value.           |
| ts           | N         | This can be used for pagination. Next set of news  items after this 'ts' value is returned.                                                             |
| keyword      | N         | If you want to search and get news having this keyword in news title or description.                                                                    |

**Response body**

```
{
    "status": "status_code",
    "news": [
        {
            "hash": "new_id",
            "publisher": "news_publisher",
            "title": "new_title",
            "url": "new_url",
            "desc": "news_description",
            "publishDate": "news_published_date",
            "companyIds": ["Intellizence_company_id_1", "Intellizence_company_id_2"],
,           "companies": ["company_name_1", "company_name_2"],
            "triggerCodes": ["Intellizence_trigger_code_1", "Intellizence_trigger_code_2"],
            "triggers": ["trigger_1", "trigger_2"]
            "topics": ["topic_1", "topic_2"],
            "ts": "timestamp of this news. Used for pagination.",
            "similarNews": "Array of similar news",
            "companyDomains": ["company_domain_1", "company_domain_2"] 
        }
    ]
}
```

| Status code | Description                            |
| ----------- | -------------------------------------- |
| 0           | Success                                |
| -3          | No company ids or trigger codes found. |


# Push News

Post news to the given REST end point

`POST /api/v1/push-news/{GROUP_NAME}/{DAYS} HTTP/1.1`

Replace GROUP\_NAME with the Group Name and DAYS with the number of days for which news have to be posted.&#x20;

Maximum number of days can be 5&#x20;

You’ll have to pass the REST end point URL to which news have to be posted in HTTP header with the name callback-url.

**Response body**

```
{
            "response": "response"
}
```

| Param    | Description                                                      |
| -------- | ---------------------------------------------------------------- |
| response | Response received from the `callback-url` after posting the news |

**News are posted in the JSON format**

```
{
    "group": "group_name",
    "postedDate": "posted_date",
    "news": [
        {
            "id": "new_id",
            "publisher": "news_publisher",
            "title": "new_title",
            "url": "new_url",
            "desc": "news_desc",
            "publishDate": "news_published_date",
            "companies": [ 
               {
                "id": "Intellizence_company_id"
                }
            ],
            "triggers": ["trigger"]
        }
    ]
}
```