Buying, integration and operations —
let us answer the obvious questions first.

Yes. A token is bound to a subscription, which defines the asset classes, symbol count, WebSocket connections and QPS. A subscription can hold several tokens (for example one for production and one for testing) that share the plan quota.

A token has no expiry of its own; it stays valid as long as its subscription does. When a subscription expires it enters a grace period, and the token stops working only after that. Renewing restores the same token immediately with no re-integration.

REST covers symbol lists, tickers, order books, trades and candle queries. WebSocket delivers live tickers, order books, trades and candle subscriptions. Candle intervals cover 1m / 5m / 15m / 30m / 1h / 4h / 1d; see the API docs for fields and formats.

Some plans support a trial, with the length set by the plan. You can start a trial subscription right after signup; quotas and rate limits match a paid plan and no charge is made when the trial ends.

Each plan may offer monthly, quarterly, semi-annual and yearly prices, billed once per cycle rather than by auto-debit. Prices on the page follow the selected currency; the server price is authoritative at checkout.

Yes. The settlement currency is fixed at registration. CNY accounts can use Alipay, WeChat Pay or bank transfer; USD accounts use bank transfer or the enabled USD channels. Prices are configured independently per currency.

Yes. Paid orders can be invoiced from the console. CNY accounts support standard and special VAT invoices; USD accounts receive commercial invoices. Issued invoices can be downloaded from the console.

REST QPS is counted per subscription and shared by all of its tokens. WebSocket limits apply to concurrent connections and to symbols per connection. Response headers report the quota and remaining calls; over-limit requests return 429.

Renew or upgrade from the console subscription page. Upgrades credit the remaining value and take effect once you pay the difference; renewals extend from the current expiry date, so paid time is never lost.

Never put a token in frontend code or a public repository. Proxy market data requests server-side, set up monitoring and alerts per token, and use different tokens per environment so one can be revoked independently.