administrators

@garv4you can you please share your client id and date and time of the issue?

Hello All,

The changes will take place on 1st October 2025.

@tushar22 As per the circular, only 1 API key can be used for non registered, client generated algos.

By providing more API keys, it will be non compliant with the circular.

@openalgo OAuth will be live soon, and for some time, it will be live along the current login process.

@lakshay-kh The deadline in the new circular is for 1st October. So it is not mandatory as of now.

But do keep a static IP handy, and register it before the deadline to avoid any last minute hiccups.

@kc Cancel orders API also goes to the exchange. To avoid any kind of impact at the exchange, we have kept a OPS of 10 on cancel order too.

@hemanthkumar097 said in Important Updates to SmartAPI in Compliance with SEBI Guidelines:

rader with rate limits less than 10 orders per second (M

Yes, you would still need a static IP, you will not need to register your algo with the exchange.

@staticip

The Addition of Static IP is live in the portal.

We have not yet kept static IP mandatory, but users can register their static IP by Logging in to SmartAPI -> My Profile -> My APIs (new)

Dear SmartAPI Users,

In accordance with SEBI’s circular on the “Safer Participation of Retail Users in Algorithmic Trading,” we are implementing a few important changes to SmartAPI.

These changes will be live from 1st August 2025.

Please review the updates below:

1. Static IP Requirement: Users must obtain a static IP address and register it with Angel One. Only orders originating from registered IPs will be executed; all others will be blocked. The page to register the static IP with Angel One will be live by 30th July 2025.
2. Multiple IP Support: Up to five static IPs can be linked to a single API key.
3. Order Throttling: A rate limit of 10 orders per second will be enforced on the order APIs (Place order, modify order, cancel order and all the GTT apis).
4. OAuth Login: The authentication process will be updated to use OAuth for improved security and compliance. The documentation will be updated by 30th July 2025.
5. Support for exchange segment of NCDEX will be stopped in SmartAPI.
6. Authentication token will be expired at 00:00 hours everyday.

We appreciate your cooperation and understanding as we make these updates to ensure compliance.

Best regards,

The SmartAPI Team

How to use smartapi websocket connections?