Hong Kong Stock Market API integration (HKEX · SSE · SZSE)

Quote snapshot API

Pulls the tabbed quote screen for stocks and indices. Returns last price, bid/ask (where available), change, change %, turnover, lot size, and trading status for any HKEX/SSE/SZSE ticker. Use case: feeding a self-built watchlist widget on an intranet portal without paying for a full HKEX Orion Market Data licence.

Index tracker API

Focused endpoint for HSI, HSCEI, HSTECH, SSE Composite, SZSE Component and sectoral indices surfaced in the app. Returns level, previous close, daily range, and percentage change. Use case: index-change notifications for wealth-management newsletters and Slack/Teams bots.

Portfolio & watchlist sync

Mirrors the “add / remove” behaviour of the customizable list plus portfolio performance. Endpoints: GET /watchlist, POST /watchlist/items, GET /portfolio/performance. Use case: sync a retail investor’s watchlist into a CRM or robo-advisor onboarding flow.

Historical chart-series API

Returns OHLCV arrays for day, week, month, and year windows, matching the full-screen charts in the app. Use case: powering a Python / R notebook for pair-trade backtests between dual-listed Hong Kong and Mainland names.

ETF metadata feed

Exchange-traded fund ticker list, quote snapshot, and latest NAV proxy. Use case: feeding a thematic ETF monitor into a family-office dashboard alongside OpenFinance bank balance data.

News ingestion endpoint

Pulls the “Support for News related to stocks” surface, returning headline, timestamp, related ticker(s), and source URL. Use case: sentiment analysis pipelines that tag news against portfolio holdings.

1. Family office research desk

Context: a boutique family office in Singapore covers Greater China equities and wants a single programmatic source for HKEX + SSE + SZSE. Data used: quote snapshot API, index tracker API, historical chart-series API. OpenFinance mapping: mirrors the OpenBanking “account information service” pattern — the end user authorizes read-only access to the app’s data surface, and we deliver a token-gated REST API that plugs directly into the firm’s internal research stack.

2. Robo-advisor onboarding with watchlist import

Context: a Hong Kong robo-advisor wants new clients to import their existing watchlist on sign-up rather than retyping tickers. Data used: portfolio & watchlist sync endpoints. OpenFinance mapping: consent-based data portability — the user opts in, we exchange app credentials for a short-lived token, pull the watchlist, and hand it to the advisor’s onboarding API in a normalized JSON shape compatible with FIX symbology.

3. Compliance-grade audit trail for a fund

Context: an SFC-licensed Type 9 asset manager needs evidence that staff watchlists are covered by the firm’s personal account dealing policy. Data used: watchlist export + timestamped delta log. OpenFinance mapping: aligned with SFC’s “Data Standards for Order Life Cycles” expectations — our wrapper emits append-only, timestamped records suitable for WINGS-style submission or internal e-discovery.

4. Chart-backed backtesting API

Context: a quant consultancy wants a uniform daily/weekly/monthly candle series across HK main board and A-shares. Data used: historical chart-series API, with adjustments for splits and dividends from a public reference. OpenFinance mapping: data-as-a-service endpoint, billed per call, so the consultancy pays only for the universe and window they actually read.

5. News-driven alert bot

Context: a corporate treasury team running an HKD/CNH cash book wants alerts when HSI constituents publish price-sensitive news. Data used: news ingestion endpoint + index tracker API as a cross-check. OpenFinance mapping: webhook-driven event stream that plugs into Microsoft Teams or PagerDuty; aligns with the OpenData idea of “push-based entitlements” rather than constant polling.

Quote snapshot endpoint

// GET /api/v1/hkstocks/quote
GET /api/v1/hkstocks/quote?symbol=0700.HK
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "symbol": "0700.HK",
  "name": "Tencent Holdings",
  "last": 312.40,
  "change": 2.60,
  "change_pct": 0.84,
  "turnover": 4123456789,
  "lot_size": 100,
  "exchange": "SEHK",
  "ts": "2025-10-14T06:02:11Z"
}

Historical candles (weekly)

// GET /api/v1/hkstocks/candles
GET /api/v1/hkstocks/candles
    ?symbol=000001.SZ&interval=1w&limit=52
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "symbol": "000001.SZ",
  "interval": "1w",
  "candles": [
    { "t":"2025-09-29","o":12.30,"h":12.85,"l":12.10,"c":12.72,"v":318299100 },
    { "t":"2025-10-06","o":12.70,"h":13.10,"l":12.55,"c":12.98,"v":289144000 }
  ]
}

Watchlist sync + webhook

// POST /api/v1/hkstocks/watchlist/sync
POST /api/v1/hkstocks/watchlist/sync
Authorization: Bearer <ACCESS_TOKEN>
Content-Type: application/json

{
  "user_ref": "robo-7f31",
  "items": [
    { "symbol":"0005.HK","action":"add" },
    { "symbol":"600519.SS","action":"add" },
    { "symbol":"0939.HK","action":"remove" }
  ],
  "webhook": "https://your.app/hooks/hkstocks"
}

// Error handling
4xx body: { "error":"INVALID_SYMBOL",
            "detail":"9999.HK not listed on SEHK",
            "request_id":"req_01HS..." }

Deliverables checklist

• API specification (OpenAPI / Swagger) covering every endpoint above
• Protocol and auth-flow report (session tokens, signing, refresh) for mdr.stocks.hkg
• Runnable source code for quote, index, watchlist, candle, ETF, and news APIs (Python / Node.js / Go on request)
• Automated test suite and Postman / Insomnia collection
• Compliance pack: consent templates, PDPO data inventory, SFC-aligned retention notes
• Deployment recipe (Docker compose / Kubernetes manifests) and on-call runbook

Engagement models

1) Source code delivery from $300. We hand over the runnable API source, documentation, and test harness; you pay only after delivery and only if you are satisfied.

2) Pay-per-call API billing. Use our hosted endpoints directly; no upfront fee, and you pay only for calls actually made. Ideal if you want to prototype against HSI/SSE/SZSE data before committing to a full codebase purchase.

Key integration scenarios at a glance

Account-less quote ingestion, watchlist and portfolio export, chart-series backtesting, ETF thematic dashboards, news-driven alerts, SFC-aligned audit trails, and cross-broker merging with Futubull / Webull / Tiger Brokers through a single wrapper.

About us

We are an independent interface-integration studio focused on fintech, OpenData, and OpenFinance. Our team has shipped production systems for brokerages, family offices, and B2B research desks, and we are fluent in protocol analysis, TLS inspection under authorized conditions, and API productization. For Hong Kong equity work specifically, we combine familiarity with HKEX OMD-C documentation, SFC data-submission practice, and retail-app structures like mdr.stocks.hkg.

• Markets covered: SEHK, SSE, SZSE, plus dual-listings, ETFs, and sectoral indices
• Tech stack: Python / Node.js / Go, PostgreSQL, ClickHouse, Kafka, Redis
• Process: protocol analysis → API design → build → validation → compliance sign-off
• Source code delivery from $300 — runnable source and full docs; pay after delivery upon satisfaction
• Pay-per-call API billing — use hosted endpoints, pay only for calls, no upfront commitment

Contact

Provide the target app (Hong Kong Stock Market / mdr.stocks.hkg) and the specific data you need — quotes, portfolio, candles, news, or a combination — and we will respond with scope, timeline, and a fixed quote.

Contact page

Engagement workflow

1. Scope confirmation: which surfaces of the Hong Kong Stock Market app you need (quotes, indices, portfolio, charts, ETFs, news).
2. Protocol analysis and API design (2–5 business days, complexity-dependent).
3. Build and internal validation against a live tester device (3–8 business days).
4. Documentation, OpenAPI spec, Postman collection, and compliance notes (1–2 business days).
5. Typical first delivery: 5–15 business days; HKEX entitlement reviews or Stock Connect MMDH rules may extend timelines.

FAQ

What do you need from me to start?

How long does a first drop usually take?

How do you handle compliance?

Do I need a separate market-data licence?