How to Connect a Broker to Nexus Algo

Before you start

• Use an active trading account in your own name and confirm API access is enabled by the broker.
• Finish the Nexus account profile so account-scoped settings and audit records can be stored correctly.
• Keep two-factor authentication or TOTP available when the broker requires it.
• Decide whether you are testing the connection or preparing for live orders; use conservative limits either way.
• Open Nexus only from the official domain and check HTTPS before entering any connection information.

The common connection workflow

1. Open Settings: Sign in to the Nexus cockpit, open Settings, and select the broker connection tab.
2. Choose one broker: Select Upstox, Zerodha, Dhan, Groww, Angel One, or Kotak Neo. Nexus uses one active live broker context at a time.
3. Authorize securely: Complete the OAuth redirect or enter the broker-specific API and session fields shown by Nexus.
4. Verify the session: Use the connection check so Nexus can make an authenticated broker request and confirm the session is usable.
5. Confirm account data: Check that balance, positions, orders, and gateway state belong to the intended broker account.
6. Set risk controls: Configure risk and execution-safety limits before the first deployment.

How broker methods differ

• Upstox and Zerodha use browser-based OAuth authorization in the primary flow.
• Dhan and Groww use API or access credentials issued for the broker account.
• Angel One and Kotak Neo can require broker-specific identity fields together with TOTP or MPIN-style session authentication.
• Token expiry times differ by broker. Nexus records expiry context and also performs live verification because the broker is authoritative.

Why a connection may need renewal every day

Indian retail broker API sessions commonly expire on a daily schedule. Nexus evaluates the stored expiry context and performs an authenticated verification call when necessary. A connection that worked yesterday should not be assumed live today.

If the gateway shows disconnected, reconnect rather than repeatedly attempting deployments. A failed broker session prevents reliable balance checks, order placement, and position reconciliation.

Verify safely before live deployment

1. Read-only state first: Confirm profile, funds, positions, and order-book data before sending any new order.
2. Check the instrument: Verify exchange, symbol, expiry, strike, and option type for derivatives.
3. Check capacity: Review broker-reported available balance and the margin estimate for the intended structure.
4. Use the smallest suitable test: If a live test is necessary, minimize capital and supervise the complete entry-to-exit lifecycle.

Connection troubleshooting

• OAuth returned to the wrong page: reopen Nexus Settings and repeat the official broker authorization flow.
• Session verifies but data is empty: confirm the selected account has the expected exchange segment and API permissions.
• Token expired: reconnect; do not copy a stale token back into the form.
• Wrong account data: disconnect immediately, clear the broker session through Nexus, and authorize the intended account.
• Repeated API errors: stop deployment attempts and review the gateway diagnostic before changing risk or order settings.

Frequently asked questions