Early access is open. Free sample datasets are live now. Download a sample

Data product · Early access

Opening and Closing Auction Imbalance Data

How many shares are left unmatched going into the open or the close, on which side, and at what price the auction looks set to cross.

Imbalance data is planned for later in our roadmap and isn't live. It needs its own exchange licence, so we're collecting early access reservations first to decide when to sign it.

Coverage

What you get

Item Detail
Product code STK-AUCTION-IMBALANCE
Coverage US listed stocks in exchange opening, closing, halt-reopen and IPO auctions
Granularity Every imbalance message the venue publishes
History Monthly history files planned once venue terms are known
Delivery REST and WebSocket on Business; history files later
Update speed As published by the exchange during the auction window

The closing auction is the biggest single print of the day for many large caps. Index funds and anyone benchmarked to the close trade there. Before it runs, the exchange publishes how many shares are paired and how many are left over. A big buy imbalance ten minutes before the bell tells you someone needs shares at the close, and the market has a few minutes to offset it.

Schema

Schema

Field Type Required Description
symbol string yes Our ticker
timestamp string yes Message time, ISO 8601 UTC
exchange string yes Auction venue
auction_type string yes open, close, halt_reopen, ipo
auction_time string yes Scheduled auction time
reference_price number yes Reference price
indicative_match_price number optional Price where most shares would cross
paired_quantity number yes Shares matched at reference
imbalance_quantity number yes Unmatched shares
imbalance_side string yes buy, sell, none
market_imbalance_quantity number optional Market-order imbalance
upper_collar / lower_collar number optional Price collars

Example record:

{
  "symbol": "JPM",
  "timestamp": "2026-11-18T20:50:00.000Z",
  "exchange": "XNYS",
  "auction_type": "close",
  "auction_time": "2026-11-18T21:00:00Z",
  "reference_price": 244.18,
  "indicative_match_price": 244.22,
  "paired_quantity": 1840200,
  "imbalance_quantity": 312500,
  "imbalance_side": "buy",
  "upper_collar": 246.62,
  "lower_collar": 241.74
}

The prices and sizes are an example. Note the times: in November, US markets are on standard time, so the 4 p.m. Eastern close is 21:00Z.

Sample data

Sample data

No free imbalance sample exists yet. Imbalance feeds are licensed by the exchange that runs the auction, and that licence comes before any file we could hand out. Ask for the symbols and dates you want, and we'll send a sample when terms allow.

Use cases

Use cases

Fade or follow the close. Track imbalance_quantity and imbalance_side from the first message to the last. Some imbalances shrink as offsetting orders arrive; others grow. Test whether the final print lands above or below indicative_match_price in each case.

Index rebalance days. On quarterly index rebalances the closing imbalances in added or removed names can be many times their normal size. Rank by imbalance_quantity / paired_quantity to find the stretched ones.

Opening auction gaps. With auction_type set to open, compare indicative_match_price against the prior close to size the gap before 9:30. Pre-market quotes are thin; the auction book is where the real size sits.

Halt reopen pricing. After a volatility halt, halt_reopen messages show where the stock is likely to reopen and whether upper_collar or lower_collar is limiting it.

Code

Code examples

Example: closing imbalance messages for one stock with curl.

curl "https://api.marketdata.co/v1/stocks/auction-imbalance?symbol=JPM&auction_type=close&date=2026-11-18" \
  -H "Authorization: Bearer $MARKETDATA_API_KEY"

Example: Python, how the imbalance moved in the last ten minutes.

import os
import requests
import pandas as pd

resp = requests.get(
    "https://api.marketdata.co/v1/stocks/auction-imbalance",
    params={"symbol": "JPM", "auction_type": "close", "date": "2026-11-18"},
    headers={"Authorization": f"Bearer {os.environ['MARKETDATA_API_KEY']}"},
)
resp.raise_for_status()
imb = pd.DataFrame(resp.json()["results"])
imb["timestamp"] = pd.to_datetime(imb["timestamp"])
imb["signed_imbalance"] = imb["imbalance_quantity"].where(
    imb["imbalance_side"] == "buy", -imb["imbalance_quantity"]
)
print(imb.set_index("timestamp")[["signed_imbalance", "indicative_match_price"]])

Pricing

Pricing

Plan Auction imbalance
Business, $249/mo Live and recent imbalance messages as an add-on, exchange fees passed through at cost

Historical imbalance files will be priced per month once the venue terms are known. Prices are early access and may change.

Vendors we looked at charge $49 to $199 a month for imbalance data, based on 2 published prices. Live use usually adds a separate exchange fee.

Side by side

How we compare

Just 2 of the 50 providers we studied sell auction imbalance data. We plan to carry open, close, halt-reopen and IPO auctions in one table with one set of field names, so you don't need separate parsers per venue. The exchange fee will show as its own line, and history files will be yours to keep.

FAQ

Frequently asked questions

Which auctions are covered?

The schema handles open, close, halt_reopen and ipo. Which venues we carry at launch depends on the licences we sign first.

How often do imbalance messages arrive?

As often as the exchange publishes them. During the closing window that can be every few seconds per symbol on the busiest names.

What time zone are timestamps in?

UTC. Both timestamp and auction_time use ISO 8601, so check daylight saving before converting to Eastern.

Is this real-time or delayed?

The Business add-on is planned as live data. Live imbalance feeds carry an exchange fee, which we'll pass through at cost.

Are prices adjusted for splits?

No. Imbalance messages are a record of what the exchange said at the time, so reference_price stays as published.

What formats will history come in?

JSON from the API, with monthly CSV and Parquet files planned.

Keep reading