---
title: "De-SPAC lifecycle: one row per SPAC business combination tracked from the"
method: GET
path: "/v1/de-spac-events"
---

# De-SPAC lifecycle: one row per SPAC business combination tracked from the

`GET /v1/de-spac-events`

## Request

- Base URL: `https://api.alphanume.com`
- URL: `https://api.alphanume.com/v1/de-spac-events`
- Auth: one of:
  - API key in header `X-API-Key`
  - HTTP bearer

De-SPAC lifecycle: one row per SPAC business combination tracked from the
definitive-agreement announcement through registration, definitive proxy, shareholder
vote, exchange listing and completion (or termination / trust liquidation). Every row
carries the SPAC's own symbol (prior_ticker), the combined company's symbol as soon as a
filing names it (new_ticker -- the definitive proxy does so in most deals, weeks before
the close), warrant ticker, exchange, SPAC / target / new company names, and the dated
milestones: announced_date, meeting_date, record_date, vote_approved_date,
listing_filed_date, expected_close_date and expected_trading_date (each with a *_basis
column saying whether the date was stated in a filing or derived), closing_date,
trading_commencement_date, terminated_date, plus next_event_date / next_event_type for
what comes next. Completed rows also carry the closing financials (redemption shares and
dollars, trust remaining, PIPE, gross proceeds, pro forma shares, enterprise and equity
value), a confidence score and the supporting evidence quote. `date` is the SEC filing
date of the filing that set the row's current status (for completed deals: the closing
8-K). `ticker` is the symbol trading for the deal today (new_ticker once listing is
pending, otherwise prior_ticker). Fields are null where no filing supported them;
quality_flags lists any rule that altered or withheld a value.

Use status=pending&upcoming=true to see de-SPACs before the new symbol trades,
ticker=<SPAC symbol> to follow one deal, view=history to replay what was known on a
given date, or status=completed with a date range for the classic redemption-rate
event study.

Requires an Alphanume Pro API key. A 403 PRO_SUBSCRIPTION_REQUIRED or
DATE_RANGE_RESTRICTED error means the key's plan does not cover the request --
it does not mean the data is missing.

## Query parameters

- `date` string
- `date_gte` string
- `date_lte` string
- `date_gt` string
- `date_lt` string
- `status` string
- `ticker` string
- `upcoming` string
- `next_event_lte` string
- `updated_since` string
- `view` 'latest' | 'history'

## Response `200`

Matching rows.

- Envelope
  - `count` integer, required
  - `data` object[], required

## Other responses

- `400`: Invalid or conflicting query parameters.
- `401`: Missing or unrecognized API key.
- `403`: PRO_SUBSCRIPTION_REQUIRED: the key's plan does not include API access; every endpoint requires an active Pro subscription. DATE_RANGE_RESTRICTED: a legacy free-tier key asked for dates outside its window. In both cases the data is not missing.
- `429`: Rate limit exceeded (600/min); the body carries retry_after_seconds.

---

[API](https://skmtc.dev/alphanume/apis/alphanume-api.md) · [All operations](https://skmtc.dev/alphanume/apis/alphanume-api/llms.txt) · [OpenAPI document](https://skmtc.dev/alphanume/apis/alphanume-api/revisions/2cb83f10bba4?raw)