US Equities Lookup File

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. To find the SecId for a ticker you need a trading date: a ticker can map to different SecIds over time (guide examples: AAC maps to three securities in 20070103-20100205, 20101213-20121015 and 20141002-20191025; S was Sprint Nextel and later Sprint). Resolve with StartDate <= date <= EndDate. Date-window semantics: dates are yyyymmdd; EndDate 29991231 means the ticker still maps to the SecId. In the sample, adjacent windows for one ticker are back-to-back (AA: 33008 to 20161031, 4920498 from 20161101) so EndDate acts as an inclusive last date; there are gaps (AAC 20100205 to 20101213) where the ticker was unassigned. In the 100-row sample, windows for the same ticker never overlap, so (Ticker, date) resolves to at most one SecId; (Ticker, StartDate) was unique, but the same Ticker+SecId pair can appear in two windows (AAUK / 75522 twice, with a gap), so the safer key includes SecId and StartDate. One security can span several SecIds (guide cites GOOG and GOOGL as a case where two or more SecIds must be linked); use the ASID Lookup dataset to chain SecIds into one continuous security history.

Coverage

US listed and delisted equity securities from 2007 to present (guide intro for the Security Master/Lookup set; lookup file sample starts 20070103). Page describes two versions: Ticker-to-SecId and FIGI-to-SecId.

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 (7)

• Primary key is inferred; AlgoSeek's guide does not name one.
• Update cadence and publication latency are not stated in the guide; confirm with AlgoSeek (or GET /v1/meta/datasets/{id}/status).
• Documentation discrepancyPage and guide describe two lookup versions (Ticker-to-SecId, FIGI-to-SecId) but only the Ticker file has a published sample header; the FIGI file's columns are known only from the guide (Tables 7-8), so FIGI is listed as a guide-only column of a different file, not of the ticker file.
• Documentation discrepancyGuide intro says algoseek 'provides three versions of lookup files', counting the ASID lookup; the page and this dataset cover only ticker and FIGI mappings (ASID is its own dataset).
• Documentation discrepancyGuide gives no 'Missing' column for the lookup files, so null/blank behaviour is unstated (sample has no blanks).
• Documentation discrepancyGuide states no update frequency for the lookup files (only the Security Master and ASID Lookup are stated as updated daily).
• Documentation discrepancySample is ordered by ticker in ASCII order (lowercase suffix tickers such as AAp, AApB, AAw sort after uppercase), not by date or SecId.