SMC Ace API integration: demat holdings, orders & IPO OpenData services

A retail-investor data goldmine

India crossed 18 crore demat accounts in 2025 and the SEBI-licensed Account Aggregator framework now lets depositories act as Financial Information Providers (FIPs). SMC Ace sits squarely inside that data plane: every authenticated session exposes holdings, executed trades, fund ledger, mutual fund folios, and IPO allotments. For a wealth-tech, neobank, or compliance vendor, that is high-signal structured data — far richer than scraping price screens.

Our role is to wrap those data flows in a stable, documented API. The customer brings the SMC Ace credentials or a signed authorization; we deliver the pipeline.

What changed in the last 24 months

• October 2024 — Buy & Sell Slider added for one-gesture order placement; impacts how order intents must be modelled in any API mirror.
• 2024-2025 — Light/Dark theme, Position Widget on Dashboard, in-app browser for IPO pages, and ReKYC-via-App for dormant users; the ReKYC flow especially matters when re-authorizing data pulls.
• February 2025 — SEBI permitted Associations of Persons to open demat accounts in their own name, opening up a new B2B integration surface our APIs already account for.
• 2025 — Mutual fund stack inside SMC Ace 2.0 became mainstream alongside SIP automation, raising demand for unified MF + equity APIs.

Scenario A — Wealth aggregation across multiple brokers

Context: A personal-finance app wants one screen showing equities at SMC Ace, mutual funds at multiple AMCs, and bank balances. Data & APIs: SMC Ace holdings + funds ledger, plus AMFI scheme metadata. OpenData mapping: Holdings normalized into the SEBI Account Aggregator FIU schema for securities, with consent IDs persisted per pull.

Scenario B — Capital-gains automation for tax season

Context: A CA SaaS platform must compute STCG/LTCG for thousands of clients before 31 July. Data & APIs: SMC Ace trade book with buy/sell pairs, plus contract notes. OpenData mapping: Mirrors the CDSL/NSDL eCAS layout so the same parser already used for AA-supplied statements ingests SMC Ace data unchanged.

Scenario C — IPO tracker for retail communities

Context: A creator-led IPO app shows live subscription, GMP, and allotment per user. Data & APIs: SMC Ace IPO module + funds-ledger ASBA blocks. OpenData mapping: Allotment events streamed via webhook so the user sees credit on the same day NSDL/CDSL push the corporate action.

Scenario D — SIP & goal-based advisor backend

Context: A roboadvisor pulls existing SIPs to avoid double-prescribing the same scheme. Data & APIs: SMC Ace mutual fund folios, SIP schedule, and units. OpenData mapping: Output normalized to BSE StAR MF and MFU field names for advisors that already consume those feeds.

Scenario E — B2B compliance & surveillance

Context: A regulated entity needs daily evidence that employee personal trading respects internal trade-window rules. Data & APIs: SMC Ace order and trade book under written authorization. OpenData mapping: Daily ledger snapshots written to a tamper-evident log, retained per the firm’s SEBI surveillance policy.

Login & session token

POST /api/v1/smc-ace/auth/login
Content-Type: application/json

{
  "client_code": "SMC1234567",
  "password": "<encrypted>",
  "totp": "482931",
  "device_id": "uuid-v4"
}

200 OK
{
  "session_token": "eyJhbGciOi...",
  "expires_in": 3600,
  "refresh_token": "rt_2f8a...",
  "rekyc_required": false,
  "segments": ["CASH","FNO","CUR","COM","MF"]
}

Holdings query

GET /api/v1/smc-ace/portfolio/holdings
Authorization: Bearer <session_token>

200 OK
{
  "as_of": "2026-04-28T09:21:00+05:30",
  "holdings": [
    {
      "isin": "INE002A01018",
      "symbol": "RELIANCE",
      "exchange": "NSE",
      "quantity": 42,
      "avg_price": 2780.55,
      "ltp": 2914.30,
      "pnl": 5617.50,
      "product": "CNC"
    }
  ]
}

Trade book / contract-note feed

GET /api/v1/smc-ace/orders/trades
  ?from=2026-04-01&to=2026-04-28&segment=FNO
Authorization: Bearer <session_token>

200 OK
{
  "trades": [
    {
      "trade_id": "T2604001892",
      "order_id": "O2604001771",
      "symbol": "NIFTY26APR22500CE",
      "exchange": "NFO",
      "side": "BUY",
      "qty": 50,
      "price": 142.55,
      "brokerage": 20.0,
      "stt": 7.13,
      "executed_at": "2026-04-26T10:14:55+05:30"
    }
  ],
  "next_cursor": null
}

IPO allotment webhook

POST https://customer.example/webhooks/smc-ace/ipo
X-Signature: sha256=ad4e9c...

{
  "event": "ipo.allotment.updated",
  "user_id": "u_8821",
  "ipo": {
    "symbol": "ACMESOL",
    "lot_applied": 2,
    "amount_blocked": 28980,
    "status": "ALLOTTED",
    "shares_credited": 65,
    "credited_at": "2026-04-27"
  }
}

Regulatory anchors

• SEBI — SMC Global Securities is a SEBI-registered intermediary (INZ000199438); we do not mirror or impersonate broker functions, only consume data the user is already entitled to see.
• SEBI Account Aggregator framework — for clients who prefer the regulated path, our pipeline can be re-routed through licensed AAs such as CAMSfinserv or Finvu so depositories (NSDL/CDSL) act as FIPs and our customer becomes the FIU.
• Digital Personal Data Protection Act (DPDP), 2023 — consent capture, purpose limitation, and the user’s right to withdraw are enforced at the API layer; consent records are retained alongside every pull.
• RBI & PMLA — KYC artefacts (PAN, Aadhaar masked) are never re-distributed; data is encrypted in transit (TLS 1.2+) and at rest (AES-256).

What this means in practice

We sign a written engagement letter that names the data scopes (e.g. holdings + trades), the user-authorization channel (in-app TOTP and explicit consent screen), the retention window, and the deletion guarantee. Where the customer prefers the SEBI AA route, we expose the same downstream API but switch the upstream connector — the application code does not need to change.

About our studio

We are an independent technical studio specializing in App interface integration and authorized API integration. Our team has shipped trading, payments, and OpenBanking integrations across India, Southeast Asia, the Middle East, and Latin America. For SMC Ace specifically, our engineers combine NSE/BSE market plumbing with hands-on experience in SEBI Account Aggregator deployments — so we can deliver either a self-hosted source-code drop or a managed pay-per-call gateway, whichever fits your governance.

• Protocol analysis · reverse engineering · data extraction
• OpenAPI spec, Python / Node.js / Go SDKs, test harnesses
• SEBI AA, NSDL/CDSL FIP, BSE StAR MF familiarity
• Source-code delivery from $300 — pay after delivery upon satisfaction
• Pay-per-call hosted API — no upfront cost; ideal for usage-based budgets

Contact

Send us your target app name (already provided: SMC Ace) and the exact data scopes you need — for example, “daily holdings + trade book for tax workflow” or “IPO allotment webhook for retail community”. We respond with a fixed-price quote and a delivery date.

Open contact page

Engagement options: source-code delivery from $300, or pay-per-call API with no upfront fee.

Engagement workflow

1. Scope confirmation — data types (holdings, orders, trades, MF, IPO), volume, and consent path (direct or SEBI AA).
2. Protocol analysis & API design — 2–5 business days.
3. Build & sandbox validation against a real SMC Ace test account — 3–8 business days.
4. Documentation, sample apps, and test cases — 1–2 business days.
5. Typical first delivery 5–15 business days; AA-routed deployments may add 1–2 weeks for FIU onboarding.

FAQ

Do you need my SMC Ace credentials?

Can the same API also cover Zerodha, Upstox, or Groww?

How do you handle SEBI surveillance & DPDP?