> ## Documentation Index
> Fetch the complete documentation index at: https://api.tryspecter.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Get company acquisitions
> Returns the acquisitions a company is involved in — both deals where it was the acquirer and deals where it was the acquiree — newest first. Every row carries both sides, so you can tell the direction of each deal. Use either `acquirer_company_id` or `acquiree_company_id` with [Get company by ID](/api-reference/companies/get-company-by-id) to pull the other party's full record.
Costs 1 credit per request.
## Behaviour
- A company can appear as the acquirer on some rows and the acquiree on others.
- Ordered by `acquisition_date` descending, with nulls last.
- Page through results with `limit` and `page` (`page` is zero-based; `limit` defaults to 50, max 1000).
- Returns `404` if the company ID doesn't exist. A company with no acquisitions returns `200` with an empty array.
## OpenAPI
````yaml /api-ref/bundle_api.yaml get /companies/{companyId}/acquisitions
openapi: 3.0.0
info:
title: Specter API
termsOfService: https://tryspecter.com/terms/
contact:
name: API support
email: api-support@tryspecter.com
version: 1.0.0
servers:
- description: Production
url: https://app.tryspecter.com/api/v1
security:
- ApiKeyAuth: []
tags:
- name: Enrichment
description: >
Endpoints which can be used to query for data and, if the data is not
found request that it be retrieved by Specter systems.
- name: Companies
description: >
Endpoints that provide the most up to date information about all the
companies in our data set. Giving the ability to query by a specific
company id, or using a keyword such as the domain.
This also allows us to enrich the data about a company if we either do not
have it or it is older than expected, which means you always have the most
up-to-date information possible.
- name: People
description: >
Endpoints that expose Specter people records — profile data and contact
details — for a known person ID.
- name: Investors
description: >
Endpoints that expose Specter investor records — profile, activity,
targeting, funds, portfolio companies, and the funding rounds they have
participated in — for a known investor ID.
- name: Talent and Interest Signals
description: >
Endpoints for retrieving Specter Talent Signals and Investor Interest
Signals by ID.
- name: News Signals
description: >
Company-level news signals generated from articles monitored by Specter.
Each signal represents a single classified company mention within an
article and includes a summary of the newsworthy update (such as funding,
deals, revenue, profitability, or traction) along with an assigned
importance score.
- name: Revenue Signals
description: >
Revenue and profitability observations for companies, derived from news
coverage and public filings. Each signal captures one data point — the
revenue or profitability metric, the year it refers to, the source, and
the company it is attributed to.
- name: Transactions
description: >
Endpoints that expose transaction detail — funding rounds, acquisitions,
and IPOs — by ID.
- name: Company Lists
description: >
Create, query and maintain lists of companies that are of particular
interest. The endpoints here allow you to interrogate and maintain those
lists using a programmatic interface.
- name: People Lists
description: >
Create, query and maintain lists of people that are of particular
interest. The endpoints here allow you to interrogate and maintain those
lists using a programmatic interface.
- name: Investor Lists
description: >
Create, query and maintain lists of investors that are of particular
interest. The endpoints here allow you to interrogate and maintain those
lists using a programmatic interface.
- name: Network
description: >
Endpoints for accessing your team's LinkedIn network - the people and
companies your teammates are connected to.
- name: Saved Searches
description: >
Manage searches that have been saved via `tryspecter.com`. These endpoints
are useful to programmatically list and delete saved searches. To update a
search the UI should be used at `tryspecter.com`.
- name: Company Saved Searches
description: >
Query and get results for company searches that have been saved via
`tryspecter.com`. These endpoints are useful to programmatically get
results and information for a search. To update a search the UI should be
used at `tryspecter.com`.
- name: People Saved Searches
description: >
Query and get results for people searches that have been saved via
`tryspecter.com` or via the API. These endpoints are useful to
programmatically get results and information for a search. To update a
search the UI should be used at `tryspecter.com`.
- name: Investor Saved Searches
description: >
Query and inspect saved investor searches — metadata (name, match counts)
and paginated results — from searches saved via `tryspecter.com` or shared
with the API.
- name: Talent Signals Saved Searches
description: >
Query and get results for Talent Signals searches that have been saved via
`tryspecter.com`.
- name: Investor Interest Saved Searches
description: >
Query and get results for Investor Interest Signals searches that have
been saved via `tryspecter.com`.
- name: Organization
description: >
Endpoints for accessing your organization's members and org-level
resources.
- name: Customer Data
description: >
Retrieve a log of API calls made by your organization. Useful for auditing
usage, debugging integrations, and monitoring activity.
paths:
/companies/{companyId}/acquisitions:
get:
tags:
- Companies
summary: Get company acquisitions
description: >
Returns the acquisitions a company is involved in — both deals where it
was the acquirer and deals where it was the acquiree — newest first.
Every row carries both sides, so you can tell the direction of each
deal. Use either `acquirer_company_id` or `acquiree_company_id` with
[Get company by ID](/api-reference/companies/get-company-by-id) to pull
the other party's full record.
Costs 1 credit per request.
## Behaviour
- A company can appear as the acquirer on some rows and the acquiree on
others.
- Ordered by `acquisition_date` descending, with nulls last.
- Page through results with `limit` and `page` (`page` is zero-based;
`limit` defaults to 50, max 1000).
- Returns `404` if the company ID doesn't exist. A company with no
acquisitions returns `200` with an empty array.
parameters:
- $ref: '#/components/parameters/CompanyId'
- $ref: '#/components/parameters/PaginationLimit'
- $ref: '#/components/parameters/PaginationPage'
responses:
'200':
description: >
A page of acquisitions involving the company. The same company may
appear on either side: as the acquirer (outbound) or as the acquiree
(inbound).
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/PublicAcquisition'
headers:
Link:
schema:
type: string
description: RFC 5988 pagination links (`first`, `prev`, `next`, `last`).
X-Total-Count:
schema:
type: integer
description: Total number of acquisitions matching the query.
X-Page:
schema:
type: integer
description: Zero-based index of the page returned.
X-Page-Size:
schema:
type: integer
description: Number of items per page.
X-Total-Pages:
schema:
type: integer
description: Total number of pages available.
'401':
$ref: '#/components/responses/Unauthorized'
'402':
$ref: '#/components/responses/OutOfCredits'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
'429':
$ref: '#/components/responses/RateLimits'
components:
parameters:
CompanyId:
in: path
name: companyId
schema:
type: string
required: true
description: The Specter company ID.
PaginationLimit:
in: query
name: limit
schema:
type: number
required: false
description: The number of results to return, default is 50.
PaginationPage:
in: query
name: page
schema:
type: number
required: false
description: The page number of results to return, base 0, default is 0.
schemas:
PublicAcquisition:
properties:
acquisition_id:
description: |
The Specter ID for this acquisition.
type: string
example: acq_b59797f0d5cb3c8e63b5d098
acquirer_company_id:
description: >
The Specter company ID of the **acquirer**. Use with `GET
/companies/{companyId}` to fetch the full company record.
type: string
example: 6270fedd4b7ad6a07cbd0326
acquirer_name:
description: The acquirer company's name.
type: string
example: Deel
acquirer_domain:
description: The acquirer's primary domain.
type: string
nullable: true
example: deel.com
acquiree_company_id:
description: >
The Specter company ID of the **acquiree**. Use with `GET
/companies/{companyId}` to fetch the full company record.
type: string
example: 6204bf4607449e8f64aa6198
acquiree_name:
description: The acquiree company's name.
type: string
example: Deel IT (Previously Hofy)
acquiree_domain:
description: The acquiree's primary domain.
type: string
nullable: true
example: hofy.com
acquisition_type:
description: >
The type of deal. One of `acquisition`, `merge`, `lbo`, `acquihire`,
or `management_buyout`. Null when Specter could not classify the
deal.
type: string
nullable: true
enum:
- acquisition
- merge
- lbo
- acquihire
- management_buyout
example: acquisition
price_usd:
description: Deal value in USD, if disclosed.
type: integer
nullable: true
example: 100000000
acquisition_date:
description: Date the acquisition was announced or closed (YYYY-MM-DD).
type: string
format: date
nullable: true
example: '2024-07-18'
required:
- acquisition_id
- acquirer_company_id
- acquirer_name
- acquiree_company_id
- acquiree_name
additionalProperties: false
title: Acquisition
type: object
ApiKeyMissing:
properties:
errorCode:
description: API_KEY_MISSING
example: API_KEY_MISSING
type: string
message:
description: No API Key was presented on the header X-API-KEY
example: No API Key was presented on the header X-API-KEY
type: string
ApiKeyNotValid:
properties:
errorCode:
description: API_KEY_NOT_VALID
example: API_KEY_NOT_VALID
type: string
message:
description: API key present, but not valid
example: API key present, but not valid
type: string
responses:
Unauthorized:
description: Unauthorized
content:
application/json:
schema:
oneOf:
- $ref: '#/components/schemas/ApiKeyMissing'
- $ref: '#/components/schemas/ApiKeyNotValid'
OutOfCredits:
description: Out of credits - API credit limit exceeded
content:
application/json:
schema:
type: object
required:
- errorCode
- message
properties:
errorCode:
type: string
enum:
- OUT_OF_CREDITS
message:
type: string
description: |
There are no more credits available to complete the request.
headers:
X-CreditLimit-Limit:
schema:
type: integer
description: The total number of credits allocated for the current period
X-CreditLimit-Remaining:
schema:
type: integer
description: The number of credits remaining for the current period
X-CreditLimit-Reset:
schema:
type: number
format: float
description: The number of seconds until the credit limit resets
Forbidden:
description: Forbidden - There is no permissions to use the endpoint
content:
application/json:
schema:
type: object
properties:
errorCode:
description: NOT_PERMITTED
type: string
example: NOT_PERMITTED
message:
type: string
description: You do not have permission to access this resource.
example: You do not have permission to access this resource.
required:
- errorCode
- message
NotFound:
description: Not Found
content:
application/json:
schema:
type: object
required:
- errorCode
- message
properties:
errorCode:
type: string
description: NOT_FOUND
message:
type: string
description: Not Found
RateLimits:
description: Too Many Requests - API Rate limit exceeded
content:
application/json:
schema:
type: object
required:
- errorCode
- message
properties:
errorCode:
type: string
description: RATE_LIMITED
message:
type: string
description: You have been rate-limited
headers:
X-RateLimit-Limit:
schema:
type: integer
description: The total rate limit allowed for this endpoint
X-RateLimit-Remaining:
schema:
type: integer
description: The number of requests remaining
X-RateLimit-Reset:
schema:
type: number
format: float
description: The number of seconds until the rate limit resets
securitySchemes:
ApiKeyAuth:
type: apiKey
in: header
name: X-API-Key
````