Timeseries Data
OHLCV Candles
/v2/timeseries/candlesReturns OHLCV candlestick data at the specified resolution. Prices are as quoted, not adjusted for distributions, so the change over a period is the price return. The return metrics of /v2/etfs/metrics and /v2/funds/metrics are total returns: for a distributing share class they exceed that change by the reinvested distributions, for an accumulating share class the income is already in the price and both agree. For an ISIN request /v2/etfs/metrics computes its returns on the listing, and in the currency, that this endpoint answers from. For an ISIN with no listing price in the requested window, daily, weekly and monthly candles come from its NAV instead, with source set to nav. Intraday resolutions never fall back to NAV.
Access depends on your account agreement and API-key permissions.
Authentication
Send your API key in the x-api-key header on every request to https://api.bavest.co. The samples read it from the BAVEST_API_KEY environment variable. Get an API key (free trial) · Authentication guide.
Parameters
Required: one of symbol, isin, for example symbol=AAPL.
- stringquery · one of symbol, isin
Stock ticker symbol (e.g.,
AAPL,MSFT,GOOGL). Provide exactly one of symbol or isin.Example
AAPL - stringquery · one of symbol, isin
ISIN code (e.g.,
US0378331005). Provide exactly one of symbol or isin. Clear the symbol example before using an ISIN. - stringquery · no
Candle resolution
One of:
DDaily bars
WWeekly bars
MMonthly bars
Default
D - string (date)query · yes
Start date (YYYY-MM-DD). Required for candle data.
Example
2026-09-01 - string (date)query · yes
End date (YYYY-MM-DD). Required for candle data.
Example
2026-09-30 - stringquery · no
Target currency (ISO 4217). When provided, prices are converted from the native currency using the latest FX rate. Example when explicitly filtering:
USD. - stringquery · no
Optional listing venue to pin the response to a specific exchange. Accepts the venue's ISO 10383 MIC (
XWBOfor the Wiener Börse,XNASfor NASDAQ) as well as our own short code for the same venue (VIE,NASDAQ,MUN); both spellings resolve to the same listings. Segment MICs are not resolved yet. For a venue whose segments carry their own MIC (the Wiener Börse'sWBAH,WBGF,WBDM), pin the operating MICXWBOor the short codeVIE. Honored forisinANDsymbolrequests. When omitted, the listing named by the symbol answers (our symbols are RICs:EBS.VIis the Vienna listing,EBO.DEthe XETRA one); for anisinrequest, or for a named listing that has no data in the requested window, the security's canonical listing answers. Where the response has anexchangefield, it always names the venue that actually answered. A venue the instrument is not listed on is never silently replaced by another listing./v2/timeseries/candlesrejects it with 400 and names the venues the instrument does have, while/v2/timeseries/eodand/v2/timeseries/quotereturn no data.
Response 200
Successful response · application/json
data- object
4 fields in data
candles- array of EquityCandle
OHLCV candle bars
6 fields in candles
open- number (double)
- required
Opening price
Example:
225.05high- number (double)
- required
High price
Example:
225.6low- number (double)
- required
Low price
Example:
220.75close- number (double)
- required
Closing price
Example:
222.75volume- integer
- required
Trading volume
Example:
3214728timestamp- integer (int64)
- required
Candle start (Unix epoch)
Example:
1773352065
currency- string
Price currency (ISO 4217), always a MAJOR unit. A venue quoting in a minor unit (LSE in pence) is restated in its major unit, so this never returns GBp, ZAc or KWF and the client needs no scaling.
exchange- string
The venue that actually answered, as our short code. It equals the pinned or named listing's venue, except when that listing has no bars in the requested window and the security's canonical listing answered instead. Read this field to confirm which venue supplied the data.
NAVwhensourceisnav; pinningexchange=NAVrequests that series.source- string
What the prices are.
listingis an exchange listing's prices.navis the security's net asset value (NAV), in either of two cases. The fund's NAV history is served as its own series, reported with exchangeNAV. Or no listing of the ISIN has a price in the requested window and the stored NAV is served instead. The second case is mostly mutual funds that do not trade on an exchange. A NAV series has the same shape as a listing's, and each bar has open, high, low and close equal to that day's NAV and volume 0. Listing prices always take precedence over the stored NAV, and the two are never mixed in one response.One of
listing,nav.Example:
listing
meta- ResponseMeta
Response metadata, including server-side processing time and resolved request parameters. Successful and error responses use the same metadata shape.
2 fields in meta
time- integer
Server-side processing time in milliseconds
Example:
17parameters- object
Echo of the request parameters the endpoint resolved
Errors
- 400 Invalid request parameters. Returned when required query parameters are missing, have invalid types, or violate constraints (e.g., providing both symbol and isin when they are mutually exclusive).
- 401 Missing or invalid API key.
- 404 Resource not found.
- 429 Rate limit exceeded. Retry after the `Retry-After` header interval.
- 500 An unexpected error occurred on the server. If the issue persists, contact support with the X-Request-Id header value.
- 502 Upstream data provider returned an error or is temporarily unavailable. Retry after a short delay.
- 504 The request timed out waiting for a response from the upstream data provider. This may occur for complex queries or during peak load.
- default An unexpected error occurred on the server. If the issue persists, contact support with the X-Request-Id header value.
403from the gateway: the API key is invalid or switched off.429with messageLimit Exceeded: the monthly quota of the key is used up. WithToo Many Requests: the key is throttled, or this route is not in the key's plan. Wait forRetry-Afterwhen it is sent.

