Help center

Sign in to the dashboard, open the API keys section, create a new key, and copy it immediately. Store it securely; if it leaks, revoke it and create a new one right away.

Send an HTTPS GET request to the /v2/datasets/* endpoints with your key in the X-API-Key header. See /docs/quick-start for examples.

Start from /v2/datasets/twse-daily-price or /v2/datasets/tpex-daily-price, passing query parameters such as symbol and limit.

Every request returns an X-Request-Id, which makes it easier to trace errors, reconcile records, and let support investigate.

Each dataset endpoint maps to a fixed cost, and the response header carries X-TWMD-Credits-Cost (estimated or actually charged depending on the mode).

These usually come from an upstream backend timeout, a cold start, or a temporary service fluctuation. Record the requestId, retry later, or contact us.

Set TWMD_API_KEY, create a client, then call methods such as twse_daily_price and issuer_profile. See /docs/sdk/python-sdk.

Create a TWMarketDataClient with your apiKey, then use getDataset or the dataset-specific helpers. See /docs/sdk/javascript-sdk.

MCP is an interface that lets agents call data services as tools. TW Market Data currently ships an MCP skeleton (preview).

A common flow is to look up the company profile first, then prices and revenue, and finally combine them into research context. See /docs/ai-agents/agent-workflow-examples.

Get the requestId from the SDK response meta or the API response header, then cross-reference it against your usage/credits records.

First confirm that browser cookies and third-party sign-in flows are enabled; if it keeps failing, report the time it occurred and the requestId so we can investigate.

Use the registration flow to create and verify your email, or set a password after verifying an existing account.

This is usually related to a session or a temporary backend fluctuation. Refresh, sign in again, or try later. If it persists, contact us.

A brief signed-out state can be caused by a failed session lookup or a network fluctuation. Retry on a stable connection and keep the timestamp for investigation.

Credits are used to price API requests. Top them up through a subscription plan's included credits or a one-time top-up.

Dry-run only calculates the estimated cost without actually deducting from your wallet. The response shows X-TWMD-Dry-Run: true.

Live deduction must be explicitly enabled by a production safety flag; it is off by default to prevent accidental charges.

While the platform is still in dry-run mode, usage records estimated credits, but the wallet balance does not decrease.

Check request records and requestId at /usage, and transaction and reconciliation details at /billing/credits.

Revoke that key in the dashboard immediately, then create and swap in a new one.

Click the delete/revoke icon in the API keys table. The key stops working immediately after revocation.

The full value is shown at creation time; the system stores only a hash and an encrypted version to avoid exposing the plaintext key.

requestId helps with issue tracing, reconciliation, and letting support locate a single request.

During low traffic the backend services can go cold, so the first request is slower; subsequent warm requests are usually noticeably faster.

Common causes are a backend cold start, a DB pool waking up, or an upstream cache that hasn't been built yet.

Include the time it occurred, the endpoint, the HTTP status code, and the requestId, and email avenra.platform@gmail.com.