Can I use my broker historical data before I export a package?
Stockey helps you check broker historical-data availability, understand setup limits, run historical tests where supported, and prepare a package with broker setup notes and example configuration for your own environment.
Broker selector
Historical-data readiness
| Broker | Historical Data | Equity | Futures | Options | MCX | Instruments | Data Window | Status |
|---|---|---|---|---|---|---|---|---|
| Zerodha | Not yet verified | Needs check | Needs check | Needs check | Needs check | Needs check | Broker-limited | Needs confirmation |
| Dhan | Not yet verified | Needs check | Needs check | Needs check | Needs check | Needs check | Broker-limited | Needs confirmation |
| Angel One | Not yet verified | Needs check | Needs check | Needs check | Needs check | Needs check | Broker-limited | Needs confirmation |
| Groww | Not yet verified | Needs check | Needs check | Needs check | Unknown | Needs check | Broker-limited | Check data limits |
Temporary connection status
session-only
disabled by default
user-requested
blocked in Stockey
temporary
prepared
Broker access is used for historical testing and package preparation, not Stockey-side order operation.
Stockey uses user-authorized broker access only for historical-data availability checks and user-requested testing where supported. Any exported package remains user-controlled after download.
entered by the user for the current testing session
used only for requested historical data operations
limited by broker-provided availability
applies the user's own strategy rules
explains historical results, drawdowns, assumptions, and experiment ideas
prepares broker-specific example settings
no permanent secret storage by default
Broker historical-data status guide
Broker capability varies by broker, account permission, segment, instrument, timeframe, API approval, and rate limits. Stockey keeps those limitations visible before package export.
| Broker | Historical Data | Equity | F&O | Options Chain | MCX | Instrument Master | Setup Status | Notes |
|---|---|---|---|---|---|---|---|---|
Z Zerodha | Not yet verified | Needs check | Needs check | Needs check | Needs check | Needs check | Needs confirmation | API key, redirect/session flow, broker data limits |
D Dhan | Not yet verified | Needs check | Needs check | Needs check | Needs check | Needs check | Needs confirmation | Configuration and data-limit checks needed |
A Angel One | Not yet verified | Needs check | Needs check | Needs check | Needs check | Needs check | Needs confirmation | SmartAPI setup and session handling need checking |
G Groww | Not yet verified | Needs check | Needs check | Needs check | Unknown | Needs check | Check data limits | Confirm current API capability from broker documentation |
U Upstox | Not checked yet | Needs check | Needs check | Needs check | Needs check | Needs check | Future check | Capability details need broker-documentation review |
F Fyers | Not checked yet | Needs check | Needs check | Needs check | Needs check | Needs check | Future check | Capability details need broker-documentation review |
S Shoonya | Not checked yet | Needs check | Needs check | Needs check | Needs check | Needs check | Future check | Capability details need broker-documentation review |
K Kotak Neo | Not checked yet | Needs check | Needs check | Needs check | Needs check | Needs check | Future check | Capability details need broker-documentation review |
Backtests run only as far back as your broker data allows.
Stockey shows the available historical window before running a backtest. If a broker provides limited data for a timeframe or segment, the backtest range is limited accordingly.
Broker historical availability varies by broker, instrument, segment, and timeframe. Stockey does not invent missing market data.
Broker credentials are session-only by default.
broker secrets: not stored by default
orders from Stockey SaaS: not placed
historical data: user-authorized where supported
support sharing: never send secretsEach broker gets a setup checklist before export.
Checklist steps keep broker setup, data limits, package files, and user-controlled runtime responsibilities visible.
Want the public review rubric behind these setup steps?
Review the broker API checklistAPI Access
- Create API app
- Configure redirect/session flow
- Confirm historical data access
- Verify instrument master
Data Limits
- Check available symbols
- Check timeframe support
- Check historical depth
- Check rate limits
Package Config
- Prepare broker_config.example.yaml
- Prepare instrument-mapping example
- Prepare broker-data setup notes
- Prepare risk_config.yaml
User-controlled Runtime
- Add credentials to local .env
- Configure VPS/static IP if required
- Run dry-run verification
- Review local setup checklist
AI explains the backtest. It does not tell you what to trade.
AI review is constrained to historical result explanation, risk observations, and user-approved experiment ideas.
Data limitations
AI explains whether the backtest was limited by timeframe, data gaps, segment, or broker availability.
Risk analysis
AI reviews drawdowns, stop-loss behavior, exposure, position sizing, and concentration.
User-run experiment ideas
AI can organize user-selected review questions, such as rule variants, risk-rule sensitivity, or different time windows.
AI analysis is for strategy review and education. It does not provide investment advice, security-selection guidance, or trade instructions.
Planned package exports include example broker configuration, not your secrets.
Safeguards
Prepare broker data. Test your rules. Export your package.
Stockey helps you understand what your broker can provide before you export the strategy as a self-hosted Python package.