How to Connect a Broker Data Feed

Before you begin

You need a signed-in TradingLead account with current platform access and, for private feeds, an eligible provider account. TradingLead's five-day product trial is separate from the provider's market-data subscription, quotas and exchange rights.

Choose the connection for the instrument you actually want. FYERS website coverage includes supported NSE/BSE equities, indices and futures. Dhan website coverage is supported NSE/BSE cash equities. Neither establishes an available Indian CE/PE options-chart workflow.

Other offered providers address supported US, forex, metals or crypto instruments. See broker data feeds rather than assuming an Indian brokerage connection can supply every market.

1. Open the correct connection surface

Open Data feeds or the chart feed selector's setup/manage action. In a normal browser, the page presents website connections. Desktop has separate local connections and may expose additional provider interfaces.

Do not treat matching broker names as one shared session. A website connection does not automatically replace Desktop-local credentials, and a local connection does not certify that the website provider is ready.

Check that the desired provider is actually offered. A definition in documentation cannot make an unavailable or unconfigured catalog entry selectable.

2. Review the required login mode

FYERS platform mode uses TradingLead's configured app and sends you through hosted broker login and consent. It does not require each user to create an API app.

If an individual API-app mode is offered, provide the exact fields requested and register the displayed callback URL with the broker when required. Dhan setup can also require the intended client ID, including a partner flow that does not ask you to create an API app.

BYO-key providers such as Alpaca, Alpha Vantage, Twelve Data and OANDA have their own fields. OANDA requires the correct practice/live environment. These are provider requirements, not interchangeable TradingLead passwords.

3. Complete consent and verify status

Use Connect and finish the official provider-hosted flow where applicable. When you return, refresh connection status. The chart-initiated flow can return you to the chart's provider dialog.

A callback success message is not sufficient proof of a usable connection. Read the verified current status. If it cannot be checked, resolve that error rather than relying on an old Connected badge.

Never paste passwords, PINs, TOTP codes or API secrets into a chart, support conversation or assistant prompt. Use the designated setup form and official consent page only.

4. Test a supported symbol and interval

Select an instrument from the provider's supported catalogue and choose an available timeframe. Use Test candles.

This is a bounded history request and can consume provider quota. It establishes only that the selected request returned a sample. It does not establish a continuous stream, unlimited history or every interval for that instrument.

If the test is empty, check the exchange, contract type, expiry and interval. FYERS futures are not options. Dhan cash-equity support does not imply index or derivatives access. An unsupported instrument is not fixed by repeatedly reconnecting.

5. Apply the tested context explicitly

The dialog identifies the Current chart feed separately from provider status. Testing alone does not switch it. After a successful sample, choose the offered Use on chart or Open chart action.

Where Check data & switch is offered, it first verifies a bounded request and switches only when candles are returned. Empty results, errors and cancelled checks should not be treated as successful source changes.

Confirm the chart's provider, symbol and interval after switching. Wait for loaded candles and inspect timestamps, not only the toolbar label.

6. Enable live updates only when supported

FYERS website connections can provide opt-in browser-direct live quotes for entitled accounts. Enable the supported Live updates control and check its actual status.

Other website connections currently provide historical candles rather than that live transport. A disabled Live toggle is not necessarily a broken login. Built-in cloud updates are another source again and do not establish guaranteed real-time exchange ticks.

Troubleshooting and limitations

• Session expired: use the provided reconnect/login flow; TradingLead sign-in and broker expiry are independent.
• Rate limited: wait for the displayed retry window; repeated reloads consume quota.
• Unsupported symbol: search the selected provider's catalogue, not another feed's universe.
• Missing interval: choose a supported interval; derived candles still need compatible underlying history.
• Desktop-only provider: use the documented Desktop path rather than looking for a nonexistent website connector.

Do not silently splice another source into the original history. If you intentionally change feeds, treat it as a new verified chart context.

FAQ

Does disconnecting close my brokerage account?

No. It removes the TradingLead website connection, not the underlying brokerage account. Desktop-local connections remain separate.

Can the feed submit live orders?

These are chart-data connections, not an implemented live broker order-execution flow. See Indian stock coverage for instrument limits before planning research.