Volume Weighted Average Price (VWAP)
Category: Trend · Updated November 2026
The TAAPI.IO VWAP API returns the Volume Weighted Average Price as JSON for crypto pairs and US stocks. Send an exchange, symbol, timeframe and anchor to get real-time or historical values, with no candles to download and no calculations to maintain.
What one request returns
- The VWAP (
value): the average price traded since the anchor, weighted by volume. - A choice of anchor, with
anchorPeriod:sessionresets every day at 00:00 UTC andweekevery Monday. Without it, VWAP runs over the last 2,000 candles. - Several anchors and the price at once, with
/bulk: session VWAP, weekly VWAP and the close in one request.
So one call answers two questions: who is in control today, buyers or sellers, and who has been in control this week?
Example: three sessions below VWAP, 12 to 14 November 2026
Request: one /bulk call for BTCUSDT on 1-hour Binance candles, with VWAP anchored to the session and to the week, and the closing price, all with backtrack=1 so the last closed hour. Sent at 22:37 UTC on 14 November.
| Value | Price | Close vs VWAP | Reading |
|---|---|---|---|
| Close, 14 Nov 21:00 | 64,455.78 | — | Last closed hourly candle |
| Session VWAP | 66,321.07 | −2.8% | Below the average price paid today |
| Weekly VWAP | 70,933.97 | −9.1% | Below the average price paid since Monday |
How to interpret this: The session VWAP is the average price everyone paid since midnight UTC, weighted by size. Price below it means that the average buyer of the day is losing money. Over the three sessions from 12 to 14 November, BTC closed above its session VWAP in only 7 of 70 hourly candles. Each session ended below its VWAP: 71,460 against 72,408 on 12 November, 68,314 against 69,153 on 13 November, and 64,456 against 66,321 by 21:00 on 14 November. Seventeen times an hourly high reached the VWAP and the candle still closed below it, which is what intraday traders call a rejection. The weekly VWAP gives the slower view: BTC has not closed above it since 21:00 on 11 November, at 74,390, and is now 9.1% below it. With price below both lines, sellers controlled each day and the week. A trader leaning on VWAP would sell rallies into the line rather than buy dips.
| Session | Hours closed above VWAP | Rejections | Last close | Session VWAP |
|---|---|---|---|---|
| 12 Nov | 1 of 24 | 4 | 71,460.00 | 72,408.22 |
| 13 Nov | 4 of 24 | 6 | 68,314.00 | 69,153.27 |
| 14 Nov, to 21:00 | 2 of 22 | 7 | 64,455.78 | 66,321.07 |
Session values are from the production API on 14 November 2026. For 12 and 13 November they are recalculated from the hourly candles with the same formula, which matches the API to the cent on 14 November. Nothing here is financial advice.
| Spec | Value |
|---|---|
| Endpoint | GET https://v2.taapi.io/indicator/vwap |
| Outputs | VWAP value, timestamp |
| Default settings | No anchor: the last 2,000 candles |
| Markets | Binance, Binance Futures, Bybit, Gate.io, Kraken and US stocks |
| Timeframes | 1m to 1w |
| Delivery | REST, bulk and WebSocket |
Get VWAP with one API call
This request returns VWAP for BTCUSDT on 1-hour Binance candles. Add your API key to run it here.
curl -G https://v2.taapi.io/indicator/vwap \ -H "Authorization: Bearer YOUR_API_KEY" \ --data-urlencode "exchange=binance" \ --data-urlencode "symbol=BTCUSDT" \ --data-urlencode "timeframe=1h"
import requests
resp = requests.get(
'https://v2.taapi.io/indicator/vwap',
headers={'Authorization': 'Bearer YOUR_API_KEY'},
params={'exchange': 'binance', 'symbol': 'BTCUSDT', 'timeframe': '1h'},
)
print(resp.json())const params = new URLSearchParams({"exchange": "binance", "symbol": "BTCUSDT", "timeframe": "1h"});
const res = await fetch(`https://v2.taapi.io/indicator/vwap?${params}`, {
headers: { Authorization: 'Bearer YOUR_API_KEY' },
});
console.log(await res.json());VWAP API response
This response came from the live API on 9 November 2026.
{
"value": [79860.1103966799],
"timestamp": [1794218400]
}| Field | Type | Description |
|---|---|---|
value | number[] | VWAP result |
timestamp | integer[] | Unix time of each candle, in seconds |
VWAP API parameters
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
exchange | string | Yes | — | binance, binancefutures, bybit, gateio, kraken or stocks |
symbol | string | Yes | — | Pair or ticker, e.g. BTCUSDT or AAPL |
timeframe | string | Yes | — | 1m 5m 15m 1h 4h 1d 1w |
anchorPeriod | string | No | null | session resets daily at 00:00 UTC, week every Monday at 00:00 UTC. Without it, VWAP is cumulative over the most recent 2,000 candles. Case-sensitive: any other value is treated as no anchor |
results | integer | No | 1 | Number of values to return, or max |
backtrack | integer | No | 0 | Candles to skip from the most recent |
What is VWAP?
The Volume Weighted Average Price is the average price weighted by traded volume since a starting point. It shows the average price paid by participants over that span, which makes it a common benchmark for judging whether price is high or low relative to actual trading.
VWAP formula
| Output | Calculation |
|---|---|
| Typical price | (high + low + close) ÷ 3 |
| VWAP | Sum of (typical price × volume) ÷ sum of volume, since the anchor |
Each new candle adds its typical price, weighted by its volume. Early in a session there are few candles, so the session VWAP moves quickly. Late in the day it barely moves, and on the weekly anchor even less.
How to read VWAP in your code
| Signal | Meaning | Condition |
|---|---|---|
| Above VWAP | Buyers in profit on average | Close above value |
| Below VWAP | Sellers in control on average | Close below value |
| Reclaim | Intraday bias change | Close crosses back above value |
| Rejection | Rally failed at the average | High reaches value, close stays below |
Limitations: by default this endpoint has no time-based anchor and is cumulative over the most recent 2,000 candles. Set anchorPeriod=session for the daily VWAP most intraday charts show. A session VWAP is based on little data early in the day, and a long-running VWAP responds slowly. Nothing on this page is financial advice.
VWAP anchor periods
VWAP depends on where it starts, so choosing the anchor is the most important decision when using this endpoint.
| anchorPeriod | Behaviour |
|---|---|
session | Resets daily at 00:00 UTC |
week | Resets every Monday at 00:00 UTC |
null (default) | No time anchor: cumulative over the most recent 2,000 candles |
The value is case-sensitive, and any other value is treated as no anchor. Sessions reset at 00:00 UTC, which is not the same as the US stock market open, so a session VWAP on stocks may differ from a chart that resets at 09:30 New York time.
Each value uses the anchor of its own day or week, so results and backtrack return earlier sessions too. VWAP is calculated from the most recent 2,000 candles. On 1m to 15m, the part of a day or week that lies before those candles is added from 15-minute or 1-hour candles, so a weekly VWAP works on 1m as well. It stays within a few thousandths of a percent of a pure 1-minute calculation.
Values are null where the anchor is out of reach, not a VWAP that starts in the wrong place: the oldest day or week in the window on longer timeframes, and the first few candles of the window.
How traders use VWAP
Staying above session VWAP suggests that buyers have control for the day, and staying below it suggests the opposite. Intraday traders watch for reclaims and rejections of the line, and larger traders use it as a benchmark for how well an order was executed.
VWAP is an intraday concept first. For a rolling volume-weighted average with no reset, use VWMA.
Compare price with session VWAP in Python
This fetches the closed price and the daily VWAP together. anchorPeriod=session resets the calculation at 00:00 UTC.
curl -X POST https://v2.taapi.io/bulk \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"constructs": [
{
"id": "btc",
"exchange": "binance",
"symbol": "BTCUSDT",
"timeframe": "1h",
"indicators": [
{
"id": "price",
"indicator": "price",
"backtrack": 1
},
{
"id": "vwap",
"indicator": "vwap",
"anchorPeriod": "session",
"backtrack": 1
}
]
}
]
}'import requests
resp = requests.post(
'https://v2.taapi.io/bulk',
headers={'Authorization': 'Bearer YOUR_API_KEY'},
json={
"constructs": [
{
"id": "btc",
"exchange": "binance",
"symbol": "BTCUSDT",
"timeframe": "1h",
"indicators": [
{
"id": "price",
"indicator": "price",
"backtrack": 1
},
{
"id": "vwap",
"indicator": "vwap",
"anchorPeriod": "session",
"backtrack": 1
}
]
}
]
},
)
data = resp.json()['btc']
price = data['price']['value'][-1]
vwap = data['vwap']['value'][-1]
distance = (price - vwap) / vwap * 100
side = 'above' if price > vwap else 'below'
print(f'Price is {abs(distance):.2f}% {side} session VWAP')Compare price with session and weekly VWAP
The session VWAP shows who controls the day and the weekly VWAP who controls the week. When price is on the same side of both, the picture is clear. One /bulk request returns both anchors and the close. It uses one construct, so it works on every plan.
curl -X POST https://v2.taapi.io/bulk \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"constructs": [
{
"id": "btc_1h",
"exchange": "binance",
"symbol": "BTCUSDT",
"timeframe": "1h",
"indicators": [
{
"id": "session",
"indicator": "vwap",
"anchorPeriod": "session",
"backtrack": 1
},
{
"id": "week",
"indicator": "vwap",
"anchorPeriod": "week",
"backtrack": 1
},
{
"id": "close",
"indicator": "price",
"backtrack": 1
}
]
}
]
}'import requests
payload = {
"constructs": [
{
"id": "btc_1h",
"exchange": "binance",
"symbol": "BTCUSDT",
"timeframe": "1h",
"indicators": [
{
"id": "session",
"indicator": "vwap",
"anchorPeriod": "session",
"backtrack": 1
},
{
"id": "week",
"indicator": "vwap",
"anchorPeriod": "week",
"backtrack": 1
},
{
"id": "close",
"indicator": "price",
"backtrack": 1
}
]
}
]
}
resp = requests.post(
'https://v2.taapi.io/bulk',
headers={'Authorization': 'Bearer YOUR_API_KEY'},
json=payload,
)
data = resp.json()
c = data['btc_1h']
close = c['close']['value'][-1]
session = c['session']['value'][-1]
week = c['week']['value'][-1]
print(f'Close {close:.2f}: {(close / session - 1) * 100:+.1f}% vs session VWAP, '
f'{(close / week - 1) * 100:+.1f}% vs weekly VWAP')
if close < session and close < week:
print('Below both: sellers in control')
elif close > session and close > week:
print('Above both: buyers in control')
else:
print('Between the two: no clear control')The response at 22:37 UTC on 14 November, for the 21:00 candle. The close is below both lines, so the script prints Close 64455.78: -2.8% vs session VWAP, -9.1% vs weekly VWAP Below both: sellers in control
{
"btc_1h": {
"session": {
"value": [66321.06577997572],
"timestamp": [1794690000]
},
"week": {
"value": [70933.97276777482],
"timestamp": [1794690000]
},
"close": {
"value": [64455.78],
"timestamp": [1794690000]
}
}
}Run it once an hour, after each candle closes. Sessions reset at 00:00 UTC, so in the first hours of a day the session VWAP rests on very little volume, and many traders lean on the weekly VWAP until the session has more data.
Get historical VWAP values
Add results to return a series for backtesting or charting. The last element is the most recent candle.
curl -G https://v2.taapi.io/indicator/vwap \ -H "Authorization: Bearer YOUR_API_KEY" \ --data-urlencode "exchange=binance" \ --data-urlencode "symbol=BTCUSDT" \ --data-urlencode "timeframe=1h" \ --data-urlencode "results=100"
Get VWAP for multiple symbols
Combine VWAP with other indicators in one request. Each exchange, symbol and timeframe combination is one construct: Basic allows 1 per request, Pro 3 and Expert 10.
curl -X POST https://v2.taapi.io/bulk \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"constructs": [
{
"id": "btc_1h",
"exchange": "binance",
"symbol": "BTCUSDT",
"timeframe": "1h",
"indicators": [
{
"id": "vwap",
"indicator": "vwap"
},
{
"id": "rsi",
"indicator": "rsi"
}
]
}
]
}'Stream VWAP in real time
Subscribe over WebSocket to receive new values every 5 seconds while the candle is forming. Streaming supports 1m, 5m, 15m and 1h, and uses interval where REST uses timeframe.
{
"type": "subscribe",
"id": "vwap",
"exchange": "binance",
"symbol": "BTCUSDT",
"interval": "1m",
"indicator": "vwap"
}Why VWAP values can differ between platforms
- Anchor: This is the most common cause. The default is not a daily VWAP, so set
anchorPeriodto match your chart. - Session times: Sessions reset at 00:00 UTC, while stock charts often reset at the exchange open.
- Volume data: VWAP uses the volume of the exchange you request.
VWAP API FAQ
What does the VWAP API return?
An array of VWAP values in value, plus a timestamp for each candle.
How do I get the daily VWAP?
Set anchorPeriod=session. It resets at 00:00 UTC every day. Without an anchor, the endpoint averages the most recent 2,000 candles.
When does the session VWAP reset for US stocks?
At 00:00 UTC, like crypto, not at the 09:30 New York open. A stock chart that resets at the open will show a different session VWAP.
Can I use the weekly VWAP on 1-minute candles?
Yes. A week is 10,080 one-minute candles, more than the 2,000 the API calculates from, so the start of the week is added from 15-minute candles. The result stays within a few thousandths of a percent of a pure 1-minute calculation, and every value is anchored at Monday 00:00 UTC.
Is price below VWAP a sell signal?
It means sellers have been in control since the anchor. Intraday traders use it as a bias, and look for rejections at the line, as in the example above, rather than selling every candle below it.
Is the latest VWAP value final?
No. The newest value belongs to the candle still forming and changes with every trade. Add backtrack=1 to read the last closed candle.
Related indicators
- Volume Weighted Moving Average (VWMA): a rolling volume-weighted average with no reset
- Volume Profile: where the volume traded
- Volume Delta: buying against selling volume
- Simple Moving Average: an unweighted average
Build with VWAP on Binance, Bybit or US stocks. Start for free or browse all 262 indicators.