Market Status & Trading Hours API - US, EU, Asia Exchanges avatar

Market Status & Trading Hours API - US, EU, Asia Exchanges

Pricing

$1.00 / 1,000 status rows

Go to Apify Store
Market Status & Trading Hours API - US, EU, Asia Exchanges

Market Status & Trading Hours API - US, EU, Asia Exchanges

Is the stock market open right now? DST-correct open/closed status, trading hours, holidays and early closes for NYSE, NASDAQ, CME, LSE, XETRA, JPX and HKEX. Computed 2026-27 calendars, next open/close in UTC, normalized JSON per exchange.

Pricing

$1.00 / 1,000 status rows

Rating

0.0

(0)

Developer

kyle herman

kyle herman

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

Market Status & Trading Hours API — NYSE, NASDAQ, CME, LSE, XETRA, JPX, HKEX

Is the stock market open right now? This actor answers that question — correctly, across time zones and DST changes — for seven major world exchanges, and gives you machine-readable trading hours, stock market holidays 2026-2027 and early-close days as normalized JSON.

A lightweight, dependency-free market status API / trading hours API: no scraping, no external calls. Everything is computed from embedded, curated exchange calendars with DST-correct session logic (Python zoneinfo).

Supported exchanges

CodeExchangeTimezoneRegular session (local)
NYSENew York Stock ExchangeAmerica/New_York09:30–16:00
NASDAQNASDAQ Stock MarketAmerica/New_York09:30–16:00
CMECME Globex (equity index futures)America/ChicagoSun 17:00 → Fri 16:00, daily 16:00–17:00 break
LSELondon Stock ExchangeEurope/London08:00–16:30
XETRADeutsche Börse XetraEurope/Berlin09:00–17:30
JPXJapan Exchange (TSE)Asia/Tokyo09:00–11:30, 12:30–15:30 (lunch break)
HKEXHong Kong ExchangesAsia/Hong_Kong09:30–12:00, 13:00–16:00 (lunch break)

Input

All fields optional — run with {} to get all exchanges.

{
"exchanges": ["NYSE", "LSE", "JPX"],
"days_ahead": 30
}
  • exchanges — array of codes; empty = all seven.
  • days_ahead — horizon for upcoming_holidays (default 30).

Output — one row per exchange

{
"exchange": "NYSE",
"exchange_name": "New York Stock Exchange",
"timezone": "America/New_York",
"local_time": "2026-09-02T18:10:44-04:00",
"is_open_now": false,
"current_session": "closed",
"next_open_utc": "2026-09-03T13:30:00Z",
"next_close_utc": "2026-09-03T20:00:00Z",
"today_is_holiday": false,
"holiday_name": null,
"early_close_today": false,
"upcoming_holidays": [
{ "date": "2026-09-07", "name": "Labor Day", "type": "closed", "confidence": "verified" }
],
"sessions": [{ "open_local": "09:30", "close_local": "16:00" }],
"as_of_utc": "2026-09-02T22:10:44Z",
"confidence": "verified"
}

current_session is one of regular, early_close_day, lunch_break, closed. JPX and HKEX lunch breaks are modeled explicitly, so at 12:00 Tokyo time you get lunch_break, not a false "open".

What's handled correctly

  • DST transitions — sessions are defined in local exchange time and converted via IANA tz data, so next_open_utc shifts automatically when New York, London, or Berlin change clocks (Tokyo and Hong Kong don't observe DST — also handled).
  • Early closes — US 1:00 pm ET closes (Black Friday, Christmas Eve), LSE 12:30 pm closes (Dec 24 / Dec 31), HKEX half-days (morning session only), CME 12:15 pm CT holiday halts.
  • Observed/substitute holidays — e.g. July 4, 2026 (Saturday) → NYSE closed Friday July 3; UK Boxing Day 2026 → substitute Monday Dec 28.
  • Overnight futures sessions — CME Globex Sun 17:00 → Fri 16:00 CT with the daily maintenance break.
  • Honest confidence flags — deterministic dates are "verified"; lunar-calendar holidays (HK Lunar New Year, Buddha's Birthday, Dragon Boat, Mid-Autumn, Chung Yeung) and product-dependent CME early closes are "estimated". We flag uncertainty instead of faking precision.

Use cases

  • Gate trading bots / order routers: don't send orders when the venue is closed.
  • "Market open/close" countdowns and dashboards.
  • Scheduling data pipelines around exchange sessions and stock market holidays 2026.
  • Normalized multi-region calendar for fintech apps.

Why this instead of a free US-only endpoint?

Free options exist for US markets only (e.g. Polygon's market status endpoint). This actor's value is multi-exchange, normalized coverage — one schema across US, UK, German, Japanese and Hong Kong venues, with lunch breaks, half-days, and substitute-holiday logic that generic holiday APIs get wrong.

Notes & limitations

  • Calendars embedded for 2026–2027. Outside that window, weekday/session logic still works but holiday flags are unavailable.
  • Ad-hoc closures (mourning days, disasters, typhoon signals at HKEX) cannot be predicted — always confirm with the exchange for anything money-critical.
  • CME rows are always "estimated": Globex holiday schedules vary by product group.

Pricing

Pay-per-event: one status-row charge per exchange row pushed. A default run (all 7 exchanges) costs 7 events.