Preparing to comply with SEBI's retail algo rules (Static IP, ratelimits, order types)

@Matti, I want a clarification on this:::: Market orders will require market protection. Orders placed with market protection set to "0" will be rejected.


I want a clarification on this, since all the orders are executed from my UI, and the range is set before trades are executed, and all are market orders placed based on candle close of previous minute along with stop losses placed the second after executing the order

Moreover, strategies also include short straddle, for which the SL is placed in the system, not visible in the order book, but it is there, how to proceed with this

For this do I need to make changes in the code?

@Matti

Sharing of IPs is permitted between family members => But I am getting "The IP address(es) you are trying to add are already linked to another account. Each IP address can only be linked to one account." error when I try to add the same IP in family member account.

I have configured IP in profile page.
Is there any API i call call from the my System to check whether the IP is configured correctly ?

eg. GET /static_ip/config

When called from correct system, It should return.

{
  "status": "success",
  "data": "The static IP (x.x.x.x) configured is valid."
}

When called from different system, i should return error.

{
  "status": "error",
  "data": "The static IP (x.x.x.x) configured is not valid. Your current IP is (y.y.y.y)"
}

I hope this option will solve @SpacemanSpiff 's problem.
I do not want to check this configuration in live orders.
Hoping for a solution before enabling the restriction.
@Matti

You can add multiple zerodha accounts in single developer profile.

@kiteapi

It seems like market_protection is not even introduced as a param in python sdk
https://github.com/zerodha/pykiteconnect/blob/6b7b7621e575411921b506203b526bf275a702c7/kiteconnect/connect.py#L336-L352

Is it accurate to infer that any market order placed from April 1 using python sdk would start failing . Am I missing something because this seems like a serious oversight

If this doesn’t get fixed before April 1 which it probably won't, I think kite._post or kite._put can be utilized as a workaround.

Not ideal though, these are internal methods, so treat this as temporary and have to be revalidated after SDK updates but still better than rewriting entire code from python sdk to http

If needed, I can provide VPN access with high-speed internet and static IP addresses for your developer accounts at a very low cost.

@Tusshar18

Market orders must now have market protection—orders with “0” will be rejected. So yes, you’ll need to update your order placement logic to include this.

Any market order must comply with this rule.

For your current setup:

• If market orders are being placed via API, you’ll need to update the code to include a suitable market protection percentage.
  
• If orders are placed via UI/manual flow, ensure the same is configured appropriately in the order placement settings.
  

Are you saying that you are still working on the sdk support for this when the cut off date for market protection orders is 1st Apr.?
This is serious problem, from 1st Apr, the market orders via SDK will start failing (as existing SDK does not provide any option to set market protection in the market orders).

@Sravanthi_bh how does market protection impact options trading in selling side, considering there is no major price fluctuation while the order is executed in a particular range

@Tusshar18
Market protection sets a limit on how far the execution price can deviate from the current market price for market orders.
For options selling, it helps prevent execution at significantly lower prices during sudden spikes or low liquidity.Learn more.

@RS6006 - Yea, but, as a standard practice, it's not recommended to update the site-packages manually. Especially if the system is docker containerised, it becomes unnecessary burden to update the package in a manual way.

Btw, during my testing today, the PR doesn't seem to work either, the market_protection parameter is ignored by the backend it seems.

Requesting @kiteapi @kiteconnect to look into this matter quickly because only 2 trading days are left before this becomes a bigger problem for Zerodha !

cc: @scaars13 @yogeshs

@Tusshar18 Market protection acts as a final safeguard at execution level, ensuring the order doesn’t get filled at an extreme price during sudden volatility or illiquidity.
So, irrespective of your entry logic, this needs to be included for all market orders.

@knightrider - I have added the market_protection = 2 flag in my order placements. Still getting error.
@Nivas - Is there an ETA by which market_protection flag will be enabled for python sdk? All my orders are failing this morning.

@adarsh1392 - It's not about adding parameter while calling the method, the definition of the place_order() in kiteconnect.py [kiteconnect package] needs to accept that parameter right. I was talking about that.

@adarsh1392 - Maybe they'll take cognisance of this issue once they see their brokerage go down quite significantly !

@kiteapi @kiteconnect

I will need this feature for Java kite connect

@adarsh1392 @knightrider Market protection will be added in all SDKs by tonight or tomorrow.

I do not want to check this configuration in live orders.

How do we test that its working ?

@subrah @SpacemanSpiff March 31st is a holiday; we are discussing taking this validation live on that date. Once it is live, you can verify it by placing AMO orders.

Please make sure to consider the case of modify_order() when I'm trying to modify an existing LIMIT-SL order to MARKET order.

When you convert from a limit to a market protection order?

@Arockiya_r - Example:
- I have an trigger-pending SL-LIMIT order
- Sometimes, before hitting the trigger, I need to square the order off the position. In that case, instead of cancelling the existing trigger-pending SL-LIMIT order and creating a new market order for squaring off my position, I just modify the existing trigger-pending SL-LIMIT order to a MARKET order. I do that by using modify_order() method in kiteconnect.py. So, I need to have a market protection parameter for that method as well.

@Arockiya_r - Awesome ! Thanks a lot !!

Zerodha Team: Pls reconfirm my following understanding based on understanding of various discussions and documnetation.

1.0 Whenever we place a new Market order- A NON ZERO Market_protection parameter value MUST be defined.
2.0 If I set this value as -1, auto protection limits specified by Zerodha will be applied
3.0 Whenever I want to modify a market order, I dont need to specify the market-protection parameter again.
4.0 Whenever I modify a LIMIT order as a Market Order, market_protection value should be redefined.
5.0 Can I specify the Market_protection parameter value for LIMIT/SL orders also so that when I modify these orders as Market orders, the value is already there?

@Matti@, regarding modification of limit order to market order, market_protection is not available as per API documentation. The list of available parameters is as follows. Pls clarify.

Regular order parameters¶
parameter
order_type
quantity
price
trigger_price
disclosed_quantity
validity

regarding modification of limit order to market order, market_protection is not available as per API documentation. The list of available parameters is as follows.

What SDK are you referring to?

Can someone please update if we are going to get the zerodha kiteconnect Java SDK change for market protection before 1st April?

Hi
Thanks.
Just checked.
You guys have updated the code in the GitHub repository but release is not created for the new version.
Anyways, that solves the problem.
Thank you.

@Arockiya_r - Strange ! My orders when converted from SL-LIMIT to MARKET (with market_protection=-1) do not show the shield icon in the orders. Instead, those seem to be executed as LIMIT orders. Can you please check why is that?

@Arockiya_r - Okay ! Thanks for the prompt and detailed explanation ! Cheers !!

Does only data feed requests from API requires static IP ?

@Arockiya_r - Is the static IP check in production? I can still place AMO orders without registering any IP.

While placing SL/Limit orders, market_protection parameter value does not need to be defined at all, not even 0 Value.

Market protection is technically a limit order, this is not applicable to limit/SL.

You shall be implementing static IP validation and market_protection parameters by tonight so that we can test tomorrow.

You can test it today @DaneshBansal

Does only data feed requests from API requires static IP ?

only order endpoints are will be validated against the static IP

@Matti @Arockiya_r I would like to understand how the order rate limit of 10 orders per second is applied when multiple apps share a static IP in the Kite developer account. Specifically, if I have three separate trading family apps under one Kite developer account and single IPv4 Static IP, and all three apps are using the same static IP, does the rate limit of 10 orders per second apply per app individually, or is it a total limit shared across all three apps for that Static IP? In other words, do all three apps combined have to stay within the 10 orders per second limit, or is each app allowed its own 10 orders per second?

In simple:
- All apps under same kite developer account can send individually 10 Orders/sec same static IP and after limit we will get error_429, or
- all apps under the same kite developer account can send combined rate limit order of 10 order per second, mean totally we have a max potential to send 30 orders per second means 10 orders by each app

Kindly clarify my confusion for that particular issue

@deepak163299 10 OPS is account-specific, regardless of the number of app

Thanks

kite client ID specific.

@yogeshs

Please verify whether the order request is transmitted using IPv4 or IPv6, and update the respective IP address accordingly. If the request is sent via IPv4 but the IPv6 address has been updated in the developer profile, the IP validation will not pass.

seems kite connect sdk is transmitting the request using IPv4

This is not controlled at the KiteConnect library/SDK level. The SDK will use the network path and source IP chosen by the client environment. For static IP validation, what matters is the actual outgoing IP address from which the request reaches the broker. So this needs to be handled on the client’s infrastructure/network side by identifying the egress IP being used and updating the correct IPv4 or IPv6 whitelisted IP accordingly.

Were users alerted to this change in any way or only through this post on this forum??

Does the market protection rule also apply to MCX Commodity contracts for algo/API orders?

yes.

will the API accept market orders (or SL-M orders) if I send a non-zero market protection value?

Yes, market with market protection is allowed.

@AmitManna99 I am also facing similar issue
first - ❌ Order placement failed: Market orders without market protection are not allowed via API. Please set market protection or use a Limit order.

After I used market_protection=-1

❌ Order placement failed: KiteConnect.place_order() got an unexpected keyword argument 'market_protection'

@AmitManna99
1. Not applicable to the kite publisher.
2. The market order not allowed rule is also not applicable to the publisher.

@Arockiya_r
1. Do you mean Market Orders are not allowed for Publisher API?
2. Because when I'm trying to place MARKET Order, I'm getting error saying - "Market orders without market protection are not allowed via API. Please set market protection or use a Limit order."
3. When I'm placing LIMIT order, I see limit price automatically become zero when it's going to kite.zerodha.com/connect/basket

@AmitManna99 I am checking this.

Update on my previous comment:

When I'm placing LIMIT order, I see limit price automatically become zero when it's going to kite.zerodha.com/connect/basket

I'm able to place LIMIT orders now. Actually the mistake was, my server was sending the limit price, however the HTML Page logic was removing it manually before making POST call to basket page. Since, I used to place MARKET order earlier, I forgot to remove the logic.

However, the other two points remains a question:

1. Do you mean Market Orders are not allowed for Publisher API?
2. Because when I'm trying to place MARKET Order, I'm getting error saying - "Market orders without market protection are not allowed via API. Please set market protection or use a Limit order."

Anyone kindly suggest a dedicated- static ip VPN service which is reliable and affordable. Ty.

@tuxred i manually place customised orders from excel..
Not automated trading..
Vpn is the only way i can think of. Static ip via ISP is needless and expensive.
Dedicated static ip - VPN service is what I'm looking for.