Lockup Feed¶
General Information¶
The VerityData Lockup database includes lockup details for all IPOs and SPACs that merged after Jan 1, 2021. The feed contains fields related to conditional dates used to determine the release dates for certain lockups and fields for the details of all early release provisions.
Additional Point-in-time notes¶
- Updates to company-related fields (ticker, cusip, company_name, etc.) do not trigger updates in the feed, only updates to transaction specific fields trigger an update.
- Company-related fields are as of the asof field, not the original insert, meaning values such as ticker, cusip, etc. may change when comparing an initial insert to a later update for the same txnid. (e.g. a transaction with ticker "FOO" at insert will show as "BAR" on subsequent updates if the company's ticker changed between the two asof dates. The original insert will always show "FOO", however.)
- Not all fields are available with point-in-time accuracy. Please see the Data Dictionary for more information.
Notes on Nested Fields¶
Some of the fields, labelled [JSON Data] below contain structured data in the JSON file format. This is a commonly-used format for structured data which can vary from instance to instance. Nearly all modern software frameworks have tools for parsing this data; it is also reasonably human-readable.
JSON data is inherently variable; do not assume specific entries, numbers of elements, or other properties of the data without verifying those assumptions. The JSON field names are chosen to be somewhat self-explanatory, but can sometimes be terse. If you have difficulty parsing or interpreting the JSON data, please contact your Verity support for assistance.
Data Dictionaries¶
MAIN FIELD | JSON Subfield | Description |
---|---|---|
ticker | Ticker of the company. | |
cid | VerityData's unique company id. PIT cusips may differ. CID should be used for consistency. Cid Should only be NULL in cases where the record was already in the feed when the cid value was removed. Such records will have edit_action = D. | |
eid | VerityData's unique entity id associated with the cid. | |
cusip | CUSIP identifier of the company. | |
company_name | Name of the company. | |
sector | Sector of the company. | |
class_status | Denotes the status of the company at the time of the last_update. Useful to exclude posthumous edits to inactive companies from your modeling / testing. | |
mcap | [Not Point In Time Data] Market Cap of the company as of the filing date. | |
lockup_id | Unique ID provided by VerityData for the Lockup. | |
spac_or_ipo | Tag designating the associated corporate action. | |
formtype | Form-type of the source filing. | |
disclosure_date | The date the source was filed with the SEC (or PR was published). | |
base_provision_id | Unique ID provided by VerityData for the Base Provision. | |
base_provision_shares_type | Shares eligible for release disclosure type: “Shares” or “Percentage” . | |
base_provision_status | "Released" or "Locked-up". | |
base_provision_shares | Shares eligible for release. NULL for base_provision_shares_type "Percentage". | |
base_provision_share_percentage | Percent of shares eligible for release. NULL for base_provision_shares_type "Shares". | |
base_provision_release_date_method | "All" or "Earlier Of". | |
base_provision_release_date | Base provision release date. | |
base_provision_extension_date | Base provision extension date. | |
base_provision_locked_up_persons | VerityData classifications: “Current Employees and consultants”, “Directors”, “Officers”, “Concurrent”, “Sponsor”, “Target”, “All” and “Other”. | |
base_provision_locked_up_persons_notes | Explanation when locked-up Persons doesn’t fall into our classifications. | |
base_provision_lockup_text | Description directly from the filing. | |
base_provision_additional_notes | Catch all for other descriptive features. | |
base_provision_shares_remaining | Shares remaining to be released. | |
base_provision_resolved | True or False | |
base_provision_percentage_remaining | Percentage remaining to be released. NULL for base_provision_shares_type "Shares". | |
conditional_dates | [JSON Data] Nested fields for base provision conditional dates. Conditional dates are used in the determination of Release dates for certain lockups. A lockup may have more than one conditional date. | |
base_provision_cond_id | Unique ID provided by VerityData for the Conditional Date. | |
base_provision_cond_date | Base provision conditional date. | |
base_provision_cond_type | "Days after", "Earnings Date", or "Other". | |
base_provision_cond_status | "Confirmed" or "Estimated". Estimated is used in cases where earnings dates are not finalized. | |
base_provision_cond_date_text | Description from the filing. | |
base_provision_cond_date_modifier | Days added to the Conditional Date to make it equal the Release Date. | |
base_provision_cond_estimated_quarter | Estimated quarter for earnings date conditions. Note that base_provision_cond_type = "Days after" may reference earnings dates. | |
base_provision_cond_days_after_prospectus | Number of days after prospectus. | |
erp_data | [JSON Data] Nested fields for Early Release Provisions. A lockup may have more than one ERP. | |
erp_id | Unique ID provided by VerityData for the Early Release Provision. | |
erp_id | Price criteria for early release. | |
erp_shares | Shares eligible for early release under the provision. | |
erp_status | "Released" or "Locked-up". | |
erp_end_date | End date of the early release period. | |
erp_max_days | Max days for the minimum number of days to be achieved in. | |
erp_min_days | Minimum number of days at the ERP price to release. | |
erp_resolved | True or False | |
erp_days_type | Type of days to count: "Trading" or "Calendar". | |
erp_price_type | Type of price used to determine early release: "Avg Price", "Close", or "VWAP". | |
erp_start_date | Start date of the early release period. | |
erp_lockup_text | Description directly from the filing. | |
erp_shares_type | Shares eligible for release disclosure type: “Shares” or “Percentage” . | |
erp_range_status | "Confirmed" or "Estimated" - date is not confirmed, i.e. prelim earnings date. | |
erp_release_date | Early release provision release date. | |
erp_additional_notes | Catch all for other descriptive features. | |
erp_shares_remaining | Shares remaining to be released. | |
erp_conditional_dates | [JSON Data] A further nested array of information about one or more erp_conditional_dates. To keep this table readable, these fields are described in the table below. | |
erp_end_date_modifier | Days added to the End Date to make it equal the End date of the early release period. | |
erp_locked_up_persons | VerityData classifications: “Current Employees and consultants”, “Directors”, “Officers”, “Concurrent”, “Sponsor”, “Target”, “All” and “Other”. | |
erp_release_date_method | "All" or "Earlier Of". | |
erp_is_conditional_start | True if the start date is dependent on other factors. | |
erp_locked_up_persons_notes | Explanation when locked-up Persons doesn’t fall into our classifications. | |
erp_share_percentage_remaining | Percentage remaining to be released. NULL for base_provision_shares_type "Shares". | |
unique_id | This is the unique identifier of each row within the Lockup tables. If an edit comes for a specific RowID, you can replace the existing RowID in your table with the latest information. | |
last_update | The date of the last update for this entry. | |
edit_action | "U" for update, "D" for delete and "I" for new insert. | |
asof | The date the record appeared in the feed. |
erp_conditional_dates Subfields¶
These fields are children of erp_conditional_dates (which is itself a JSON field within the erp_data element), as a JSON array. For example:
"erp_conditional_dates": [
{"erp_cond_id": 86,
"erp_cond_date": "2022-12-31",
"erp_cond_type": "Days after",
"erp_cond_status": "Confirmed",
"erp_cond_date_text": "Commencing at least 150 days after the Closing",
"erp_cond_date_modifier": 0,
"erp_cond_estimated_quarter": "",
"erp_cond_days_after_prospectus": 150}
]
Heading | Description |
---|---|
erp_cond_id | Unique ID provided by VerityData for the ERP Conditional Date. |
erp_cond_date | Early Release provision conditional date. |
erp_cond_type | Days after, Earnings Date, Other. |
erp_cond_status | Confirmed or Estimated. |
erp_cond_date_text | Description from the filing. |
erp_cond_date_modifier | Days added to the Conditional Date to make it equal the Early Release Date. |
erp_cond_estimated_quarter | Estimated quarter for Earnings Date conditions. |
erp_cond_days_after_prospectus | Days after prospectus for Days after conditions. |