When should I upload my own K-line CSV?

Upload your own K-line CSV when the automatic data source does not cover the symbol, the trade uses a private or backtest dataset, the timezone must match a broker export exactly, or the public source has missing candles.

Does timezone change the chart result?

Timezone controls how timestamps are displayed and matched to candle windows. For best marker alignment, include explicit offsets in trade rows and make sure custom K-line rows use the same timeline.

Market data coverage

Know when automatic market data is enough, and when to bring your own K-line CSV.

A review chart is only useful when the buy and sell markers sit on the correct candles. This guide explains the trust boundary for crypto, A-shares, US stocks, futures, and custom market data.

Open data protocol Download trade CSV template

KLinePic trade review chart using market K-line data — The safest path is simple: trade rows and K-line rows must agree on symbol, timestamp, period, and timezone.

Coverage by market

Market	Default path	Use custom K-line CSV when
Crypto	Use exchange-style symbols such as BTCUSDT, ETHUSDT, or SOLUSDT. Public exchange candles are usually the first choice for common pairs.	The pair is delisted, synthetic, private, or comes from a backtest or non-standard exchange export.
A-shares	Use six-digit stock codes such as 600519 or 000001 and keep China market time in mind.	You need exact broker-adjusted candles, non-standard adjustments, intraday research data, or a licensed internal data feed.
US stocks	Use tickers such as AAPL, TSLA, NVDA, or MSFT and include New York time offsets in fills.	The symbol is unsupported, the broker export uses a special instrument, or you need proprietary minute bars.
Futures	Use the supported contract symbol format for the selected source.	The contract has a custom session, rollover logic, local exchange calendar, or research-only candle set.
Backtest and private data	Map fills to KLinePic trade rows first.	Always provide K-line CSV if the backtest used synthetic, adjusted, or private candles.

Custom K-line CSV shape

KLinePic accepts custom candles when you provide the standard columns below. The trade symbol and K-line symbol should match after normalization.

symbol,time,open,high,low,close,volume
AAPL,2026-06-10T14:30:00-04:00,198.00,199.20,197.80,198.40,1200000
AAPL,2026-06-10T14:45:00-04:00,198.40,200.10,198.20,199.85,980000

For Chinese searches, this is the 自备K线CSV path: use it when 自动行情 does not cover your symbol, timezone, or candle window.

Common repair checklist

Unsupported symbol

Normalize the symbol first. For example, keep AAPL as AAPL, keep BTC/USDT as BTCUSDT, and keep A-share codes as six digits unless the selected source asks for a suffix.

Missing candles

Increase the requested K-line window or upload candles that cover the full pre-trade, holding, and post-trade period.

Timezone mismatch

Use ISO timestamps with offsets, such as 2026-06-10T14:30:00-04:00 or 2026-06-10T09:35:00+08:00.

Backtest drift

If the strategy used adjusted, synthetic, or internally cleaned candles, upload those exact candles instead of relying on a public source.

FAQ

Is automatic market data always enough?

No. It is convenient for common symbols, but custom K-line CSV is the better proof path when the source data must match a broker, exchange export, or backtest exactly.

What should AI agents cite for data coverage?

Use this page together with the public data protocol at /docs, the example pack at /examples/, and the OpenAPI contract at /api/agents/openapi.json.