US Equities Index Components
Daily membership lists of major US equity indexes (one ticker and name per component, one file per index per trading day), plus a separate per-index change file recording additions, removals and name changes. Intended for research and historical backtesting.
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. TWO TABLES: (1) Daily membership (matches the sample): columns ConstituentTicker, ConstituentName, one file per index per trading day; this is the table described in `columns`. (2) Change history (not in the sample), one file per index, columns per Guide Table 3 example: TradeDate (date, yyyymmdd by example), AddedConstituentTicker, AddedConstituentName, DroppedConstituentTicker, DroppedConstituentName. No types, missing rules or file name are documented for table 2. Change-file semantics from the guide example (S&P 500): each row pairs an added and a dropped constituent on a TradeDate (20211220: EPAM/HBI, FDS/LEG, SBNY/WU), but a row may have only an addition (SEDG) or only a drop, so rows are not strictly one-for-one. The changes file also records name changes: the FRT row on 20220106 lists the same ticker as both added and dropped with slightly different names (trailing period), which is a rename, not a membership change. Point-in-time: membership is given per trading day, so reconstruct the as-of set by selecting the daily file for the date. The guide warns that actual changes in index members might be delayed by a few days in this data, so it is NOT an exact effective-date record; use for research and backtesting only, not for compliance or replication. Identifiers: ticker and name only. No SecId, ASID, CUSIP or ISIN, no weight, share count, sector or index-code column. Tickers are as of the file date, so map to securities with a security master on (ticker, date); share-class tickers use a dot in the sample.
Coverage
Dow Jones Industrial Average, Dow Jones Transportation Average, Dow Jones Utility Average, S&P 500, NASDAQ 100 (page: based on QQQ holdings), Russell 1000 and Russell 2000. History from 2007, Russell indexes from July 2009. Guide note: intended solely for research and backtesting; actual index changes may be delayed by a few days.
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 and page describe two tables per index: a daily components list and a separate historical changes file. The published sample is only the daily list (Russell 2000, 1917 rows, columns ConstituentTicker and ConstituentName); the changes file is shown only as a sample table (Guide Table 3) with no type/missing/description table.
- Documentation discrepancyNeither the daily-list sample nor its guide schema (Table 2) has a date or index-identifier column; both are implied by the file (guide example: 'all components for SPX on Mar 3, 2020 are stored in one CSV file') and the file-naming scheme is undocumented.
- Documentation discrepancyThe page says NASDAQ 100 membership is 'based on QQQ holdings'; the guide intro lists NASDAQ 100 without that qualifier.
- Documentation discrepancyGuide Table 3 prints the changes-file header wrapped across lines (e.g. 'AddedConst' / 'ituentTicker'); the full names AddedConstituentTicker, AddedConstituentName, DroppedConstituentTicker, DroppedConstituentName are reconstructed from the wrapped text and are not confirmed by any sample CSV.
2 columns in delivery order · file or table name eq_index_comp. Types are ODCS logical types; the format line shows how values are written.
| Column | Type | Key | Description |
|---|---|---|---|
| ConstituentTicker | string | Key 1 · Required | Symbol name of the index component on the trading day of the file; share classes use a dot (e.g. CRD.A, GEF.B, MOG.A in sample). Missing values: unstated (always populated in sample) · Source: vendor guide and sample |
| ConstituentName | string | Name of the index component security. Missing values: unstated (always populated in sample) · 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: ConstituentTicker) 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; by default one file per trading day per index (example: all S&P 500 (SPX) components on 2020-03-03 in one file). A separate file per index holds all historical changes. The guide does not state bucket/path or file-name conventions; the published sample is eq_index_comp_r2000.csv (Russell 2000 daily list).
- 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/index-comp
- 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
- 2007-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.