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

# Events

> How Sacra models company milestones, funding rounds, secondary transactions, and corporate actions

An **event** is a structured record of something that happened at a company — a funding round, a secondary transaction, a milestone like an IPO, or a corporate action like a stock split. Events are returned in chronological order and serve as the authoritative timeline of capital activity for every company Sacra covers.

## Replacing the funding rounds endpoint

The legacy `/api/v1/funding-rounds/` endpoint covered only one kind of activity. Events supersede it with a unified model that handles the full range of things that matter to investors tracking private companies:

| Event type              | Examples                                        |
| ----------------------- | ----------------------------------------------- |
| `funding_round`         | Seed, Series A–N, growth rounds, crowdfunding   |
| `secondary_transaction` | Tender offers, direct secondary sales           |
| `company_milestone`     | IPOs, incorporations, delistings                |
| `corporate_action`      | Stock splits, reverse splits, recapitalizations |

If you're using the funding rounds endpoint today, migrate to [events](/api-reference/events/get-aggregated-events) and filter by `types=funding-round`. You'll get richer data and access to the other event types in the same response.

<Warning>The `/api/v1/funding-rounds/` endpoint is deprecated. It remains available for backward compatibility but will not receive new data or features.</Warning>

## Event envelope

Every event, regardless of type, shares a common envelope:

| Field           | Description                                                                                                                                |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| `event_id`      | Prefixed unique ID — `fr_` for funding rounds, `st_` for secondary transactions, `ca_` for corporate actions, `cm_` for company milestones |
| `event_type`    | One of `funding_round`, `secondary_transaction`, `corporate_action`, `company_milestone`                                                   |
| `event_subtype` | More specific classification — e.g. `series_a`, `tender_offer`, `ipo`, `stock_split`                                                       |
| `event_name`    | Human-readable name for the event, suitable for display in timelines                                                                       |
| `event_date`    | The primary date of the event — typically the announcement date                                                                            |
| `event_status`  | `announced`, `closed`, or `cancelled`                                                                                                      |
| `data`          | Event-specific payload — shape varies by `event_type`                                                                                      |

## Data payloads by type

The `data` field contains fields specific to each event type.

**Funding rounds** include `round_type`, `amount_raised`, `valuation`, `announced_date`, `equities` (a list of preferred share classes issued), and `is_extension` — a boolean that identifies whether the round is an extension of a prior close rather than a new series.

**Secondary transactions** include `transaction_type` (e.g. `tender_offer`), `transaction_amount`, `valuation`, `price_per_share`, `announced_date`, and `closing_date`. When a transaction is closed but only one date is known, `closing_date` is set equal to `announced_date`.

**Company milestones** and **corporate actions** include an `effective_date` alongside the announcement date, which matters for events like stock splits where the announcement and the effective date differ.

## Citations

Events support optional citations via the `include_citations=true` parameter. When enabled, each event includes a `citations` object with the sources backing the event data — article links, headlines, quotes, and publication names. This is useful when you want to surface the provenance of a funding round or transaction to end users.

<Tip>Use `updated_at_gte` for incremental syncs — see [Sync Sacra Research & Data](/guides/syncing-data) for a complete polling guide. Events are updated as new information surfaces — a round announced at one valuation may be revised as SEC filings come in.</Tip>