M&A
Detect whether a company was acquired or made acquisitions in the recent window, with counterparty, deal status, and value where disclosed.
What it answers
The M&A signal detects mergers and acquisitions in both directions: the queried company being acquired (role: acquiree) and the queried company acquiring others (role: acquirer). It reports the counterparty, the deal status, and the value where disclosed.
Only true acquisitions — a transfer of control — count. Minority investments, funding rounds, and partnerships are excluded. The deal status distinguishes a closed deal from one that was merely announced or that later collapsed: an announced deal that is subsequently called off or blocked is terminated, never completed.
The window differs by direction: an acquisition of the company (acquiree) is a durable ownership fact reported at any age, while the company acquiring others (acquirer) is a recency signal limited to the last 24 months.
Key: mna · Scope: company · Cost: 0.75 credits per fresh result (cache serves and failures are free)
The legacy routes (POST /v1/signals/mna and POST /v1/signals/sync/mna) keep working at their old 2-credit price until their announced sunset — responses carry Deprecation and successor Link headers. New integrations should use the endpoint above.
Request
Provide only a domain.
curl -X POST https://api.saber.app/v1/companies/enrich/mna \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"domain": "figma.com"
}'For webhook delivery, call the same endpoint with a webhookUrl to have the completed result delivered.
| Field | Type | Required | Description |
|---|---|---|---|
domain | string | yes | Company domain to research. |
webhookUrl | string | no | Where to deliver the completed result when the run finishes (202 path). On a 200 cache serve the answer is already in the response. |
forceRefresh | boolean | no | Bypass the cache and force a fresh run. |
Response
A completed run's result conforms to the M&A answer schema:
(The legacy /v1/signals routes return the same payload under answer.jsonSchema.)
{
"detected": true,
"latestEvents": [
{
"role": "acquiree",
"counterparty": "Adobe",
"status": "terminated",
"amount": 20000000000,
"currency": "USD",
"announcedAt": "2022-09-15",
"sourceUrls": ["https://news.adobe.com/news/2023/12/adobe-figma-update"]
}
]
}| Field | Type | Description |
|---|---|---|
detected | boolean | True if at least one corroborated announced, completed, or terminated acquisition was found. A rumored-only finding does not count. |
latestEvents | array | The one to three most relevant events, most recent first. Each carries role (acquirer/acquiree), counterparty, status (rumored/announced/completed/terminated), optional amount/currency, announcedAt, and sourceUrls. |
detected is always present; latestEvents appears when there is a qualifying event.
Evidence
An acquisition backed only by a data aggregator, with no primary corroboration — acquirer or acquiree press/IR, a regulatory or securities filing, or major business press — does not meet the bar for detected: true or status: completed. Such a finding is treated as at most rumored, and detected stays false unless a primary source confirms the deal. Deal amounts are omitted rather than reported as zero when undisclosed.