Products
Docs
Company
Symbol | Expiration UTC | Underlying | Last price | Volume | Open interest |
|---|---|---|---|---|---|
BGI EMZ0030_OMPA0000034000122030 | 2030-12-20 | - | 0 | 0 | |
BGI EMZ0029_OMPA0000034000122129 | 2029-12-21 | - | 0 | 0 | |
BGI EMZ0029_OMPA0000030000122129 | 2029-12-21 | - | 0 | 0 | |
BGI EMZ0028_OMCA0000030000121528 | 2028-12-15 | - | 0 | 0 | |
BGI EMZ0027_OMPA0000030000121727 | 2027-12-17 | - | 0 | 0 |
The capture-server-received timestamp expressed as the number of nanoseconds since the UNIX epoch.
The order quantity.
The matching-engine-received timestamp expressed as the number of nanoseconds since the UNIX epoch.
The channel ID assigned by Databento as an incrementing integer starting at zero.
The record type. Each schema corresponds with a single rtype value.
The order ID assigned at the venue.
The publisher ID assigned by Databento, which denotes dataset and venue.
A bit field indicating event end, message characteristics, and data quality.
The numeric instrument ID.
The matching-engine-sending timestamp expressed as the number of nanoseconds before ts_recv.
The event action. Can be Add, Cancel, Modify, cleaR book, Trade, Fill, or None.
The message sequence number assigned at the venue.
The side that initiates the event. Can be Ask for a sell order (or sell aggressor in a trade), Bid for a buy order (or buy aggressor in a trade), or None where no side is specified by the original source.
The requested symbol for the instrument.
The order price expressed as a signed integer where every 1 unit corresponds to 1e-9, i.e. 1/1,000,000,000 or 0.000000001.
Need to see more data for Berkeley Group Holdings (Std Options/Amer/Dlv)? You can extract historical data and save it as a DBN, CSV, JSON, or Parquet file. Read our API guide ->
UTC