US Equities Announcements
One row per announced ticker change or delisting of a US exchange-listed equity, with announcement date, effective date, old/new tickers or delisting exchange. Used to anticipate and replay symbol changes and delistings.
How to use it
Rows are effective-dated. Answer point-in-time questions with the row in force on the as-of date, never the latest row. SecId and ASID are both durable AlgoSeek security keys but different values (the ASID lookup links them); tickers are reused across companies, so resolve a ticker to a key with a trade date.
Typical use
Point-in-time security identity, corporate-action adjustment, and universe construction for US equities.
Limitations
Vendor-curated reference data: rows can be restated when AlgoSeek learns of a late or corrected event, so land each delivery as a snapshot rather than overwriting history. Point-in-time: AnnounceDate is when the event became public and EffectiveDate is when it takes effect; the dataset covers announcements of FUTURE changes, so EffectiveDate is usually after AnnounceDate (sample: always later). Use AnnounceDate for as-of knowledge, EffectiveDate for the symbol/listing switch. EffectiveDate holds the effective date published at first announcement; later rescheduling is not stated to be reflected, so treat it as the initially announced date, not a confirmed one. Identity: SecId is the algoseek security identifier; Ticker is the symbol at announcement. For TickerChange, Ticker = OldTicker in every sample row and NewTicker is the post-change symbol; for Delisting, OldTicker/NewTicker are blank and DelistingExchange is set. Field applicability by EventType: TickerChange rows use OldTicker/NewTicker (DelistingExchange blank); Delisting rows use DelistingExchange (OldTicker/NewTicker blank). In the sample 94 of 100 rows are Delisting and 6 are TickerChange.
Coverage
All announcements of future symbol changes and delistings on public US exchanges; OTC excluded. Built from public sources (page: exchange listing announcements and company SEC filings). Available from 2022.
Venues (3)
- NASDAQ
- NYSE
- AMEX
Usage constraints
- Licensed vendor data: never export raw rows to a tenant-local destination or include them verbatim in a public artifact; serve only through entitlement-checked platform reads.
- Do not treat the vendor's `Ticker` as a stable identity across time; join on an AlgoSeek security key (SecId or ASID, which are distinct) or the platform symbol mapping.
Known issues (5)
- Primary key is inferred; AlgoSeek's guide does not name one.
- Documentation discrepancyGuide Table 3 shows the event name as 'Ticker Change' (wrapped across two lines); the published sample uses TickerChange.
- Documentation discrepancyGuide says EffectiveDate may be blank when the effective date is not yet defined; no sample row has a blank EffectiveDate.
- Documentation discrepancyGuide does not enumerate DelistingExchange; sample has NASDAQ, NYSE, AMEX (71/21/2 of 94 delistings) and the guide's own example uses the same three.
- Documentation discrepancyGuide intro says the data covers 'announces for symbol's name changes and Delistings'; 'name' means the ticker symbol, there is no company-name field.
8 columns in delivery order · file or table name eq_announce. Types are ODCS logical types; the format line shows how values are written.
| Column | Type | Key | Description |
|---|---|---|---|
| AnnounceDate | dateyyyymmdd | Key 1 · Required | Date on which the event was announced. Missing values: Never · Source: vendor guide and sample |
| EffectiveDate | dateyyyymmdd | Initial effective date published in the first announcement; blank when the date is not yet set. Not updated if the date later moves. Missing values: Blank · Source: vendor guide and sample | |
| SecId | integeri64 | Key 2 · Required | algoseek unique security identifier. Missing values: Never · Source: vendor guide and sample |
| Ticker | string | Symbol name; for TickerChange rows in the sample it equals OldTicker (the pre-change symbol). Missing values: Never · Source: vendor guide and sample | |
| EventType | string · enum (2) | Key 3 · Required | Type of announced listing event. Missing values: Never · Source: vendor guide and sample 2 allowed values
|
| OldTicker | string | Symbol before the change; populated for TickerChange only. Missing values: Blank · Source: vendor guide and sample | |
| NewTicker | string | Symbol after the change; populated for TickerChange only. Missing values: Blank · Source: vendor guide and sample | |
| DelistingExchange | string | Exchange the symbol is delisted from; populated for Delisting only (NASDAQ, NYSE, AMEX in sample). Missing values: Blank · Source: vendor guide and sample |
- errorrow_count_positivecompleteness
Every delivered partition (trade date, or snapshot) carries at least one row.
rowCount must be greater than 0
- errorprimary_key_uniqueuniqueness
The declared primary key is unique within each delivered partition (one file or table snapshot).
duplicateValues (properties: AnnounceDate, SecId, EventType) must be 0
Delivery
S3 flat files
AlgoSeek flat-file delivery (the layout the schema below describes).
- Layout:
- Plain-text CSV with a fixed header row; by default a single file containing all history.
- Compression:
- gzip
- Access:
- Bucket access is granted per subscription; bucket names arrive with license provisioning.
REST API
AlgoSeek Datasets REST API (X-API-KEY header; JSON, CSV or gzipped CSV). Returns AlgoSeek's normalized API layout, which differs from the flat-file columns in this contract's schema.
https://api.algoseek.com/v1/data/us-equity-ref/announce
- Authentication:
- X-API-KEY header issued by AlgoSeek
- Response formats:
- json, csv, csv_gzip
- Pagination:
- offset + limit; tick endpoints take trade_date and identifier (Ticker or ASID) in the path
Service levels
- History starts
- 2022-01-01
- First trade date of the vendor history.
- Update frequency
- Daily
- Retention
- Bounded by the license term
- Retention of landed copies is bounded by the AlgoSeek license; purge on termination.
Service levels describe the vendor feed as documented. They are draft values, not a commitment by AlphaSwarm.
Data Contract Editor · read-only preview — edits are not saved
Open-source Data Contract Editor (MIT). Changes stay in this browser tab: Cancel restores the published contract, and Download copy saves your edited YAML to your device only.
Contracts follow the Open Data Contract Standard (Bitol, LF AI & Data).
Vendor names are trademarks of their owners.