Trading APIs · Developer preview

The broking desk,
now an API.

Orders, live market data, portfolio and risk — the full SMIFS trading stack behind clean REST and websocket endpoints. Start in the paper sandbox today; exchange connectivity follows the same contract.

Try it live below Open API reference →

No sign-up for sandbox · familiar broker-API request shapes · v1

sandbox · smifsgq.smifs.com connecting…

10/secorder rate per client

7,000orders per day

500msfeed tick interval

₹0API access charges

The surface

Five APIs. One venue contract.

Every endpoint works identically against the paper venue and, as connectivity ships, the live exchange lines.

Orders & Super Orders

Regular, cover and bracket-style super orders, GTT forever orders, price triggers and large-order slicing.

POST /v1/orders
POST /v1/orders/slice
POST /v1/super/orders
POST /v1/forever/orders

Live Market Feed

Snapshot quotes over REST and a binary websocket that streams ticks, quotes and market depth.

POST /v1/marketfeed/ltp
POST /v1/marketfeed/quote
WSS /feed

Portfolio

Positions with live mark-to-market, holdings, and position conversion between products.

GET /v1/positions
GET /v1/holdings
POST /v1/positions/convert

Funds & Margin

Fund limits, per-order margin requirements and multi-leg margin with spread benefit.

GET /v1/funds/limits
POST /v1/funds/margin
POST /v1/funds/margin/multi

Historical & Options

Intraday and daily candles, option chains with greeks, expiry lists and the instrument master.

POST /v1/charts/intraday
POST /v1/optionchain
GET /v1/instruments/master

Trader's Control

A risk layer above the OMS: kill switch, daily loss limits and order-modification caps — enforced server-side.

POST /v1/killswitch
POST /v1/traderscontrol

Integration

Your first order in four lines

# 1 · get a sandbox token
curl -X POST https://smifsgq.smifs.com/v1/auth/token/issue \
  -H 'Content-Type: application/json' \
  -d '{"clientId":"you"}'

# 2 · place a paper order
curl -X POST https://smifsgq.smifs.com/v1/orders \
  -H "access-token: $TOKEN" -H 'Content-Type: application/json' \
  -d '{"transactionType":"BUY","exchangeSegment":"NSE_EQ",
       "productType":"INTRADAY","orderType":"MARKET",
       "validity":"DAY","securityId":"11536","quantity":1}'

from smifsgq import GodQuant

gq = GodQuant.sandbox(client_id="you")          # issues a token
order = gq.place_order(security_id="11536",     # TCS
                       exchange_segment="NSE_EQ",
                       transaction_type="BUY",
                       quantity=1, order_type="MARKET",
                       product_type="INTRADAY")
print(order["orderId"], gq.funds()["availableBalance"])

// .mcp.json — give Claude a trading desk
{
  "mcpServers": {
    "smifsgq": {
      "command": "python",
      "args": ["-m", "smifsgq_mcp"],
      "env": { "SMIFSGQ_BASE_URL": "https://smifsgq.smifs.com",
               "SMIFSGQ_CLIENT_ID": "you" }
    }
  }
}

// then, in Claude:
// "Buy 1 TCS at market and show my positions."

Model Context Protocol

Plug an AI into the desk

God Quant ships an MCP server that exposes the whole API — orders, quotes, portfolio, risk controls — as typed tools any MCP client can call: Claude, Claude Code, or your own agent stack.

17 tools covering the full v1 surface
SKILL.md teaches agents venue rules and error codes
Paper-first — agents practice on the sandbox before real capital
Kill switch stays server-side, out of the model's hands

Get the MCP server Tool schemas →

Why God Quant

Built like a risk desk, priced like a utility

Sandbox is the front door

Every account starts on the paper venue with ₹10,00,000 of practice capital and a synthetic NSE/MCX universe ticking every 500 ms. Same endpoints, same error codes, zero risk.

Server-side risk engine

Kill switch, daily-loss exits and modification caps run on the venue — not in your client code.

Familiar by design

Request and response shapes follow the conventions Indian algo developers already know, so existing bots port in minutes.

Wrappers included

Python SDK and MCP server maintained in the same repo as the API — versioned together.

Honest limits

10 orders/sec, 7,000/day, 5 data calls/sec per client — enforced and documented. When we raise them, the changelog says so.

Questions

Frequently asked

Is this live trading?

Not yet. The developer preview runs entirely on a paper venue with synthetic market data. Live NSE/BSE/MCX connectivity through the SMIFS OMS ships next, behind the same API contract — code written against the sandbox carries over unchanged.

How do I authenticate?

POST your client id to /v1/auth/token/issue and pass the returned JWT in the access-token header on every call. Tokens live 24 hours. The production portal will replace open issuance with login-based consent.

What can the MCP server do?

Everything the REST API can: place and manage orders, read quotes and option chains, inspect positions, funds and margins, and arm the kill switch. Each capability is a typed MCP tool, and the bundled SKILL.md teaches agents the venue's rules before they trade.

Will my existing trading bot port easily?

Largely yes. Endpoint paths, order payloads and error envelopes follow conventions common to mainstream Indian broker APIs, so most bots need only host, auth and small field changes — all listed in the API reference.

What does it cost?

API access is free in the developer preview. Live trading, when it arrives, is charged as standard SMIFS brokerage — the API itself stays ₹0.

Ship your first strategy this afternoon.

Get a sandbox token Read the reference

The broking desk,now an API.