Skip to main content

Welcome to the Acquisition Signals API

The Acquisition Signals API provides access to comprehensive, real-time acquisition signals aggregated from across the web. Our platform continuously monitors and collects acquisition activity, giving you up-to-date information on M&A deals, acquirers, and market trends.

Acquisition Signals Endpoint

View the complete OpenAPI specification

Count Mode

You can get the total number of results matching any filter combination without consuming credits by adding count=true to your request. This returns an empty data array with full pagination metadata, including totalCount.
Response:
Use count mode to preview how many results match your filters before fetching actual data. This is useful for building filter UIs, showing result counts, or validating queries — all at zero credit cost.

Key Features

  • Real-time Signals: Acquisition signals are aggregated continuously from web sources
  • Advanced Filtering: Filter by countries, categories, subcategories, date ranges, and search terms
  • Numeric Range Filters: Filter by amount, employee count, and founded year
  • Flexible Sorting: Sort by date, amount, or employee count
  • Verification Status: Filter signals by verified, unverified, or pending status
  • Pagination Support: Efficiently retrieve large datasets with up to 100 results per page
  • Rich Response Data: Detailed company information, acquisition amounts, and acquirer data
  • Credit-based Usage: Transparent credit consumption per API call

Company fields and acquirer object

The acquired company uses companyCountry and companySubcategory on the root of each signal. The nested acquiringCompany object uses the same naming (companyCountry, companySubcategory) so all company HQ fields are consistent across the API. See Company fields in signal responses.

Service Level

  • Rate Limit: Based on your subscription tier
  • Uptime: 99% guaranteed uptime
  • Data Freshness: Real-time aggregation ensures up-to-date signals
  • Maximum Results: Up to 100 results per page

Authentication

All API endpoints require authentication using a Bearer token passed in the Authorization header.
If you know a company’s website domain or LinkedIn page, query by URL instead of by name. Name search is fuzzy and can return lookalikes (Novartis also matches Novartis UK); URL identifiers match exactly one company.
Accepted input formats. URL identifiers are normalized before matching, so equivalent variants return the same results:
  • company_domain: novartis.com, www.novartis.com, https://www.novartis.com/, https://novartis.com/any/path — scheme, www., port, path and trailing slash are ignored. Values that can’t be reduced to a domain return 400.
  • company_linkedin_url: linkedin.com/company/novartis, https://www.linkedin.com/company/Novartis/http/https, www. and trailing slash are ignored, the slug is case-insensitive. URLs that aren’t LinkedIn company pages (e.g. personal /in/ profiles) return 400.
Strict matching. When a URL identifier is provided, the API never falls back to fuzzy name matching: if no company matches, the result is empty. Identifiers combine with ANDcompany_domain=novartis.com&company_name=Acme returns empty because they disagree. Match confidence. Every result row includes match_confidence:

Query Parameters

Pagination

Date Filters

Company Filters

Numeric Range Filters

Acquisition-specific Filters

Sorting

Response Structure

All successful responses follow this structure:

Error Handling

The API returns standard HTTP status codes:
  • 200: Success
  • 401: Unauthorized - Invalid or missing API key
  • 429: Rate limit exceeded
  • 500: Internal server error
Error responses include:

Example Usage

Filter by Date Preset and Country

Filter by Amount and Acquiring Company

Filter by Subcategory with Sorting

Combined Filters