Coverage
What you get
| Item | Detail |
|---|---|
| Product code | FUT-TICK |
| Coverage | US futures by contract month, starting with CME Group products |
| Granularity | Every trade and top-of-book quote; nanosecond timestamps where the venue provides them |
| History | Pro: last 30 days of trades. Business: full history of trades and L1 quotes |
| Delivery | REST, real-time stream on Business, CSV files per root per year |
| Update speed | 10-minute delayed on Pro, real time on Business |
Order-flow traders read futures through the tape: who's lifting offers, who's hitting bids, how size shows up at a level. That needs aggressor_side on every trade. We carry it straight from the exchange feed rather than guessing from price changes.
Schema
Schema
| Field | Type | Required | Description |
|---|---|---|---|
symbol |
string | yes | e.g. ESZ6 |
event_type |
string | yes | trade or quote |
timestamp |
string | yes | Exchange event time, ISO 8601 UTC, nanoseconds where the venue provides them |
receive_timestamp |
string | optional | Our capture time |
price |
number | trade | Trade price |
size |
number | trade | Contracts |
aggressor_side |
string | trade | buy, sell or unknown |
bid_price, bid_size, ask_price, ask_size |
number | quote | Best bid and offer |
trade_id |
string | optional | Exchange trade ID |
sequence |
number | optional | Venue sequence number |
conditions |
array of string | optional | Sale conditions |
session |
string | optional | regular or extended |
is_block |
boolean | optional | Block trade flag |
is_corrected |
boolean | optional | Trade later corrected or cancelled |
Example record:
{
"symbol": "ESZ6",
"event_type": "trade",
"timestamp": "2026-11-18T15:30:00.012345678Z",
"receive_timestamp": "2026-11-18T15:30:00.012401223Z",
"price": 6741.75,
"size": 12,
"aggressor_side": "buy",
"sequence": 184420917,
"is_block": false,
"is_corrected": false
}
Sample data
Sample data
No free futures tick sample yet. CME historical redistribution terms come with the distributor licence we're still arranging. A sample file is available on request: one root, one session.
Use cases
Use cases
Cumulative delta. Add size for aggressor_side = buy and subtract it for sell. Running that through the session gives you the delta line footprint charts are built on.
Footprint and volume profile. Group trades by price and side within each bar to see where volume traded and which side was aggressive at each level.
Slippage studies. Join quotes to trades by timestamp and measure how far market orders moved through the book. On ES, one tick is $12.50 per contract, so a tick of slippage per side adds up fast.
Cleaning out bad prints. Filter is_corrected = true before any study. Corrected and cancelled trades still appear in raw feeds and will distort highs, lows and volume.
Code
Code examples
Example: ES trades for the first minute of the cash session.
curl "https://api.marketdata.co/v1/futures/ticks?symbol=ESZ6&event_type=trade&start=2026-11-18T14:30:00Z&end=2026-11-18T14:31:00Z" \
-H "Authorization: Bearer $MARKETDATA_API_KEY"
Example: Python, cumulative delta through a session.
import os
import requests
import pandas as pd
resp = requests.get(
"https://api.marketdata.co/v1/futures/ticks",
params={"symbol": "ESZ6", "event_type": "trade",
"start": "2026-11-18T14:30:00Z", "end": "2026-11-18T21:00:00Z"},
headers={"Authorization": f"Bearer {os.environ['MARKETDATA_API_KEY']}"},
)
resp.raise_for_status()
t = pd.DataFrame(resp.json()["results"])
t = t[t["is_corrected"] == False]
sign = t["aggressor_side"].map({"buy": 1, "sell": -1}).fillna(0)
t["delta"] = (t["size"] * sign).cumsum()
print(t[["timestamp", "price", "delta"]].tail())
Pricing
Pricing
| Plan | Futures ticks |
|---|---|
| Pro, $79/mo | Last 30 days of trades, 10 minutes delayed |
| Business, $249/mo | Trades and L1 quotes, full history, real-time stream, CME fees passed through |
Files are planned at $49 per root per year for trades (all expiries), or $99 per root per year with L1 quotes, with no minimum order. Prices are early access and may change.
Among the vendors we studied, futures tick subscriptions run from $133 to $1,500 a month, and one-off files cost $500 to $3,750, often with minimum orders.
Side by side
How we compare
11 of the 50 providers we studied sell futures ticks. The history sellers tend to set minimum orders or monthly minimums that make buying one product for one year expensive. We sell a single root-year at $49 with no minimum and let you keep the file, and the trade record uses the same symbol and UTC timestamps as our futures bars.
FAQ
Frequently asked questions
How is aggressor side determined?
It comes from the exchange: CME marks which side of each trade was the incoming order. Where the venue doesn't provide it, the field is unknown rather than inferred.
What timestamp precision do you have?
Nanoseconds where the venue provides them, as with CME's modern feed. Older history may be coarser. receive_timestamp is our capture time.
Are quotes full depth?
No, top of book only (L1): best bid, best ask and their sizes. Market depth is a separate product.
How large is a year of ES ticks?
Large. ES is one of the busiest futures contracts there is, so check your disk space before you buy several years of it.
Which session do overnight trades belong to?
Ticks carry UTC timestamps. To group by CME trading day, use the session rules in our contract specs: the session opens the evening before.
Keep reading
Related
- Asset hub: Futures
- Contracts: ES, NQ, YM, RTY, CL, GC
- Docs: API reference: futures
- Learn: Tick data vs bar data