Dhanush: Demat, Stocks & IPOs — API integration services

Deliverables checklist

• API specification (OpenAPI / Swagger) for every delivered endpoint
• Protocol & auth-flow report — login, OTP/2FA, token refresh, cookie/header chain, request signing
• Runnable source for login, holdings and statement APIs in Python and Node.js
• Automated test suite + Postman / HTTP collection
• Compliance guidance — KYC/PAN handling, consent capture, retention and data-minimization notes
• Optional: webhook/poller service for IPO allotment and order-status events

Feature module — Holdings & positions sync

A holdings API returns ISIN, symbol, quantity, average price, last traded price and unrealised P&L; a positions API covers intraday and carry-forward F&O legs. Concrete use: nightly reconciliation against the depository statement and a unified net-worth view across the client's other broker accounts.

Feature module — IPO allotment tracker

An IPO API exposes the open/upcoming issue list, bid lots, ASBA/UPI mandate reference and allotment outcome. Concrete use: an advisory app that pushes "allotted / not allotted" alerts the moment registrar data updates, instead of users refreshing the app.

Feature module — Mutual fund & SIP data

A mutual fund API lists folios, scheme codes, units, NAV-based current value and the SIP calendar (amount, next debit date, frequency). Concrete use: feeding a goal-tracking tool or a CA's capital-gains workbook with direct-plan transactions.

Feature module — Market data & option chain

A quotes API returns LTP, bid/ask, OHLC and volume for NSE/BSE/MCX/NCDEX instruments; an option-chain API returns strikes, expiries, OI and IV. Concrete use: a strategy backtester or a watchlist widget pinning up to 50 instruments, mirroring the app's own pinned-instrument behaviour.

Feature module — Ledger & statement export

A statement API pulls the funds ledger, contract notes and charges with date-range paging and filters by segment. Concrete use: exporting to Excel/CSV for GST/brokerage reconciliation or to a PDF pack for an audit file.

1 · Unified portfolio dashboard

Context: a wealth-tech product wants one screen across several Indian brokers. Data/API: GET /holdings + GET /positions + GET /mf/folios, refreshed post-market. OpenFinance mapping: the same "consented account information" pattern as RBI Account Aggregator — read-only, scoped, revocable — applied to a broking app rather than a bank.

2 · IPO allotment notification engine

Context: an advisory app promises instant allotment alerts. Data/API: poll GET /ipo/applications?status=allotment against the issue calendar from GET /ipo/open; emit a webhook on status change. OpenData mapping: turning an in-app status screen into an event stream other systems can subscribe to.

3 · Tax & reconciliation export

Context: a CA platform needs a client's full-year trades and charges. Data/API: POST /statement with from_date/to_date, paging through contract notes and ledger entries; export CSV + PDF. OpenFinance mapping: machine-readable statements, the broking equivalent of an OpenBanking transactions endpoint.

4 · Algo & strategy tooling

Context: a quant desk runs strategies on NSE/BSE/MCX symbols. Data/API: GET /quotes + GET /optionchain for inputs, GET /orders for fills; static-IP and rate-limit handling baked in. OpenData mapping: exposing market and execution state through a documented contract instead of screen scraping.

5 · Household / family aggregation

Context: a family-office tool tracks several Dhanush logins (the app supports up to 3 linked trading accounts with 2FA switching). Data/API: per-account POST /login → token, then fan-out GET /holdings; merge by ISIN. OpenFinance mapping: multi-account consent orchestration with per-account token lifecycles.

1 · Login + 2FA → access token

POST /api/v1/dhanush/login
Content-Type: application/json

{
  "client_code": "AB1234",
  "password": "<secret>",
  "totp": "482915"          // 2FA, app supports up to 3 linked accounts
}

200 OK
{
  "access_token": "eyJhbGci...",
  "refresh_token": "rt_8f2a...",
  "expires_in": 3600,
  "segments": ["CM","FO","CDX"]
}

2 · Holdings & positions

GET /api/v1/dhanush/holdings
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "as_of": "2026-05-11T16:05:00+05:30",
  "holdings": [
    {"isin":"INE002A01018","symbol":"RELIANCE",
     "qty":40,"avg_price":2410.5,"ltp":2887.0,
     "pnl":19060.0,"exchange":"NSE"}
  ]
}
# Errors: 401 token_expired -> call /refresh; 429 rate_limited -> backoff

3 · IPO allotment status

POST /api/v1/dhanush/ipo/status
Authorization: Bearer <ACCESS_TOKEN>
Content-Type: application/json

{ "issue_id": "IPO-2026-042" }

200 OK
{
  "issue":"ExampleTech Ltd",
  "applied_lots":2,"cutoff_price":188,
  "mandate_ref":"UPI/ASBA/9921...",
  "status":"ALLOTTED","allotted_qty":75
}

4 · Statement export + webhook

POST /api/v1/dhanush/statement
Authorization: Bearer <ACCESS_TOKEN>
{ "from_date":"2025-04-01","to_date":"2026-03-31",
  "segment":"ALL","format":"csv" }

202 Accepted -> { "job_id":"stmt_7712" }

# When ready, we POST to your callback:
POST https://your-app/webhooks/dhanush
{ "job_id":"stmt_7712","status":"done",
  "download_url":"https://.../stmt_7712.csv","rows":1284 }

Regulatory alignment

Dhanush operates under SEBI registration as a stock broker and depository participant; integrations follow SEBI's broker technology and API-trading guidance — note that a static IP becomes mandatory for API-based trading from 1 April 2026, which we account for in deployment design. Account-information style read access is built on the RBI Account Aggregator consent model: scoped, time-bound, revocable. Personal data handling follows India's Digital Personal Data Protection Act, 2023, and we apply data minimization, consent logging and defined retention.

How we work

• Only under client authorization or documented public/authorized APIs — no unauthorized access
• Reverse engineering of the app's own protocol is used to document the contract, not to bypass security
• Consent records, request logging and audit hooks shipped with the integration
• Secrets never logged or committed; NDAs signed on request
• PAN, KYC and contact fields treated as sensitive; masked in logs and exports by default

• Zerodha Kite — holds holdings, positions, order/trade book and historical candles; Kite Connect is a reference point for what a documented broking API looks like. Users who also work with Kite often want unified portfolio exports across both platforms.
• Upstox — stores demat holdings, F&O positions and order history; teams integrating Upstox typically need the same normalised P&L view as Dhanush.
• Groww — keeps stocks, mutual fund folios and SIP schedules; a common ask is merging Groww MF data with a Dhanush demat view in one dashboard.
• Angel One — holds positions, order book and research/advisory data; relevant when an aggregator wants advisory plus execution state side by side.
• 5paisa — stores trades, ledger and IPO applications; appears when clients reconcile multi-broker contract notes for tax.

• ICICI Direct — holds holdings, ledger and a bank-linked funding flow (Breeze API); relevant for banking-plus-broking aggregation.
• Motilal Oswal (MO Investor) — stores portfolios, research calls and order history; pairs naturally with Dhanush's own research-call section.
• HDFC Sky — keeps stocks, F&O positions and statements; another candidate for the same statement-export contract.
• Dhan — holds positions, order book and option-chain data with TradingView charts; often integrated alongside Dhanush for traders running multi-broker strategies.
• Paytm Money — stores demat holdings, mutual fund folios and SIPs plus a UPI funding rail; relevant when an integration needs both investment data and payment context.

About us

OpenFinance Lab is an independent studio focused on fintech and open-data API integration. Our engineers come from broking, banking, payment-gateway and protocol-analysis backgrounds, and we know SEBI, RBI and depository (NSDL/CDSL) expectations alongside multi-region privacy rules. We ship end-to-end financial APIs under security and compliance constraints — from protocol analysis through build, validation and compliance review.

• Broking, digital banking, mutual funds, insurtech and cross-border clearing
• Enterprise API gateways, rate-limit/static-IP handling and security reviews
• Custom Python / Node.js / Go SDKs and automated test harnesses
• Full pipeline: protocol analysis → build → validation → compliance
• Source code delivery from $300 — runnable API source plus full documentation; pay after delivery upon satisfaction
• Pay-per-call API billing — hosted endpoints, pay only per call, no upfront cost

Contact

For a quote, send us the target app (Dhanush: Demat, Stocks & IPOs) and the data you need — holdings, order book, IPO allotment, ledger, mutual fund folios — plus where you'll call from. We reply with scope, timeline and price.

Contact page

Engagement workflow

1. Scope confirmation — integration scenarios and endpoints (login, holdings, orders, IPO, statements, MF)
2. Authorization check — confirm you control the accounts or have documented API access
3. Protocol analysis & API design (2–5 business days, complexity-dependent)
4. Build & internal validation (3–8 business days)
5. Docs, samples and test cases (1–2 business days)
6. First delivery typically 5–15 business days; exchange or vendor approvals may extend it

FAQ

What do you need from me to start a Dhanush integration?

How long does delivery take?

How do you handle compliance for Indian broking data?

Can you export portfolio and tax data to Excel or accounting tools?