Skip to content
AllTick
API Selection

HK Stock API: Integration Checklist

Essential checks before integrating Hong Kong equities: ticker formatting (700.HK), trading sessions, lunch breaks, holidays, and licensing.

Updated:
Maintained by:AllTick Technical Team
Audience:Developers integrating Hong Kong stock market feeds into trading apps or quant workflows

Core Takeaway · 30-Second Brief

Before integrating Hong Kong stock data, confirm four essentials: exact symbol formatting in the API (such as whether leading zeros are stripped in 700.HK), how morning/afternoon sessions and the lunch break appear in feeds, HKEX holiday and severe weather schedules, and end-user display permissions.

01

Symbol Formatting: The Most Common Pitfall

Hong Kong equities are identified by numeric codes—for example, Tencent Holdings is 00700 on HKEX. Different data providers format this as 00700, 700, 700.HK, or 0700.HK. In AllTick, Tencent is written as 700.HK. Always verify against the official symbol list rather than guessing string rules.

FormatCommon ContextIntegration Risk
00700Exchange & brokerage terminalsMay return empty results if passed directly to API
700.HKAllTick API conventionLeading zeros are stripped before the .HK suffix
0700.HKCertain third-party terminalsMixing with 700.HK creates duplicate symbol records

02

Trading Sessions and Market Breaks

  • HKEX operates separate morning and afternoon continuous trading sessions separated by a midday lunch break; zero new trades during lunch is normal.
  • Pre-opening and closing auction sessions have distinct tick behavior compared to continuous trading.
  • Public holidays can create full-day or half-day closures. Since 23 September 2024, HKEX severe-weather trading continues under its published rules; a typhoon warning alone is not a closure signal.
  • K-line feeds do not generate new bars during market breaks—do not trigger false data-outage alerts during lunch.

03

HK Equities Integration Checklist

1Run a live trade-tick query with 1–2 liquid symbols (such as 700.HK).
2Verify the response timestamp unit and convert to Asia/Hong_Kong time to confirm alignment.
3Observe WebSocket behavior during the midday lunch break to ensure idle streams are handled gracefully.
4Check that required K-line intervals and historical bar counts fit within your plan tier.
5Confirm whether your subscription covers internal research or public end-user display.

Sources & Verification · 2026-10-13

Relevant endpoint, field, and exchange rules were checked against the primary specifications linked below.

Authenticated AllTick requests and production end-to-end tests were not run for this review. Record your token plan, library versions, market session, ret/trace, and observed results when reproducing these checks.

Reproduce before deployment

  • Check the exact HK symbol, morning session, 12:00–13:00 HKT lunch break, and afternoon session. Distinguish an unchanged closed-session trade timestamp from connection failure.
  • HKEX severe-weather trading began on 23 September 2024. Do not infer suspension from a typhoon warning alone; check the exchange announcement and applicable product session.