kotak-logo

Static IP Whitelisting for Retail Algo Trading

To comply with the SEBI circular on retail algorithmic trading participation, Kotak Neo Trade APIs will require Static IP Whitelisting for order execution.

This requirement ensures that orders are placed only from verified infrastructure, improving security and regulatory compliance.

From 1 April 2026, order APIs will accept requests only from whitelisted static IPs with a valid session created from the same IP.

If you are using Kotak Neo APIs to automate trading:

You must:

  1. Whitelist a static IP address
  2. Create API session from that IP
  3. Place orders from the same environment

If requests originate from non-whitelisted IPs or sessions created from another IP, order APIs will reject the request.

You can configure static IP from the Kotak Neo platform.

Steps

  1. Login to Kotak Neo
  2. Go to More
  3. Open Trade API
  4. If you have not already created one → Create API Application
  5. Click on Add IP and add your Primary Static IP
  6. Optionally add Secondary Static IP from the default application details page as a fallback

IP validation is enforced only on order APIs.

APIs With IP Validation

  • Place Order
  • Modify Order
  • Cancel Order

APIs Without IP Validation

  • Login APIs
  • Report APIs
  • Portfolio APIs
  • Data APIs
  • Websocket streams

These APIs will continue to work normally regardless of IP.

IP is bound to the API session.

This means:

The session must be created from the same IP that is sending order requests.

Correct Flow

  • Whitelist static IP
  • Run trading system on that environment
  • Create Neo API session
  • Place orders

Non-Whitelisted IP

If the request originates from an IP that is not whitelisted:

{
    "stCode": 100008,
    "errMsg": "unauthorized",
    "stat": "Not_Ok"
}

Session IP Mismatch

If the IP is whitelisted but the session was created from another IP:

{
    "stCode": 1037,
    "errMsg": "session ip doesnt match with reqest ip",
    "stat": "Not_Ok"
}

Sessions do not automatically terminate if IP changes.

However:

  • Order APIs will fail
  • Other APIs will continue to work

Orders will return:

unauthorized

To resume order placement:

  1. Ensure correct IP
  2. Create a new API session

Step 1 — Obtain Static IP

You can get a static IP from:

  • Your Internet Service Provider
  • A Cloud VPS

Common choices:

  • AWS
  • DigitalOcean
  • Azure
  • Google Cloud

Step 2 — Configure Your Strategy Environment

Run your trading algorithm from the system where the static IP is configured.

Step 3 — Verify Your Static IP in your configured environment

You can check your active IP using:

GET https://api.ipify.org/

If this returns your whitelisted static IP, your environment is correctly configured.

Step 4 — Create API Session

Create the Neo API session from the same environment.

Step 5 — Place Orders

Once session and IP match:

  • Place Order
  • Modify Order
  • Cancel Order

Requests should return HTTP 200 OK.

Kotak Neo allows family members to share the same static IP.

Rules

  • Up to 10 family members can be added
  • Sharing is only for static IP usage
  • It does not give account access

Important: Existing login family relationships do not automatically apply here. You must add family members separately under Trade API family management.

Parent Account

Can:

  • Add family members
  • Add static IP
  • Change static IP

Child Accounts

Can:

  • Create API application

Cannot:

  • Add or modify static IP

Are Market Orders Allowed?

As per SEBI circular, market orders are not allowed for retail algos.

Kotak Neo recommends using limit orders.

If you still send a market order, the system will automatically according to below grid:

Price grid:

Buy orders use a protection limit above the LTP; sell orders use a limit below the LTP.

Same logic would be valid for AMO market orders.

Please note,

  1. in case of options, IF LTP is unavailable we have to reject the order. Make sure the rejection reason is clear.
  2. Client place order in Market but in order book Limit order will get visible

For precise execution, always use limit orders.

Do users need to send Algo ID in order payload?

No.

Kotak Neo APIs automatically append the appropriate Algo ID.

This is because:

  • APIs are rate limited to 10 Orders Per Second
  • APIs are intended for tech-savvy retail users

The system automatically sends the required exchange-compliant Algo ID.

What if I use a fintech platform to place algo trades?

As per SEBI circular:

Your fintech partner must:

  • Get empanelled with exchanges
  • Host their infrastructure on broker systems

To continue using the service, confirm with your fintech partner:

  • Are they exchange empanelled?
  • Are they hosted on Kotak infrastructure?

How many IP addresses can I whitelist?

Maximum 2 IP addresses:

  • Primary IP
  • Secondary IP (fallback)

How many sessions can I create?

You can create multiple sessions.

However:

Orders can only be placed from 2 sessions simultaneously:

  • Session created from Primary IP
  • Session created from Secondary IP

How often can I change my IP?

  • You can update IP once every 7 days.

  • After changing IP, create a new API session.

Is there any delay after whitelisting IP?

No.

Changes apply immediately.

Can I use IPv6?

Yes.

IPv6 can be whitelisted.

Currently the platform supports IPv4, and IPv6 platform support will be available soon.

Can multiple accounts use the same IP?

Yes.

Family accounts can share the same IP.

Can I run multiple strategies from the same IP?

Yes.

Multiple strategies can run from the same IP if sessions are created from that environment.

Do websocket streams require the same IP?

No.

Websocket connections are not restricted by IP validation.

If you face issues configuring static IP or sessions, please contact Kotak Neo API support.
service.securities@kotak.com