Fathom Levels
Open, high, low, close and midpoint of sessions, weeks and months, plus the POC, value area and VWAP of sessions and weeks.
At a glance
- Identifier
key-levels- Objects received
level- Historical cost
- 1 compute unit per trade
What the indicator shows
- For each session, week and month: open (O), high (H), low (L), midpoint (MP) and, for past periods, close (C).
- For sessions and weeks: POC (P), 70% value area (VH / VL) and VWAP (VW).
- Current period levels move; past period levels are fixed.
How to use it
- The previous period’s extremes and close act as support and resistance: watch how price reacts when it reaches them.
- The previous session’s POC and value area show where the market accepted price. Price settling outside that area is looking for a new value.
- Use
days,weeksandmonthsto choose how many periods to keep on screen. Inconfirmedmode, count the current period:weeks: 2to receive the previous week.
How it is computed
- Publishes the last
dayssessions,weeksweeks andmonthsmonths, current period included.days,weeksandmonthscannot all be 0. - A session runs from 18:00 to 17:00 the next day, New York time; a week, from Sunday 18:00 to Friday 17:00; a month groups the sessions that open during that month: the session of October 1, 2026 opens on September 30 at 18:00, so it counts in September.
- Levels are computed on finished
timeframe-second bars:timeframeonly sets how often they update (and the delay of the period change), not their values. The current period’sHandLtherefore lag the live price by up to one bar. The closeConly exists for past periods. The POC, the value area (70% of the volume, built likesession-profile’s) and the VWAP are only published for sessions and weeks. - A period that starts before the contract’s own history is computed on the product’s front month during that period (on each UTC day, the product’s contract with the most trades), so every count up to its maximum works on the current contract; such a period that is still open is refused with
NOT_COVEREDuntil it ends (a contract whose history has just started). A period inside the contract’s history but before the last rollover is computed on that contract, thinly traded at the time: its levels are not very representative. - Over history, the computation starts early enough before your range to cover the periods you ask for (
origin: periods, seecoveredFromin the estimate). It needs the product’s history over those periods: where it is missing, the query fails withNOT_COVERED.
When it updates
- Levels of the current period are sent in progress (
current: true) and sent again on every finished bar where they change. A level that does not change during your range, such as the open of the current week, therefore only arrives in the snapshot: over history, ask forsnapshot: trueto get every level. - The period change is processed when the first bar of the new session closes (18:05 with
timeframe: 300, 19:00 withtimeframe: 3600, at the next session withtimeframe: 86400): the levels of the period that ends are sent final, with the closeC, if they stay in the window; those leaving it are removed (remove, withfinal: true). - With a count of 1 (
weeks: 1, the generic default, ordays: 1), the only period published is the current one: its levels never become final and are removed when the period changes. Inconfirmedmode you therefore receive no level of that period, only theirremoves (ignore aremovefor an unknownid); useweeks: 2to get the previous week. WithskipCurrent, a count of 1 publishes nothing. - No reset: past periods stay published while they are in the window.
Subscribe
The same params work in real time, on historical data and in exports. Parameters you omit take the defaults of the instrument’s ticker.
{
"t": "subscribe",
"sub": "key-levels",
"instrument": "NQ.front",
"indicator": "key-levels",
"params": {
"days": 2,
"months": 0,
"skipCurrent": false,
"timeframe": 300,
"weeks": 1
},
"mode": "live",
"from": "live"
}Parameters
As soon as a parameter differs from its default on the instrument’s ticker, the subscription counts as a custom configuration. To change a parameter, open a new subscription.
Every ticker currently uses the generic defaults of the Default column. Defaults can be set per ticker and are regularly updated, ticker by ticker: an update changes the results of the subscriptions and queries that rely on them. A subscription whose parameters are all at its instrument’s defaults is not a custom configuration. Only explicit parameters keep a computation identical over time: pass them to keep the same results.
| Parameter | Type | Role | Default | Allowed values | Unit | Description |
|---|---|---|---|---|---|---|
days | integer | Computation | 2 | 0 to 30 | — | Number of sessions published, current session included. days, weeks and months cannot all be 0. |
months | integer | Computation | 0 | 0 to 12 | — | Number of months published, current month included (no POC, value area or VWAP). days, weeks and months cannot all be 0. |
skipCurrent | boolean | Computation | false | true · false | — | Hide the levels of the current period. |
timeframe | integer | Computation | 300 | 1 · 5 · 10 · 15 · 30 · 60 · 120 · 180 · 300 · 600 · 900 · 1800 · 3600 · 7200 · 10800 · 14400 · 86400 | seconds | Bar duration in seconds: from 1 second (1) to 1 day (86400). Bars are counted from the product's session open (18:00 New York time for every current product): 4-hour bars start at 18:00, 22:00, 02:00 and so on, and a 1-day bar covers the whole session. |
weeks | integer | Computation | 1 | 0 to 12 | — | Number of weeks published, current week included. days, weeks and months cannot all be 0. |
Objects received
Each object keeps the same id from one update to the next. Its data is in the data field. Prices are in ticks: Prices and timestamps explains how to convert them.
An object sent in progress arrives with final: false, then again on every change, and each version fully replaces the previous one. Its description says when it ends: most objects end with a last version carrying final: true, and some are removed without one. An object sent final is sent once, with final: true.
Fields and units
Prices are in ticks (Prices and timestamps). Timestamps are nanoseconds since the Unix epoch, sent as strings: parse them as 64-bit integers. The fields below place the objects in time.
| Field | Unit | How to read it |
|---|---|---|
level.id | string · <period>:<key>:<label> | No timestamp: period and key name the session, week or month, label the level. Draw it as a horizontal line at price. |
level sent in progress
Level; in progress during the current period, final once it ends, removed when the period leaves the window. With a count of 1, the level never gets a final version: it is removed when the period changes.
id format: <period>:<key>:<label>.
| Field | Type | Unit | Present | Description |
|---|---|---|---|---|
current | boolean | — | always | true: level of the current period, which can still change. |
key | string | — | always | Session: its closing date YYYY-MM-DD; week: the date of the Sunday it opens; month: YYYY-MM. |
label | string · MP | L | H | O | C | P | VH | VL | VW | — | always | MP midpoint ((high + low) / 2), L low, H high, O open, C close (past periods only), P POC, VH value area high, VL value area low, VW VWAP. P, VH, VL and VW: sessions and weeks only. |
period | string · day | week | month | — | always | Period: session (day), week or month. |
price | number | ticks | always | Price of the level. |
Example messages
Messages as the WebSocket sends them to the subscription above, taken from a real NQ session. Historical data returns the same objects, with the same cursor, without the sub field.
The params of the subscription above are the current NQ ticker defaults, written out in full.
{
"sub": "key-levels",
"cursor": "20720.0.0",
"t": "upsert",
"id": "day:2026-09-24:VH",
"final": false,
"ts": "1790208000058746563",
"data": {
"period": "day",
"key": "2026-09-24",
"label": "VH",
"price": 123177,
"current": true
}
}{
"sub": "key-levels",
"cursor": "20720.0.2",
"t": "upsert",
"id": "week:2026-09-20:VW",
"final": false,
"ts": "1790208000058746563",
"data": {
"period": "week",
"key": "2026-09-20",
"label": "VW",
"price": 122951.4386543437,
"current": true
}
}{
"sub": "key-levels",
"cursor": "20720.451308.9",
"t": "upsert",
"id": "day:2026-09-24:MP",
"final": true,
"ts": "1790287500006398661",
"data": {
"period": "day",
"key": "2026-09-24",
"label": "MP",
"price": 122395,
"current": false
}
}JSON schemas
To validate or type your data: the JSON schemas of the parameters and of data, also available from GET /v1/indicators. The SDKs can generate types from them. Rules that compare two parameters, such as a maximum of at least its minimum, and the two decimals of decimal parameters, are only in the parameter descriptions: the API checks them too.
Parameters schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://fathomcharts.com/schemas/key-levels/params.json",
"type": "object",
"additionalProperties": false,
"properties": {
"days": {
"description": "Number of sessions published, current session included. `days`, `weeks` and `months` cannot all be 0.",
"type": "integer",
"default": 2,
"minimum": 0,
"maximum": 30
},
"months": {
"description": "Number of months published, current month included (no POC, value area or VWAP). `days`, `weeks` and `months` cannot all be 0.",
"type": "integer",
"default": 0,
"minimum": 0,
"maximum": 12
},
"skipCurrent": {
"description": "Hide the levels of the current period.",
"type": "boolean",
"default": false
},
"timeframe": {
"description": "Bar duration in seconds: from 1 second (`1`) to 1 day (`86400`). Bars are counted from the product's session open (18:00 New York time for every current product): 4-hour bars start at 18:00, 22:00, 02:00 and so on, and a 1-day bar covers the whole session.",
"type": "integer",
"default": 300,
"enum": [
1,
5,
10,
15,
30,
60,
120,
180,
300,
600,
900,
1800,
3600,
7200,
10800,
14400,
86400
]
},
"weeks": {
"description": "Number of weeks published, current week included. `days`, `weeks` and `months` cannot all be 0.",
"type": "integer",
"default": 1,
"minimum": 0,
"maximum": 12
}
},
"allOf": [
{
"description": "`days`, `weeks` and `months` cannot all be 0 (nothing would be published)",
"not": {
"properties": {
"days": {
"const": 0
},
"months": {
"const": 0
},
"weeks": {
"const": 0
}
},
"required": [
"days",
"weeks"
]
},
"x-field": "days"
}
]
}data field schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://fathomcharts.com/schemas/key-levels/data.json",
"title": "level",
"type": "object",
"additionalProperties": false,
"properties": {
"current": {
"description": "`true`: level of the current period, which can still change.",
"type": "boolean"
},
"key": {
"description": "Session: its closing date `YYYY-MM-DD`; week: the date of the Sunday it opens; month: `YYYY-MM`.",
"type": "string",
"pattern": "^[0-9]{4}-[0-9]{2}(-[0-9]{2})?$"
},
"label": {
"description": "`MP` midpoint ((high + low) / 2), `L` low, `H` high, `O` open, `C` close (past periods only), `P` POC, `VH` value area high, `VL` value area low, `VW` VWAP. `P`, `VH`, `VL` and `VW`: sessions and weeks only.",
"type": "string",
"enum": [
"MP",
"L",
"H",
"O",
"C",
"P",
"VH",
"VL",
"VW"
]
},
"period": {
"description": "Period: session (`day`), week or month.",
"type": "string",
"enum": [
"day",
"week",
"month"
]
},
"price": {
"description": "Price of the level.",
"type": "number"
}
},
"required": [
"period",
"key",
"label",
"price",
"current"
]
}