Connect to KuCoin via Vezgo API

Data mapping

A field-level guide to the Vezgo API data for KuCoin — what each attribute means and where to read it — so you can map it into your own system.

How to read a transaction

Each KuCoin activity maps to a Vezgo transaction. Read the value movement from parts[], and classify with transaction_type / transaction_subtype:

• Value movement — parts[] (direction sent/received, ticker, provider_ticker, amount, fiat_value in USD). A trade / convert has two parts (the received leg + the sent leg, and a fee leg when charged); a staking subscription / redemption has two legs (the asset and its staked counterpart); deposits, withdrawals, transfers and rewards have one part.
• Type — transaction_type (trade / deposit / withdrawal / staking / unstaking / reward / other) with transaction_subtype: transfer_in on an account transfer (transfers are surfaced as deposit / transfer_in) and refund on a refunded fee (typed other). Trades, deposits, withdrawals, staking, unstaking and rewards carry no subtype.
• Staking — a staking subscription (staking) or redemption (unstaking) is a two-leg move where the staked leg carries provider_ticker with a .staked suffix (e.g. ticker ETH, provider_ticker ETH.staked).
• Counterparty — a deposit carries the on-chain from_address (where the coins came from) and a withdrawal carries the to_address (the destination); trades and ledger entries carry no address.
• Fees — fees[] (the trade / network / withdrawal fee): the native fee asset and amount, with fiat_value in USD.
• misc.origin_id is KuCoin's id for the activity (the wallet transaction id for a deposit / withdrawal, the trade id for a trade, or the ledger id). misc.origin_type is KuCoin's raw type (deposit, withdrawal, trade, Transfer, Convert, staking, unstaking, reward, …); spot trades also carry misc.origin_pair (e.g. BTC-USDT), misc.order_id and misc.order_type (converts and ledger-sourced trades may omit some of these). There is no separate transaction_hash field — for a deposit / withdrawal the wallet transaction id is surfaced as misc.origin_id.

// One Vezgo transaction = a KuCoin activity (a trade / convert / staking move carries its two legs as parts)
const id    = tx.misc.origin_id;        // KuCoin id: wallet tx id (deposit/withdrawal), trade id, or ledger id
const kind  = tx.misc.origin_type;      // raw KuCoin type: deposit | withdrawal | trade | Transfer | Convert | staking | unstaking | reward
const pair  = tx.misc.origin_pair;      // e.g. "BTC-USDT" on a spot trade (else undefined)

const type    = tx.transaction_type;    // trade | deposit | withdrawal | staking | unstaking | reward | other
const subtype = tx.transaction_subtype; // transfer_in | refund | (else none)
const parts   = tx.parts ?? [];         // trade/convert/staking = 2 legs; deposit/withdrawal/transfer/reward = 1
const fees    = tx.fees ?? [];          // trade / network / withdrawal fee (native asset + USD)

// Deposits expose from_address, withdrawals expose to_address (on parts[]).
// transaction_hash is null — the wallet tx id is in misc.origin_id for deposits/withdrawals.
// Staking legs carry provider_ticker with a .staked suffix (e.g. ETH.staked).
// No tokenTransfers / nftTransfers / internalTransfers arrays (exchange, not on-chain).