The basic position
Who carries which obligation
| Obligation | Whose |
|---|---|
| Exchange approval for algo order flow | Your broker's |
| API access controls and whitelisting | Broker, with your cooperation |
| Order-rate and risk limits | Broker and exchange |
| Research analyst registration for published strategies | The RA's |
| Keeping your credentials secure | Yours |
| Tax on your gains | Yours |
Where the rules touch you directly
- Credential security. Your API key and secret are account access. Sharing them is both a security problem and a terms-of-service one.
- Trading in your own account only. Running a strategy on someone else's account for them is a different activity with different requirements.
- Not pooling funds. Collecting money from others to trade is regulated activity requiring specific registration.
- Honest representation. If you publish strategies or results publicly, what you claim matters.
Research Analyst registration
If you want to publish
Why the API route exists at all
- Order flow has to be attributable. The exchange needs to know which broker sent an order and under whose account, which an authorised API provides and a scripted web terminal does not.
- Risk controls have to be enforceable. Order rate limits and margin checks sit at the broker, and a rejection is often one of those controls working rather than a fault.
- Access has to be revocable. Hence the daily session expiry and the address whitelist — both exist so that leaked access stops being useful.
Things people worry about unnecessarily
- Needing personal exchange approval. You do not. Your broker holds the approval for its API order flow.
- A limit on strategies you may run. No regulatory limit; your broker may apply operational ones.
- Registering as an algo trader. There is no such retail registration.
- Backtesting being restricted. It is not. Historical analysis places no orders.
Things worth actually doing
- Keep your API credentials private — never in a shared sheet or chat
- Trade only your own account
- Keep records of your trades for tax purposes
- Understand how your gains are taxed before year-end, not after
- If you plan to publish strategies, resolve registration first
The short version
- Retail algo trading through a broker's API is permitted
- Most regulatory obligation sits with your broker and the platform
- Your part is credential security, trading your own account, and your tax
- Pooling others' funds is regulated activity requiring registration
- Publishing strategies for others requires SEBI Research Analyst registration
Frequently asked questions
Yes, when it runs through a broker's authorised API. What is not permitted is circumventing that interface, such as scripting a web terminal or sharing credentials.
No. There is no retail registration for trading your own account. Your broker holds the approval for its API order flow.
Not with their money in your account. Pooling or managing others' funds is regulated activity that requires specific registration.
Because publishing a strategy for others to subscribe to requires it. Registration means an accountable, identifiable entity with regulatory obligations rather than a username.
No regulatory limit. Your broker may apply operational limits on order rates or API usage.
No. Historical analysis places no orders, so there is nothing to regulate there.
Not for the permission to trade your own account through a broker API. Your tax treatment and record keeping may look different, which is a question for an accountant rather than a regulatory one.
Not the ones that are yours — credential security, trading your own account, and your tax. The platform and your broker carry the infrastructure and approval obligations.
Start with a free 3-day trial
Build a strategy, backtest it and run it on paper — no broker, no IP and no money needed to try it.
