Fyers invalid_auth after IP whitelist — what now?

Regenerate access token after whitelisting, confirm ipify matches whitelisted IP through proxy, and ensure app secret/redirect URL unchanged.

Fyers API v3 Static IP Setup: Whitelisting & Proxy Configuration

Run Fyers API v3 algos with a dedicated static Indian IP — myapi.fyers.in whitelist steps, Python fyers-apiv3 proxy config and session stability tips.

Fyers API v3 and static IP requirements

Fyers API v3 uses OAuth-style app registration with app ID, secret and redirect URL. Under SEBI retail algo rules effective 2026, order placement must come from whitelisted static IPs. Fyers allows up to 5 IPs per app in the API dashboard.

Whitelist your Algo-IP address

Login to myapi.fyers.in
Select your trading application
Open IP Whitelist / Security settings
Add your dedicated IPv4 from Algo-IP dashboard
Save changes

Attach proxy to Fyers Python SDK

Fyers data socket + orders on one IP

Fyers data websocket and order API should share the same egress IP. Mixed origins can cause invalid_auth or origin mismatch errors even when REST alone works.

Competitor comparison: why not residential proxy?

Some providers sell "residential" IPs for trading. Those addresses rotate, are shared with other users, and can be flagged by broker WAFs. Algo-IP provides dedicated datacenter IPv4/IPv6 mapped to your account alone — the model SEBI traceability rules expect.