Bringing iWow愛挖寶's quotes, watchlists and news into your own system

Open iWow愛挖寶 and the screen that actually carries value is the self-selected watchlist — a per-account list of Taiwan and US symbols that follows the user across devices, wrapped around a live quote stream and an intraday push feed. That is the part worth integrating. The headline real-time quotes are licensed exchange numbers; the personalization layered on top of them — what a given user follows, the alerts they set, the news they pulled toward — is what makes a sync worth building. This page maps both, names the authorized route to each, and says what we hand over.

The bottom line: iWow is two data problems wearing one app. The quote numbers are governed by exchange licensing and are cleanest sourced from an authorized feed; the watchlists, alerts and per-user news selection are reachable through consented protocol analysis of the app's own session. Keep those two separated and the integration is both compliant and useful.

What sits behind an iWow account

Each row below is a surface the app genuinely exposes to its users, named the way iWow names it where the wording is visible in the product.

Three authorized ways in

Not every route fits every buyer, so here are the ones that genuinely apply to iWow.

Consented protocol analysis of the app session

We instrument a build and observe how the iWow client talks to its SYSTEX backend for a consenting account — the device handshake, the session token, the watchlist fetch, the quote subscription. This reaches the user-specific layer: the watchlists, the account's alerts, the news it surfaces. Effort is medium-to-high because the quote transport is a long-lived socket rather than plain request/response, and durability tracks the client version. Access is arranged with you during onboarding; the work runs against a consenting account, never a scraped one.

User-consented account replay

With the account holder's explicit consent, we replay the same login and watchlist calls on a schedule so their own data flows into your system on their behalf. Reachable: that user's lists, profile and alert settings. This is the lighter build and holds up well while the auth scheme is stable.

Exchange-licensed quote feed for the numbers

The price values themselves are licensed market data. Rather than redistribute iWow's licensed stream, we wire the quote layer to an exchange-authorized source — TWSE / TPEx / TAIFEX trading information, or a licensed vendor feed — so the numbers in your product carry their own license. The user layer from the first two routes rides on top.

Practically, the cleanest split for this app is to take the quote numbers from an exchange-authorized feed and reserve the consented protocol work for the parts that are genuinely personal — the watchlists, the account's alerts, its news selection. That keeps the licensed data licensed and still gives you the personalization that makes iWow worth integrating in the first place. For most teams that means a small consented sync against the account, sitting beside a clean market-data subscription.

A watchlist-and-quote pull, in code

Illustrative shape of the consented route — a session token, the two watchlist groups, then a depth-5 quote stream with gap backfill. Field names get confirmed against a consenting account during the build; nothing here is copied from any iWow documentation.

# Illustrative only. Confirmed against a consenting account at build time.
import httpx, websockets, json

BASE = "https://<iwow-session-host>"        # resolved during protocol analysis

def open_session(device_id, credential):
    # the mobile client posts a device handshake, gets a short-lived token
    r = httpx.post(f"{BASE}/auth/session", json={
        "device": device_id,
        "cred":   credential,          # user-consented login material
    })
    r.raise_for_status()
    return r.json()["session_token"]   # minutes-scale; refreshed on heartbeat

def watchlists(token):
    # the two grouping concepts iWow exposes: 自選 and 分類
    r = httpx.get(f"{BASE}/me/lists", headers={"X-Session": token})
    groups = r.json()["groups"]        # [{"kind":"self|category","symbols":[...]}]
    return [normalize(g) for g in groups]

async def quote_stream(token, symbols):
    url = BASE.replace("https", "wss") + "/quote"
    async with websockets.connect(url, extra_headers={"X-Session": token}) as ws:
        await ws.send(json.dumps({"sub": symbols, "depth": 5}))   # 五檔
        async for frame in ws:
            tick = json.loads(frame)
            if tick.get("type") == "gap":         # sequence gap -> backfill
                await backfill(ws, tick["from"], tick["to"])
                continue
            yield tick                            # {sym, last, bid[5], ask[5], ts}

What lands in your repository

The handover is built around iWow's actual surfaces, not a generic kit:

• An OpenAPI / Swagger spec covering the session, watchlist and news endpoints, plus the quote-stream subscription described as an async channel.
• A protocol and auth-flow report: the device handshake, the session-token lifetime and its heartbeat refresh, the cookie/header chain as it actually behaves.
• Runnable source for the key endpoints in Python and Node.js — watchlist fetch, the depth-5 quote stream with reconnection and gap backfill, the news pull.
• Automated tests with recorded fixtures for each surface, so the build verifies against known frames rather than a live market.
• A normalized schema that maps the 自選 / 分類 grouping into a clean watchlist model and the tick frames into a single quote shape.
• Interface documentation and data-retention guidance written against Taiwan's licensing and personal-data rules.

Where teams plug this in

• A robo-advisor that imports a prospect's existing iWow watchlist, with consent, so onboarding starts from the symbols they already follow.
• An alerting service that ingests the account's intraday push events and re-fires them into Slack, email or a trading journal.
• A research desk that snapshots the five-level depth on a watched set at fixed intervals for later replay.
• A portfolio dashboard that joins the user's grouped lists to a licensed quote feed for one consolidated view across TW and US holdings.

Things we plan around when building against iWow

A few specifics about this app shape the build, and we account for each of them:

• The real-time numbers are licensed exchange data under the TWSE / TPEx / TAIFEX trading-information rules. We design the integration so the quote values come from an authorized feed and only the personal layer is mirrored from the app, which keeps redistribution inside the licensing terms.
• Watchlists carry two grouping concepts — 自選 and 分類 — rather than one flat list. We model both so a synced portfolio preserves the user's arrangement instead of collapsing it.
• The quote transport is a long-lived socket with a session heartbeat. We build reconnection and sequence-gap backfill so a dropped stream recovers instead of quietly going stale.
• When SYSTEX ships a new client build, the captured protocol can move. The handover includes a checked fixture set so a version bump surfaces as a failing test, not a silent data gap. Access and any compliance paperwork are arranged with you as part of onboarding.

Market-data licensing and Taiwan's PDPA

Two regimes meet on this app. The price data is licensed: the Taiwan Stock Exchange (TWSE), the Taipei Exchange (TPEx) and the Taiwan Futures Exchange (TAIFEX) each set rules on the use and retransmission of their trading information, and the securities market sits under the Financial Supervisory Commission. That is exactly why we route the quote values through an authorized feed rather than re-serving iWow's licensed stream. The personal layer — a user's watchlists, alerts and account profile — falls under Taiwan's Personal Data Protection Act, so it is only ever touched with the account holder's consent, scoped to what the integration needs, with consent and access logged and an NDA in place where the work calls for one. Consent is the dependable basis here: the user authorizes the sync of their own data, and we keep the footprint minimal.

Cost, and how the build gets paid

A consented watchlist sync paired with quote normalization, as sketched above, runs one to two weeks. Source-code delivery starts at US$300: you receive the runnable code, the spec, the tests and the docs, and you pay once it runs on your side and you are satisfied. If you would rather not host anything, we run the endpoints and you pay per call with nothing up front. Tell us the app and what you want out of it, and we will say which fits — start at /contact.html.

Screens we mapped against

The surfaces above were read off the app's own screens.

Other Taiwan quote apps in the same bracket

These sit in the same category and hold comparable data; a unified integration usually spans several of them. Listed for context, not ranked.

• 三竹股市 (Mitake) — the broadest Taiwan multi-market quote app, also socket-based, covering equities, ETFs, futures, options, warrants and international indices.
• Yahoo股市 — TW and US quotes with ETF comparison and smart screening, watchlists tied to a Yahoo account.
• CMoney 籌碼K線 — institutional-flow and chip analytics with free and paid watchlist tiers.
• 富果 Fugle — a fintech with its own quote infrastructure and brokerage tie-ins.
• 玩股網 Wantgoo — community discussion, screening and quotes in one place.
• 鉅亨網 Anue (cnyes) — news-led coverage with global market data.
• 元大投資先生 — a broker app combining quotes, watchlists and order entry.
• 行動股市 — a lightweight quote-and-watchlist app for Taiwan equities.
• Goodinfo 台灣股市資訊網 — a web-first reference for fundamental and chip data.

Questions integrators ask before building on iWow

Once iWow is integrated, are its real-time quotes ours to store and redistribute?

The price numbers iWow shows are licensed exchange data governed by the TWSE, TPEx and TAIFEX trading-information rules. We source those values from an exchange-authorized feed and mirror only the user-specific layer — a consenting account's watchlists, its news selection and alerts — so what you store stays inside the licensing terms.

Can a synced watchlist keep iWow's 自選 and 分類 groupings instead of flattening them?

Yes. iWow organizes followed symbols as two grouping concepts, and we model both, so the portfolio you sync preserves how the user arranged their lists rather than collapsing everything into one bucket.

Which Taiwan authorities and rules apply to this integration?

The Financial Supervisory Commission oversees the securities side. The market-data licensing sits with the exchanges — TWSE, TPEx and TAIFEX. Any account-level personal data falls under Taiwan's Personal Data Protection Act, so we work consented, logged and data-minimized.

What happens when SYSTEX ships a new iWow build that shifts the protocol?

The handover includes a fixture and test set keyed to the surfaces we mapped, so a client update shows up as a failing test rather than a silent data gap. The initial build runs one to two weeks; re-validation after a version bump is a much shorter pass.

What was checked, and when

For this write-up we read iWow's Google Play and App Store listings for the feature set and package identity, SYSTEX's own description of the app's integrated services and broker routing, and the Taiwan Stock Exchange's real-time trading-information page for how the quote data is licensed. Checked 11 June 2026 against the then-current listings.

• Google Play — iWow愛挖寶 (com.softmobile.anWow)
• SYSTEX — iWow integrated-services writeup
• TWSE — real-time trading information
• App Store — iWow愛挖寶 (id 434162698)

Mapped by the OpenBanking Studio integration desk · June 2026.