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

# GET /v1/events/ma

> Discover filing-derived merger and acquisition signals from public-company disclosures

Discover filing-derived merger and acquisition signals from public-company disclosures

<Info>
  Audience: application and coding agent.
</Info>

## Coverage and source scope

Returns merger and acquisition candidates inferred from SEC filings and relevant exhibits. It is a research surface, not a definitive deal feed or closing-status record. Preserve the cited accession and source fields, and treat filing dates as disclosure timing rather than announcement, signing, or closing dates. Use the returned `nextCursor` value with the same filters. The bounded submission scan can leave older matching filings outside the result. See [API conventions](https://docs.secapi.ai/api-conventions).

## Agent mode

Pass `?view=agent` to receive the compact agent shape: deal structure fields (event type, status, consideration type, counterparty), headline, and the cited filing URL. The longer summary and per-row provenance, freshness, and materialization blocks are omitted. See [api conventions → response formats](/api-conventions) for the full `?view=` contract.

## Canonical metadata

* `requestId`
* `traceparent`
* `per-row provenance`
* `per-row freshness`
* `per-row materialization`

## Example request

<RequestExample>
  ```bash theme={null}
  curl -X GET \
    -H "x-api-key: $SECAPI_API_KEY" \
    -H "secapi-version: 2026-03-19" \
    "https://api.secapi.ai/v1/events/ma?ticker=AAPL&limit=10"
  ```
</RequestExample>

## Example response

<ResponseExample>
  ```json theme={null}
  {
    "object": "list",
    "data": [
      {
        "object": "ma_event",
        "ticker": "EXAMPLE",
        "form": "8-K",
        "filingDate": "2026-03-18",
        "accessionNumber": "0000000000-26-000001",
        "eventType": "acquisition",
        "status": "announced",
        "considerationType": "cash",
        "counterparty": "Example counterparty",
        "headline": "Example issuer announces acquisition",
        "provenance": {
          "source": "sec",
          "accessionNumber": "0000000000-26-000001",
          "filingUrl": "https://www.sec.gov/Archives/edgar/data/0000000/example.htm",
          "retrievedAt": "2026-03-18T16:00:00.000Z",
          "parserVersion": "2026-03-18.1"
        }
      }
    ],
    "hasMore": false,
    "nextCursor": null,
    "requestId": "req_2ZK8Q1W9F4M6P7R3"
  }
  ```
</ResponseExample>

## Give this prompt to your agent

<Prompt>
  Use SEC API GET /v1/events/ma to discover filing-derived merger and acquisition signals from public-company disclosures. Preserve `requestId`, `traceparent`, `per-row provenance`, `per-row freshness`, `per-row materialization` in the output. Return a concise markdown summary plus the exact structured payload fields that a downstream engineer or agent should keep using this result.
</Prompt>

## Failure posture

* treat non-2xx responses as contract-aware failures, not free-form errors
* preserve `requestId` and `traceparent` in logs and downstream reports
* if provenance or freshness metadata is present, return it unchanged so trust is not lost in the handoff