Account for adjustments
Choose the split or dividend adjustment needed for your research. Check sessions and missing dates before comparing returns.
Data & availability Historical data API
Give your charts
some history.
Retrieve standard open, high, low, close and volume data. Choose an interval and inspect the available candles before building your analysis.
Preview: the endpoint contract below is checked against source. Neutral-domain access and historical depth are pending production validation.
Financial context in your application
A candle belongs to a market.
Keep the series consistent
Select a specific venue and pair. Inspect candle timestamps, gaps and volume before joining historical windows.
Data & availabilityResolve the contract first
Distinguish an individual contract from a continuous series. Test the exact symbol and dates; do not assume continuous-history availability.
Data & availability01 / Start with ten daily candles
A familiar format.
Explicit parameters.
Use the standard OHLCV endpoint for charting and price research. Define your API base and key using the quickstart.
GET /api/price/ohlcv/{symbol}
curl --fail-with-body --get \
"$NAVQUOTE_API_BASE/api/price/ohlcv/NASDAQ:AAPL" \
-H "Authorization: Bearer $API_KEY" \
--data-urlencode "timeframe=D" \
--data-urlencode "range=10" \
--data-urlencode "adjustment=splits"Proposed endpoint · do not treat this as a verified live example.
02 / Shape the request
Choose the time you need.
These are the documented request parameters. Instrument availability still needs checking.
| Parameter | Meaning | Boundary |
|---|---|---|
| timeframe | Bar interval | Minute intervals: 1, 5, 15, 30, 60, 240. Daily, weekly, monthly: D, W, M. Default: 5. |
| strictTo | Preserve a near-live target as an uncached historical query. | Boolean; defaults to false. |
| range | Requested candle count | It is a count, not a duration in days. Availability may limit the result. |
| from | Start timestamp, Unix seconds | Fetch forward from this time. Overrides to if both are supplied. |
| to | End timestamp, Unix seconds | Look backward for the requested number of candles. |
| adjustment | splits or dividends | Default: splits. Verify the applicable adjustment for the instrument. |
Inside a candle
See the field.
Understand the shape.
Schematic rising candle · not market data.time uses Unix seconds; volume is separate.
ARCHIVED CANDLE · ROW EXCERPT
{
"time": 1776769080,
"open": 76761.31,
"close": 76761.2,
"max": 76761.31,
"min": 76754.38,
"volume": 2.21
}One row from an April 2026 repository price sample; the OHLCV contract uses the same response shape.
Parsing, time & reproducibility
The response includes data.current, data.history and instrument information. Parse max and min as the source field names; map them to high and low for your chart library.
Sort and deduplicate by time (Unix seconds). Check ordering, session and returned count; midnight UTC can be outside a trading session. Convert to milliseconds only where required.
Save the symbol, timeframe, adjustment and requested time anchor. A new request can return a different latest, still-forming candle.
Choose the candle semantics
Standard data or a transformed chart?
Similar paths do not always imply identical prices.
Standard OHLCV
Use /api/price/ohlcv/{symbol} for standard Japanese candles. This endpoint explicitly avoids synthetic Heikin-Ashi values.
Chart-type selection
/api/price/{symbol} supports Japanese, HeikinAshi and Range. The contract notes that omitting type selects HeikinAshi; set the type explicitly when using that route.
Price adjustment
splits adjusts for splits; dividends includes splits and cash dividends. Keep the chosen setting consistent across comparisons.
04 / Common questions
History has boundaries.
How far back can I retrieve data?
Historical availability depends on the instrument and interval. A universal earliest date has not been verified. Test the specific symbol and dates you need.
What happens when I provide both from and to?
In the current endpoint contract, from takes precedence and to is ignored. The parameters do not define an arbitrary inclusive date window.
Are these standard or synthetic candles?
The /api/price/ohlcv endpoint explicitly requests standard Japanese candles. Use this endpoint when you need ordinary OHLCV rather than a transformed chart series.
Why might candles be missing?
Market closures, session boundaries or unavailable history may produce gaps. Do not assume every interval has a candle or forward-fill without considering your application’s requirements.
Build something your users can use
See where this API fits.
Choose the experience you want to deliver. Follow a concrete path from the first response to the access your application needs.
Dashboards & watchlists
Quotes, history and updates in one market workspace.
Explore the workflow
Research & screening
From a filtered shortlist to company context and historical exports.
Explore the workflow From the developer guides
Make the next step concrete.
Historical data
Export historical OHLCV to CSV with Python
Fetch standard candles, map max and min to high and low, sort and deduplicate timestamps, and export a reproducible CSV with a separate request manifest.
Historical data
Choose historical candle windows and adjustments
Understand candle counts, Unix-second from and to parameters, split and dividend adjustments, and checks for incomplete historical windows.
Build on a clearer history.
One account for API keys, usage and subscriptions.
Get API Key
Continue to our shared account console.