Authorized OpenData / OpenFinance integration for WEEX accounts, statements, perpetual futures, and copy-trading mirroring
WEEX is a global crypto exchange founded in 2018 with 6.2M+ users across 200+ countries, 1,700+ trading pairs, up to 400× leverage on perpetual futures, and a 1,000 BTC Protection Fund backed by 1:1 proof of reserves. We help product, finance, and compliance teams turn that activity into structured, query-able data.
POST /api/v1/weex/statement
Content-Type: application/json
Authorization: Bearer <ACCESS_TOKEN>
X-WEEX-SIGN: <HMAC_SHA256(secret, ts+method+path+body)>
{
"account_id": "uid_8821934",
"from_ts": 1735689600,
"to_ts": 1738368000,
"scope": ["SPOT", "FUTURES", "AUTO_EARN"],
"symbols": ["BTC-USDT", "ETH-USDT", "SOL-USDT"],
"page": 1,
"page_size": 200
}
200 OK
{
"rows": [
{"ts": 1737421102, "symbol": "BTC-USDT", "side": "BUY",
"qty": "0.0125", "price": "97431.20", "fee": "0.0608",
"realized_pnl": null, "channel": "SPOT"},
{"ts": 1737420041, "symbol": "ETH-USDT", "side": "SELL",
"qty": "1.50", "price": "3320.84", "fee": "0.498",
"realized_pnl": "+42.18", "channel": "FUTURES_PERP"}
],
"next_cursor": "eyJwIjoyfQ=="
}
Treasury reconciliation across CEX accounts. Tax reporting for 200+ jurisdictions. Risk dashboards that fold WEEX exposures next to DeFi positions. Quant back-testing on real fill data instead of public ticks. Compliance evidence for proof-of-reserves and audit windows.
Each engagement starts from your concrete need, not a generic SDK dump — we map the WEEX endpoints you actually need and stop there.
The table below maps the data WEEX exposes (publicly or under user-authorized access) to typical downstream uses. We treat each row as a discrete deliverable so engagements can scope tightly.
| Data type | Source feature | Granularity | Typical use |
|---|---|---|---|
| Spot trade history | Spot module · 1,700+ pairs | Per-fill, ms timestamp | Tax reporting, P&L attribution, accounting close |
| Perpetual futures fills & funding | Futures module · up to 400× leverage | Per-fill + funding interval | Realised PnL, funding-cost analysis, risk reports |
| Open positions & margin | Cross / isolated margin engine | Real-time snapshot + websocket | Liquidation alerts, exposure dashboards |
| Wallet & sub-account balances | Spot, futures, funding wallets | Per-asset, per-account | Treasury sync, internal transfer audits |
| Auto Earn yield ledger | WEEX Auto Earn (idle USDT, no lock-up) | Daily interest accrual | Yield dashboards, APR comparison vs DeFi |
| Copy-trading mirror events | Copy Trading 2.0 sub-accounts | Per-trade with follower mapping | Strategy monitoring, lead-trader payout calc |
| Deposits & withdrawals | On-chain + fiat on-ramps (Apple Pay, Google Pay, Visa, SEPA, PIX) | Per-transfer, on-chain txid | Travel-rule reporting, AML reconciliation |
| WXT rewards & airdrops | WXT holder benefits, VIP tiers | Per-event ledger | Loyalty analytics, profit-sharing reports |
| Market data & klines | TradingView-powered chart engine | 1m → 1M candles + depth | Quant research, signal generation |
An accounting team running a quarterly close pulls WEEX spot fills, perpetual futures realised PnL, and Auto Earn daily interest into the same ledger they use for Binance and Bitget. We provide a unified statement endpoint that normalises symbols (e.g. BTC-USDT), preserves fee currency, and emits realised PnL for both LIFO and FIFO. Maps to OpenFinance "transaction reporting" patterns.
A trading desk wants real-time aggregate exposure across WEEX (futures, up to 400× leverage), DeFi vaults, and OTC books. We deliver a websocket bridge that pushes position, funding, and liquidation_warn events into Kafka, plus a daily margin-call rollup. The page on liquidation alerts feeds an internal Slack/Telegram bot.
A strategy provider on the WEEX leaderboard needs to verify follower payouts and reconstruct entry/exit timing for each follower under Copy Trading 2.0 sub-accounts. We expose /copytrade/mirror_events and /copytrade/payouts with deterministic ordering, so payouts can be re-derived offline and audited.
A corporate treasury parking idle USDT in WEEX Auto Earn (promotional APRs up to 100% for new users) wants daily accrual rows synced into a SQL warehouse next to bank-account interest. We deliver a daily snapshot job that records per-asset balance, accrued interest, and the effective APR window so finance can compare across providers.
An institutional client wants to verify WEEX's published 1:1 proof-of-reserves attestations (third-party audits referenced on CoinMarketCap and GitHub) on a schedule. We integrate the public reserves feed with an internal compliance log and raise an alert if backing drops below 100% or audit timestamps go stale.
// Signed private request (HMAC-SHA256)
const ts = Date.now();
const path = "/api/v1/weex/positions";
const body = JSON.stringify({ account_id: "uid_8821934" });
const payload = `${ts}POST${path}${body}`;
const sign = hmacSha256(secret, payload).toString("hex");
await fetch("https://api.partner.example.com" + path, {
method: "POST",
headers: {
"X-WEEX-KEY": apiKey,
"X-WEEX-TS": ts,
"X-WEEX-SIGN": sign,
"Content-Type": "application/json"
},
body
});
// Subscribe to private fills + funding stream
{
"op": "subscribe",
"topic": ["fills", "funding", "position"],
"auth": {
"key": "<API_KEY>",
"ts": 1738368012,
"sig": "<HMAC>"
}
}
// Server push (fill event)
{
"topic": "fills",
"ts": 1738368013421,
"data": {
"symbol": "BTC-USDT-PERP",
"side": "SELL",
"qty": "0.04",
"px": "97402.10",
"lev": 25,
"margin_mode": "ISOLATED"
}
}
POST https://yourapp.example.com/hooks/weex
X-WEEX-Webhook-Sign: <HMAC_SHA256>
{
"event": "auto_earn.accrual",
"account_id": "uid_8821934",
"asset": "USDT",
"principal": "120000",
"interest": "8.91",
"apr": "27.10",
"as_of": "2025-01-31T00:00:00Z"
}
// Reply 2xx within 5s; we retry with
// exponential backoff on 5xx / timeouts.
We work strictly under user authorization or against documented public APIs. Our delivery covers regional context that crypto-exchange data inevitably touches:
Where the engagement crosses into derivatives-specific rules (e.g. up to 400× leverage products are restricted in some regions), we annotate scope and recommend per-region routing.
A typical WEEX integration pipeline runs in four stages, with optional fan-out to a warehouse:
(account, ts, txid).The pipeline is built so it can sit next to existing CEX integrations (Binance, OKX, Bybit) without forcing a rewrite of downstream consumers.
WEEX serves a global retail + active-trader audience: 6.2M+ registered users across 200+ countries, with strong adoption among futures traders attracted by up to 400× leverage and the copy-trading leaderboard. The platform supports Apple Pay, Google Pay, Visa, Mastercard, SEPA, PIX, Alchemy Pay and MoonPay on the fiat side, which makes its user base measurably international rather than concentrated in a single region. Apps run on Android and iOS with TradingView-powered charts, so integration consumers are typically (a) prop / family-office desks, (b) crypto-tax and accounting SaaS, and (c) compliance and audit tooling.
A concrete recent signal: in March 2025 a server malfunction caused a flash crash on the ETH/USDT pair; WEEX publicly acknowledged the incident and compensated affected users for 100% of their losses (over $6M paid out), and shipped Copy Trading 2.0 with sub-account fund segregation later that year. Both events shape what "good" data integration looks like — incident reconstruction and per-follower fund isolation are now first-class requirements.
Tap any thumbnail to view full-size. Use these to map UI features to the exact API resources you want exposed.
Teams that integrate WEEX usually maintain parallel pipelines for several other crypto exchanges. The list below is purely descriptive — same data shapes, slightly different auth and field names — and exists so users searching for any of these platforms can find this page when they need a unified integration plan.
We are an independent technical studio focused on fintech and crypto-exchange API integration. Our engineers come from exchanges, payment gateways, market-data vendors, and protocol-analysis backgrounds, and we have shipped integrations against tier-1 CEX, regional banks, and OpenBanking PSPs. We know exchange engineering culture: rate limits, signed requests, websocket private channels, and the audit pressure that follows.
Send us the target app and the exact data points you need (e.g. spot fills, funding payments, copy-trade events). We will reply with scope, timeline, and price.
For WEEX-specific user support, refer to WEEX's own channels: support@weex.com or t.me/WeexGlobalGroup_New. We are an independent integration studio, not affiliated with WEEX.
What do you need from us?
How long does delivery take?
How do you handle compliance?
Can you keep WEEX data alongside other exchanges?
WEEX (package com.wake.weexprd) is a global cryptocurrency exchange founded in 2018, serving 6.2M+ users across 200+ countries. It supports more than 1,700 trading pairs spanning major assets (BTC, ETH, SOL, XRP, USDC, USDT) and emerging tokens, with spot, futures, OTC, and copy-trading products.