IIFL Capital, the new name of IIFL Securities, is one of the brokers that run the XTS trading system, and QuantPower connects to it through that route. XTS brokers share one way of connecting: a client code, an API key and an API secret, a session that lasts the trading day, and a "Log in again" step each morning that uses your saved key. This page explains what you need, how to connect step by step, what changes each trading day, what QuantPower can and cannot do on your IIFL account, how SEBI's rules for retail algos apply, worked examples, and what to do when something goes wrong.
A short history of IIFL and its trading APIs
IIFL began in 1995 as Probity Research and Services, a research firm founded by Nirmal Jain, and grew into India Infoline, one of the early online brokers of the internet era. Its broking business was later run as IIFL Securities, and it now operates as IIFL Capital Services. The name has changed; the broker and client accounts have not.
For years, IIFL's clients who wanted to automate reached the market through the XTS trading system built by Symphony Fintech, which many Indian brokers use for their trading terminals and APIs. IIFL's version is known as Blaze: the Blaze terminal for trading and the Blaze API portal for API keys. IIFL also offers its own newer API on the IIFL Capital developer portal. QuantPower connects to IIFL through the XTS route, which it shares with other XTS brokers.
The rules around those APIs changed in 2025 and 2026. SEBI's circular of 4 February 2025 made every broker responsible for the algo orders that pass through its API, tied API access to registered static IPs, and set an order-rate limit above which an algo must be registered with the exchange.1 After two postponements, the framework came into force for every broker from 1 April 2026.2 IIFL, like every broker, now applies those rules to every order that reaches it through an API.
How QuantPower connects to IIFL
| Part | How it works on IIFL |
|---|---|
| Connection type | IIFL's XTS trading API |
| What you enter | Your IIFL client code, API key and API secret, once |
| How keys are kept | Sent once over https, stored encrypted, never shown again; the screen shows your client code masked |
| Daily session | QuantPower signs in at IIFL with your saved key; the session lasts the trading day |
| Where orders come from | Your two static IPs, through a forwarding proxy that uses only them |
| If the static IP route is down | Orders are held, never sent from another address |
| Prices | From your connected broker's feed |
You do not need a computer or a VPS of your own, and nothing needs to stay switched on at your end while your algos run. You can close the app or switch off your phone.
How to connect IIFL to QuantPower
- Ask IIFL for API access. IIFL activates its XTS (Blaze) API for a client on request, from the client's registered email.4 Once it is active, create your API app on IIFL's API portal and note the API key and API secret it gives you. IIFL's portal also offers a separate key for market data; the Brokers screen in QuantPower asks for the keys it needs.
- Open Brokers in QuantPower and choose IIFL Capital.
- Enter your client code, API key and API secret. QuantPower asks for your tap, then sends the keys once over https. They are stored encrypted and never shown again.
- Register the static IPs. The broker row shows your two static IPs. Enter them as the allowed addresses for your API app on IIFL's side, as IIFL's process asks.
- Sign in for the day. QuantPower signs in at IIFL with your saved key. The row shows "signed in" and when the session ends.
- Check the connection. Your positions, holdings, funds and orders should appear in QuantPower as IIFL holds them.
- Test before you go live. Run a new strategy in Forward test first, with test money, then switch it on live with the smallest size. The algo bot setup tutorial walks through the settings.
The general checklist for every broker is in our guide to broker connection requirements.
IIFL API terms you will see
| Term | What it means |
|---|---|
| Client code | Your IIFL trading account ID |
| Interactive API | The part of the XTS API that places, changes and cancels orders and reads your positions and orders |
| Market data API | The part that streams prices |
| API key and secret | The pair that identifies your API app; keep the secret private |
| Session | The sign-in for the day; it ends at the end of the trading day |
| Static IP | The fixed address your API orders must come from, registered with IIFL |
| Order rate | Orders per second from your account; above 10 a second an algo must be registered with the exchange through the broker |
Every trading day
- Before the first entry: use "Log in again" on the IIFL row. A live algo cannot be switched on to enter now while the broker is signed out; an algo with a later entry switches on and its card asks you to sign in before the entry.
- Before each entry: check free margin. Option buyers pay the full premium; sellers need SPAN and exposure margin.
- On expiry day: short index options expiring that day need extra margin, and Nifty weekly options expire on Tuesdays.
- During the day: the IIFL row shows when the session ends. If IIFL ends it early, the row shows "Sign-in needed" and later entries are refused until you sign in again.
- After the close: the session ends, and the next trading day starts with a fresh sign-in.
What QuantPower can and cannot do on your IIFL account
| QuantPower can | QuantPower cannot |
|---|---|
| Show your positions, holdings, funds and orders as IIFL holds them | Withdraw money from your IIFL account |
| Place, change and cancel orders for your strategies and your manual trades | Change your bank account, address or nominee |
| Square off positions when Smart Exit is hit, and stop the algos | See the password you use with IIFL |
| Refuse new orders once your daily loss limit is reached | Trade after your IIFL session has ended |
| Stop trading in a segment with the kill switch | Send an order from an address other than your static IPs |
| Read live prices for your charts and strategies | Switch an algo on by itself, from an AI app or anything else |
Your IIFL account inside QuantPower
Once IIFL is connected, day-to-day trading does not need a separate broker app open beside it:
- Positions with M2M as IIFL holds them; convert a position's product, exit one, or exit all.
- Holdings with profit and loss, and pledging of holdings for margin.
- Funds: margin, collateral, cash and what can be withdrawn.
- Orders: market, limit, SL and SL-M where the exchange allows them; intraday, delivery and overnight products; GTT orders that wait up to 365 days; baskets of up to 20 legs; iceberg orders; stock SIP.
- Trading from the chart and the Scalper: order, position and GTT lines on the chart, and a call-and-put screen for fast option trades. Every action opens the order sheet for your tap.
Running several strategies on one IIFL account
Up to 20 algos can run at a time, each with up to 6 legs. Each algo's own stops limit that algo; the account's Smart Exit, an MTM stop loss for the whole account, and the daily loss limit cover all of them together, and the loss figure adds up every connected broker. Check that the margin of every algo that may be in a position at once fits the account, or later entries will be refused for margin.
If you also trade at another broker, an algo is switched on at one broker and every leg goes there. With two brokers connected, the order sheet asks which broker; nothing is sent to a guessed broker.
Market data from IIFL
Prices in QuantPower come from your connected broker. Once IIFL is connected and signed in, your charts, the option chain, the scanner and your algos read IIFL's feed. Each feed shows its state: live, delayed, stale or closed. With no broker connected, QuantPower shows no live prices; Forward test then uses the prices your account sees.
The charts are Arth.live's chart engine, with 201 indicators, 19 chart types, 89 drawing tools and up to 16 charts on one screen. Your algos, alerts and risk rules use each contract's own market hours, so commodity and currency contracts follow their own sessions.
Commodity and currency on IIFL
QuantPower covers NSE and BSE cash and F&O, commodity contracts on MCX, NSE and BSE, and currency on NSE and BSE. Whether you can trade a segment depends on what is enabled on your IIFL account; ask IIFL to enable commodity or currency if you need them. Algo legs can be commodity and currency futures and options, picked by search, and the account's limits cover them with everything else.
Costs to count
A strategy on IIFL has three kinds of cost:
- Brokerage, under your IIFL plan, on every executed order.
- Statutory charges: STT, exchange transaction charges, SEBI fees, stamp duty and GST, the same at every broker. STT on futures and options rose from 1 April 2026.5
- QuantPower tokens: 200 per live algo per 28 days, 100 per Forward-test algo, and 2 per backtest after the first 10 free each week. Orders inside a live algo are unlimited, so a busy strategy costs the same tokens as a quiet one.
A checklist before your first live algo on IIFL
- API access is active at IIFL, and the key and secret are entered in QuantPower.
- Both static IPs are registered with IIFL for your API app.
- The IIFL row shows "signed in" with today's session end.
- Positions, holdings and funds in QuantPower match IIFL's own terminal.
- The strategy has run in Forward test and its trades look as expected.
- Smart Exit and the daily loss limit are set for the account.
- Margin covers the strategy at its live size.
Order rules at IIFL
- Stop orders in options. NSE does not accept stop-loss market orders in options.3 Algo exits are market orders that only reduce a position; for entries and manual stop orders in options, use limit or stop-limit orders.
- Freeze quantity. An order above the exchange's freeze limit for a contract is rejected. QuantPower splits an order above the freeze quantity automatically, and iceberg orders send 2 to 50 legs one after another.
- Order rate. Keep your account under 10 orders a second. A short straddle sends two orders at entry and an iron condor four; QuantPower sends buy legs first, then sell legs, so a hedge is in place before a sold option.
- Price bands. Orders outside a contract's price band are rejected by the exchange.
A worked example: a Nifty short straddle on IIFL
This is a hypothetical example.
A trader connects IIFL and sets up the Short Straddle template as an algo: sell the ATM call and the ATM put, weekly expiry, one lot each (65 units), entry at 9:20 am on Tuesdays, a 30% stop on each leg, an algo M2M stop of ₹4,000, and exit at 3:10 pm.
- At 9:05 am the trader uses "Log in again" on the IIFL row. It shows "signed in".
- At 9:20 am the algo picks the ATM strike from the index price and sends both sell orders through IIFL's API from the trader's static IP. The card shows both fills; IIFL's order book shows the same two orders.
- At 11:40 am the index moves up and the call rises 30% above its entry price. The algo buys back the call at market. The put stays open.
- At 3:10 pm the algo buys back the put. Both legs are closed, and the activity log lists every order.
The trader then compares the day's trades with the backtest for the same day. If the fills are much worse than the backtest assumed, the slippage setting in the backtest was too optimistic. After a few weeks of such comparisons, with the trades in Forward test and live side by side, the trader knows how the strategy behaves on IIFL in practice, and can decide whether to raise the size with the quantity multiplier.
A worked example: a chart alert to IIFL
This is a hypothetical example.
A trader uses an Arth.live price alert on Nifty futures. In QuantPower they create a webhook and link it to an algo with one leg: buy one lot of Nifty futures, intraday, with a stop and a target. They link the Arth.live alert to the webhook.
When the alert fires, the webhook's entry hit switches the algo on for the day and enters now, through IIFL's API. A second alert, pointed at the same webhook as an exit, stops the algo and squares off. Outside market hours, or after the algo's exit time, a hit does nothing and the webhook's hit log says why. The trader can see every hit in the log, up to the last 500.
A worked example: a stock signal on IIFL
This is a hypothetical example.
A trader wants to buy a stock when its 20-period EMA crosses above its 50-period EMA on 15-minute candles, with a stop and a target. In QuantPower they create a signal algo on that condition. The condition is checked on closed candles.
- In one-touch mode, the default, the signal fires a notice when the cross happens, and the order is ready in the app; the trader places it with one touch, and it goes to IIFL.
- In auto mode, after the trader arms it, the signal places the order by itself when it fires, with every risk check. Any change to the condition or the order disarms it.
Either way, the order goes through the same order path as a manual order, with the kill switch, the daily loss limit and the cap on orders a day checked first. A signal that places its own order costs no tokens; only an algo that a signal starts is charged as a live algo.
Moving from your own XTS script
Some IIFL traders already run their own Python scripts against the XTS API. Moving a strategy into QuantPower changes three things:
- Where it runs. The script no longer needs a machine of yours that stays on through the session; the algo keeps running with your computer off.
- Where the IP comes from. Orders leave from the two static IPs included with your QuantPower account, instead of an address you arrange yourself.
- What sits above it. Smart Exit, the daily loss limit, the kill switch and the cap on orders a day apply to the strategy and to your manual trades together, across every connected broker.
If your signals must still come from your own code, keep the code and send its entry and exit signals to a QuantPower webhook. The webhook starts and stops your algos, and the algos send the orders.
When something goes wrong
| What you see | Likely cause | What to do |
|---|---|---|
| "Sign-in needed" on the IIFL row | The day's session has ended | Use "Log in again" |
| The login is refused | Key, secret or client code wrong, or API access not yet active | Check the keys with IIFL; re-enter them in QuantPower |
| Orders are refused with an IP message | The static IPs are not registered for your API app | Register the IPs shown on the Brokers screen with IIFL |
| An algo entry is refused | Margin, a risk rule, the kill switch or the daily loss limit | Read the reason on the algo card |
| An exit is refused | A broker or exchange rejection | The algo retries up to 8 times; check IIFL's order book and exit by hand if needed |
| Prices stop updating | The broker's feed or session | Check the session; prices come from your connected broker |
Before you ask for help
Most connection problems can be traced with four checks, in this order:
- Is the session live? The IIFL row shows "signed in" and today's session end. If not, use "Log in again".
- Are the keys right? A refused login usually means a wrong key, secret or client code, or API access that IIFL has not yet activated.
- Are the IPs registered? Orders refused with an address message mean the two static IPs on the Brokers screen are not yet registered with IIFL for your app.
- What does the algo card say? Every refusal is written there and in the activity log, in plain words: margin, the kill switch, the daily loss limit, an expired contract or the broker's own rejection.
If you still need help, use "Copy log" on the algo card and send the day's log with your question. It shows every entry, exit and refusal with its time, which is usually enough to find the cause.
What SEBI's rules mean for an IIFL user
| Rule | What it means on IIFL with QuantPower |
|---|---|
| Your own API access | Keys issued to you by IIFL, entered once and stored encrypted |
| Registered static IP | Orders come from your two static IPs, registered with IIFL |
| Changing the IP | Brokers limit how often a registered IP can be changed |
| Daily sign-in | A fresh session each trading day |
| Order rate | Under 10 orders a second, unless the algo is registered with the exchange |
| The broker's kill switch | IIFL can stop algo orders on your account at once, as every broker must be able to |
| Black-box strategies | Strategies whose logic is hidden are offered only by registered research analysts; QuantPower's algos are your own rules, fully visible to you |
Building IIFL strategies with Quanty and your own AI app
Quanty, the AI assistant in QuantPower, can build a strategy from your description, backtest it and save it switched off for you to check. It can read your IIFL positions, funds and orders through QuantPower, and explain why an algo did or did not trade today. It cannot place, change or cancel an order, and it cannot switch an algo on.
If you use your own AI app, such as Claude or ChatGPT, Connect AI links it to your QuantPower account with the permissions you choose. It can read your account and market data, backtest your rules and prepare an order as a card in your app; only you confirm it, with a tap and the second factor of your login. Both Quanty and a connected AI app are software, not advisers: they help you build and test your own rules and do not tell you what to trade.
Security
- Your API secret is stored encrypted and never shown again. Admin screens show masked values only.
- Sensitive actions in QuantPower, such as exiting all positions, setting the kill switch or connecting an AI app, ask for the second factor of your QuantPower login.
- Each device you sign in on is listed under Settings, and you can sign any of them out.
- If you think your IIFL API secret has been exposed, regenerate it at IIFL and enter the new one in QuantPower.
- Never share your API secret in a chat, an email or a screenshot, including with anyone who says they are from support. Nobody at QuantPower needs it to help you.
Where IIFL algo trading is going
Two changes are under way. Brokers, IIFL among them, are building their own developer portals alongside the XTS route, with newer sign-in flows and documentation. And under SEBI's framework, the broker's role in every algo order keeps growing: registered IPs, order-rate checks and the broker's own kill switch are now standard. For a trader, the practical effect is that connections are more uniform across brokers, and the daily sign-in and the registered static IP are part of every automated setup.
Start with 500 free tokens
Connect your broker, build a strategy and test it on paper before a single live order goes out.
Frequently asked questions
Which IIFL API does QuantPower use?
IIFL's XTS trading API, the route IIFL offers through its Blaze API portal. You enter your client code, API key and API secret once, and QuantPower signs in for the day with your saved key.
Does QuantPower see my IIFL password?
No. QuantPower keeps your API key and secret, encrypted, and the day's session. It never asks for or stores the password you use to log in to IIFL.
Is IIFL Capital the same as IIFL Securities?
Yes. IIFL Securities is now named IIFL Capital Services. The broker, and your account with it, are the same.
Do I need my own computer or server to run algos on IIFL?
No. Algos keep running with your computer off and send orders to IIFL through its API from the two static IPs included with your account.
Can I trade options through the IIFL API?
Yes, once F&O is enabled on your IIFL account. For entries and manual stops in options, use limit or stop-limit orders, because stop-loss market orders are not accepted in options on NSE.
What happens to my algos if I forget to sign in to IIFL?
A live algo that would enter while IIFL is signed out cannot be switched on, and a later entry is refused with the reason on the algo card. Nothing signs in for you. Sign in with "Log in again", and switch the algo on again if it was refused.
Can I run algos on IIFL and another broker at the same time?
Yes. Each algo runs at one broker, which you choose when you switch it on. Smart Exit and the daily loss limit add up the positions of every connected broker.
Related guides
- Zerodha algo trading: connecting a Zerodha account through Kite Connect
- Fyers algo trading: connecting a Fyers account
- Wisdom Capital algo trading: connecting a Wisdom Capital account
References
- SEBI, circular on safer participation of retail investors in algorithmic trading, 4 February 2025 (sebi.gov.in)
- SEBI, circular extending the timeline for implementation, 30 September 2025, with the framework in force for every broker from 1 April 2026 (sebi.gov.in)
- NSE, circular on the discontinuation of stop-loss market orders in options, 2021 (nseindia.com)
- IIFL Capital Services: help pages on getting IIFL APIs (help.iiflcapital.com) and the Blaze API setup described by third-party platforms (docs.algotest.in), checked 12 November 2026
- Union Budget 2026-27: securities transaction tax on futures and options raised from 1 April 2026 (indiabudget.gov.in)