US Equities IPO

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. Row grain is one mutable record per security: the guide says each row is an individual security record and the file is rewritten (3 times daily) whenever an IPO event is new or modified, so a point-in-time history of Status transitions is NOT retained in the file; snapshot it yourself if you need as-of replay. CreatedDate = trading date the record first appeared; ModifiedDate = trading date of the last change with an optional _n version suffix (basic sample uses _1/_2/_3; many detailed-sample rows carry a bare yyyymmdd). Treat ModifiedDate as a string, not a date. Status NEW and HISTORY are date-driven (NEW while listing date is today/yesterday, HISTORY once it is more than 2 days old), so a record's Status can change without a new IPO event; the lifecycle in the guide is RUMOUR -> PENDING -> NEW -> HISTORY, with POSTPONED, WITHDRAWN and DLP as other outcomes. SecId is algoseek's security id and is already assigned to PENDING/POSTPONED IPOs; USIdentifier, ISIN and FirstTradingDate are blank until known (basic sample: blank in 68, 66 and 75 of 100 rows respectively).

Coverage

IPO data for the whole US market excluding OTC; gathered from local stock exchanges (primary) and newspapers/news agencies (secondary). Page says records typically exist several days before the first trading day. Guide gives no history start date.

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.
• Documentation discrepancyGuide says IPOs are captured at 'six different stages' but Table 4 defines seven Status values (NEW, RUMOUR, PENDING, HISTORY, POSTPONED, WITHDRAWN, DLP).
• Documentation discrepancyGuide and page scope the dataset to US exchanges excluding OTC, but the published basic sample contains two DLP rows with ExchangeCode IRIFX, ISIN prefix IRO3 and blank USIdentifier (non-US listings).
• Documentation discrepancyGuide Table 1 shows a record with Status NEW and a blank FirstTradingDate, although NEW is defined as 'listing date is today or yesterday'.
• Documentation discrepancyGuide does not list ExchangeCode values; the sample uses USNASD, USNYSE, USAMEX, IRIFX.
• Documentation discrepancyGuide intro says the detailed variant includes Shares Outstanding information, but neither the detailed schema (Table 3) nor the detailed sample has a shares-outstanding column (see us-equities-ipo-detailed).
• Documentation discrepancyGuide Table 1 sample rows carry 6-digit SecIds (e.g. 120884) and ModifiedDate values without suffix for some rows; published sample SecIds are 7-digit and every ModifiedDate has an _n suffix. Not a conflict, only an example-format difference.