存股價值K線 API integration & Taiwan OpenData services

Deliverables checklist

• OpenAPI / Swagger specification for every wrapped endpoint
• Protocol and auth-flow report (CMoney login, token rotation, request signing)
• Runnable Python and Node.js source for watchlist sync and screener pulls
• Automated test suite (pytest / vitest) and Postman collection
• Compliance pack covering Taiwan PDPA scope, retention windows and consent records
• Operational runbook for token refresh, rate-limit handling and CMoney-side schema changes

Data available for integration

Technical implementation

Each wrapped capability is delivered as an HTTPS endpoint with OAuth2-style bearer tokens, exponential-backoff retry, and a JSON schema that matches our OpenAPI spec. Three representative samples below.

// 1. Login + token bind (server-side proxy of CMoney auth)
POST /api/v1/valuek/auth/login
Content-Type: application/json

{
  "device_id": "<uuid>",
  "credential_ref": "<encrypted_user_credential_handle>"
}

200 OK
{
  "access_token": "<jwt>",
  "refresh_token": "<opaque>",
  "expires_in": 3600,
  "subscription_tier": "pro"
}

// 2. Pull watchlist enriched with valuation + physique
GET /api/v1/valuek/watchlist?user_ref=u_8821
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "as_of": "2026-04-30T08:00:00+08:00",
  "items": [
    {
      "ticker": "2330",
      "name": "TSMC",
      "last_price": 1085.0,
      "valuation_tier": "fair",
      "physique_grade": "A",
      "mine_flags": []
    },
    {
      "ticker": "2412",
      "name": "Chunghwa Telecom",
      "last_price": 124.5,
      "valuation_tier": "cheap",
      "physique_grade": "A",
      "mine_flags": []
    }
  ]
}

// 3. Run a fundamental screener and receive a cohort
POST /api/v1/valuek/screener/run
Authorization: Bearer <ACCESS_TOKEN>
Content-Type: application/json

{
  "strategy": "growth_with_value",
  "filters": {
    "min_roe_3y": 12,
    "max_pe": 18,
    "exclude_mine_flags": true
  }
}

200 OK
{
  "strategy": "growth_with_value",
  "generated_at": "2026-04-30T08:05:11+08:00",
  "matched": [
    {"ticker": "2454", "trigger": "roe_3y=21,pe=14"},
    {"ticker": "1216", "trigger": "roe_3y=15,pe=12"}
  ]
}

# Errors: 401 invalid_token, 429 rate_limited (5 req/s),
# 503 upstream_unavailable (retry with jitter)

Typical integration scenarios

The five flows below are derived from real engagement patterns — boutique asset managers, fintech research desks and family offices that already use Value K-Line as a personal tool and want it as a programmable signal source.

1. Family-office watchlist mirroring. Wealth advisor logs into Value K-Line; our connector exports the optional-stocks list nightly into the firm's portfolio system, alongside the per-ticker valuation tier. Field flow: watchlist.items[].ticker → portfolio.positions, valuation_tier → review queue.
2. Fundamental factor model overlay. A quant team backtests Value K-Line's physique grade as a quality factor against TWSE returns. We deliver a daily snapshot table of (date, ticker, physique_grade, mine_flags) joined to TWSE OpenAPI close prices.
3. Robo-advisor risk gate. Before any auto-rebalance, the engine calls /screener/run with the user's risk profile and excludes any ticker whose mine_flags are non-empty. This maps cleanly to OpenFinance suitability and product-governance requirements.
4. Compliance archiving for sell-side recommendations. When an analyst publishes a recommendation, we snapshot the matching Value K-Line valuation tier and physique grade as supporting evidence, retained for the audit window required by Taiwan's FSC.
5. Cross-app unified dashboard. A retail brokerage merges Value K-Line fundamental scores with 籌碼K線 institutional flows and TPEx daily quotes, exposing one OpenFinance-style endpoint to its mobile client. This is exactly the integration shape PSD2-inspired Open Banking applies to bank accounts, transposed to equity research data.

Compliance & privacy

Taiwan's Financial Supervisory Commission regulates the securities market and enforces the Personal Data Protection Act (PDPA). The FSC's 2013 "Regulations Governing Maintenance of Personal Information Files by the Non-government Institutions as Designated by the FSC" require security-incident response, employee training and consent collection for information sharing — and Article 21 of the PDPA empowers the FSC to restrict cross-border transfers.

Our delivery follows that envelope: explicit user authorization captured per data subject, minimum-necessary fields, encryption at rest and in transit, and consent-revocation hooks so a user can purge their watchlist mirror in a single API call. Where the integration touches authoritative market data, we route through the official TWSE / TPEx OpenAPI rather than scraping the consumer app.

Typical modules we wrap

• Login and CMoney token rotation
• Watchlist (自選股) read / write
• Valuation, physique and mine-sweeping endpoints
• Screener strategies across value, performance, growth
• Discussion-thread metadata per ticker
• TWSE / TPEx daily quote and corporate-action ingestion
• Subscription / entitlement check for Pro features

About us

OpenFinance Lab is an independent technical studio focused on App protocol analysis and authorized API integration. Our team has shipped fintech, brokerage and OpenBanking work across Greater China, South-East Asia and Europe, and we ship end-to-end Taiwan-equity integrations under FSC and PDPA constraints.

• Taiwan equities, dividend stocks, ETF analytics and cross-border clearing
• Enterprise API gateways, security reviews and audit logging
• Custom Python / Node.js / Go SDKs and test harnesses
• Full pipeline: protocol analysis → build → validation → compliance hand-off
• Source code delivery from $300 — runnable API source plus full documentation; pay after delivery upon satisfaction
• Pay-per-call API billing — access our hosted endpoints and pay only per call, no upfront cost

Contact

To request a quote or share your target app and integration brief, open our contact page:

Contact page

We typically reply within one business day. NDAs available on request.

Engagement workflow

1. Scope confirmation: which Value K-Line surfaces matter (watchlist, screeners, scores, threads).
2. Protocol analysis and API design (2–5 business days, complexity-dependent).
3. Build, internal validation and TWSE / TPEx OpenAPI fusion (3–8 business days).
4. Documentation, runnable samples, Postman collection and test cases (1–2 business days).
5. Typical first delivery: 5–15 business days; FSC-grade compliance reviews can extend timelines.

FAQ

What can I actually pull out of 存股價值K線 through your integration?

Do you also pull official Taiwan market data, or only the app layer?

How long does a first delivery take?

Is this compliant with Taiwan's PDPA and FSC rules?