Why does volume return as a FLOAT value from the Aggregates Endpoint? | Polygon

Knowledge Base/Why does volume return as a FLOAT value from the Aggregates Endpoint?

Why does volume return as a FLOAT value from the Aggregates Endpoint?

Stocks

FAQ

These decimal values are entirely normal when requesting adjusted data for stocks that have split.

When requesting historical Aggregate OHLCV (Open, High, Low, Close, Volume) data, you might occasionally encounter a volume value represented as a decimal instead of a whole number.

This occurrence is attributed to the 'adjusted' parameter within the Aggregates Endpoint. When the 'adjusted' parameter is set to 'true,' the OHLCV values are modified to reflect stock splits. This adjustment ensures that the data provides a more accurate historical representation, accounting for changes that have occurred over time. Therefore, seeing decimal values in volume data under these circumstances is both normal and expected

Was this article helpful?

Modernizing Wall St.

Reimagining financial market data for the 21st century.

Schedule a demo

Talk with our market data experts

Recommended

Can't find the answer you're looking for? Contact our team.

Title
Are all Indices available through the basic subscription tier?
Data Coverage Category
Data Coverage
Indices Category
Indices
Description
No, certain indices are only available through paid subscription tiers.
Title
Does Polygon offer dark pool data?
Data Coverage Category
Data Coverage
Stocks Category
Stocks
Description
Yes, we provide dark pool data. If a trade comes through with an exchange ID of 4 (exchange:4) and also has an attached “trf_id” field, it came from a dark pool.
Title
Does Polygon offer pre-market and after-hours data?
FAQ Category
FAQ
Stocks Category
Stocks
Description
Yes, we provide data for every trade that occurs, including during pre-market and after-hours. Our tick-level market data streams during these extended hours as well.