Error message

Unauthorized request: IP address does not match the login IP.

Last updated 16 July 2026

Broker rejects your IP (static IP not registered)

In short

Your broker rejects the request because the static IP that AutoTrader uses is not registered with the broker. Any broker error about an invalid static IP, a static IP not registered, or an order or login coming from the wrong IP has this same cause and fix. Fix it in two steps: first assign a static IP to the account in our system using the free Auto-Assign IP button (you do not buy one from your internet provider — a normal connection's IP keeps changing and will not work), then register that same IP in your broker's API dashboard. In most cases the IP shown in the broker's error is that same assigned IP, so registering the IP from the error at your broker fixes it. Only if the error shows a different IP that you did not assign should you not register it — that can happen when no static IP is set on the account yet; assign one first, or contact our support if you are unsure.

When this happens

  1. 1 No static IP is assigned to your trading account in our system.
  2. 2 A static IP is assigned in our system but it is not registered in your broker's API dashboard.

Errors

This fix applies to broker errors about IP, such as:

  • Unauthorized request: IP address does not match the login IP. (Anand Rathi, Jainam)
  • AG7002 - your IP is not a registered IP, please check your registered IP. (Angel One)
  • AG8005 - API key mismatch against app found with Static IP in request. (Angel One)
  • Access to this API is blocked due to static IP restrictions. No static IP has been configured. (Upstox)
  • Please register your static IPs first. (5paisa)
  • Orders are only allowed from whitelisted IP addresses. (Fyers)
  • Primary/Secondary IP not configured. Login denied. (XTS brokers)
  • No IPs configured for this app. (Zerodha)
  • GenAcsTok failed: Invalid Input : INVALID_IP. (Profitmart, Finvasia / Shoonya, Flattrade, PL India)
  • DH-905 - Invalid IP. (Dhan)
  • Session IP doesn’t match with request IP / unauthorized. (Kotak Neo)

Motilal Oswal also checks the request IP. If your IP is not registered, the connection is blocked, sometimes showing up as a connection or timeout failure rather than a clear IP message. The same two-step fix below applies.

The wording differs by broker, but the cause is always the same. Any broker message about an invalid static IP, a static IP that is not registered, or an order or login that came from the wrong IP has this same cause and the same fix below — even if the exact words are not in the list above.

The fix in short

Two steps, and you need both:

  1. Assign our static IP. In Accounts → Trading Accounts, click the EDIT icon next to the account and click Auto-Assign IP. This assigns a dedicated static IP from our pool (a small tax-inclusive monthly add-on) — you do not buy one from your internet provider (a normal connection’s IP keeps changing, so it will not work).
  2. Register that IP with your broker. Add the IP from Step 1 in your broker’s API dashboard (the IP whitelist field), then come back, click Validate and Save.

Register only the IP our system assigns you — not the IP shown in the error. The detailed steps are below. (Angel One is the one exception: a pool IP is not available, so you buy a static IP we set up for you or bring your own IPv4 static IP.)

Which IP do I register?

Register only the static IP that our system assigns to you in Step 1 below (the IP shown after Auto-Assign IP, or your own BYOIP for brokers that need it).

In most cases the IP shown in the broker’s error is that same assigned IP — you simply have not whitelisted it at the broker yet — so you register the IP from the error and it works. But the IP in the error is only the address the broker saw, and it is not always yours to register. If the IP in the error is different from the one our system assigned to you, do not add it to your broker. Adding the wrong IP will not fix the problem, and the IP in the error may not even belong to you. In that case, contact our support and we will check it for you.

How to fix it

You need to do two things. The IP must be set in our system and registered with your broker.

Step 1: Assign a static IP to the account in our system

  1. Go to the menu (Accounts -> Trading Accounts).
  2. Click the small EDIT icon next to your account’s client id or login id.
  3. Click the Auto-Assign IP button. The system reserves a static IP for you.
    • IPv4: one primary IP is shown.
    • IPv6: a primary and a secondary IP are shown.
  4. Note down the IP (or IPs) shown.

Angel One: a static IP from our pool is not available for Angel One. For an Angel One account you can buy a static IP we set up for you (a paid add-on) or bring your own IPv4 static IP (BYOIP). See Static IP Setup.

Step 2: Register that IP in your broker’s API dashboard

  1. Log in to your broker’s API or developer dashboard.
  2. Add the IP (or IPs) from Step 1 to the broker’s IP whitelist / registered IP field — not the IP from the error message. Register all the IPs shown (both primary and secondary for IPv6).
  3. Save it on the broker side.
  4. Come back to our system, click Validate, and Save the account.

The exact field name is different for each broker, so see your broker’s setup guide for where to enter the IP. For more detail, read the Static IP Setup guide.

Did this solve your problem?
Contact support