> ## Documentation Index
> Fetch the complete documentation index at: https://agent-docs.akta.pro/llms.txt
> Use this file to discover all available pages before exploring further.

# Company M&A and Investment API Overview

> Acquisitions, investments, acquirers, deal terms

The akta.pro Company M\&A and Investment API returns the `mna_and_investment` section of the akta.pro company record as a standalone endpoint. Pass a company website domain or UUID in the path and get back just the `mna_and_investment` payload — no other sections, no sections parameter to configure.

This is a **synchronous GET API**. Pass the company in the URL path and receive the m\&a and investment payload immediately in the HTTP response. No polling required.

<Info>
  Need multiple sections together or a different set of fields? Use the [Company Data API](/docs/company-data/overview) and pass the sections you want via the `sections` parameter.
</Info>

**The fields included in every response:**

| Field          | What it contains                                           |
| -------------- | ---------------------------------------------------------- |
| `acquisitions` | List of acquisitions with date, target, deal value, source |
| `investments`  | List of investments with date, target, amount, source      |
| `acquirers`    | List of acquirers                                          |
| `deal_value`   | Deal value                                                 |
| `deal_date`    | Deal date                                                  |

**Common use cases:**

* **M\&A timeline** : render `acquisitions` chronologically on a corporate-development dashboard
* **Acquisition-target sourcing** : filter companies by their `investments` portfolio
* **Buyer profiling** : surface `acquirers` on a target's profile so reps know who's been in the space

<Info>
  This section is available on Subscription and Enterprise plans. Requests from other plans return a 403 error.
</Info>

<Info>
  This API is synchronous. The m\&a and investment payload is returned directly in the HTTP response. No job submission or polling required.
</Info>

***