generated: '2026-08-09'
method: searched
source:
  - https://status.infoway.io
  - https://infoway.readme.io/reference/api-endpoints.md
  - https://infoway.readme.io/reference/api-key-application.md
  - https://blog.infoway.io/en/
  - openapi/infoway-real-time-market-data-api-openapi.yml

versioning:
  scheme: uri-path (partial)
  current: mixed — unversioned v1 paths alongside a /v2/ family
  detail: >-
    Basic/reference and original market-data paths carry no version segment
    (/common/basic/symbols, /stock/batch_trade/{codes}). The newer batch K-line form and the whole
    analytical family are under v2 (/{prefix}/v2/batch_kline, /common/v2/basic/market/...,
    /common/v2/basic/plate/..., /common/v2/basic/stock/...). Infoway publishes no written versioning policy
    describing how the two coexist or how long v1 is supported.
  policy_url: null
  docs: https://infoway.readme.io/reference/api-endpoints

deprecation:
  policy_url: null
  policy_published: false
  sunset_header: unknown — not documented
  deprecation_header: unknown — not documented
  note: >-
    No deprecation or sunset policy was found on the docs host, the ReadMe hub, the marketing site or the
    GitHub repositories. RFC 8594 Sunset/Deprecation header support is not documented either way.

deprecated_operations: []
deprecated_operations_note: >-
  No operation in openapi/infoway-real-time-market-data-api-openapi.yml carries `deprecated: true`.

sla:
  url: null
  uptime_target: null
  note: >-
    No published SLA or uptime commitment was found. The quick-start does state that where an Infoway-side
    problem affects a customer, additional validity period is offered as compensation
    (https://infoway.readme.io/reference/quick-start.md) — a goodwill statement, not an SLA.

status_page: https://status.infoway.io
status_page_note: >-
  Live and provider-operated ("Status Page | 服务状态 | infoway"). The component/incident data is rendered
  client-side by a Vue app, so current state is not machine-readable — /api/status and /data.json both
  return the SPA shell rather than JSON.

changelog:
  url: null
  published: false
  note: >-
    No dated changelog or release-notes page exists. Feature launches are announced as blog posts
    (e.g. "Infoway Korean Stock Market Data API Is Now Live", 2026-06-24) and none of the five GitHub SDK
    repositories has published a GitHub Release. No changelog/ artifact was written.

lifecycle_events:
  - date: '2026-06-24'
    event: Korean stock market data API launched
    source: https://blog.infoway.io/en/infoway-korean-stock-market-data-api-now-live/
    kind: capability-added

plan_lifecycle:
  source: https://infoway.readme.io/reference/api-key-application.md
  renewal: All paid plans support renewal from the dashboard.
  upgrade: >-
    Upgrades are one-way up the ladder (Basic -> Advanced/Professional, Advanced -> Professional);
    Professional cannot be upgraded. The customer pays the pro-rated difference for the remaining term.
  keys: One distinct API key per plan; an account may hold several plans concurrently.

x-evidence:
  fetched: '2026-08-09'
  urls:
    - {url: 'https://status.infoway.io', http_status: 200}
    - {url: 'https://status.infoway.io/api/status', http_status: 200, note: 'returns the SPA shell, not JSON'}
    - {url: 'https://infoway.io/status', http_status: 404}
    - {url: 'https://blog.infoway.io/en/category/changelog/', http_status: 404}
    - {url: 'https://api.github.com/repos/infoway-api/infoway-sdk-python/releases', http_status: 200, note: 'empty array — no releases'}