Connect to Bybit via Vezgo API

Data mapping

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

How to read a transaction

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

• Value movement — parts[] (direction sent/received, ticker, provider_ticker, amount, fiat_value in USD). A spot trade and a convert each have two parts (base + quote / from + to); a derivative (linear) trade has one part, the contract quantity under the settlement-currency ticker; deposits, withdrawals, transfers and rewards have one part. On a Unified-account trade the sent part's amount is negative: take its absolute value and apply direction.
• Type — transaction_type (trade / deposit / withdrawal / reward / bonus). Bybit carries no transaction_subtype; read a trade's buy vs sell from parts[].direction. A convert (crypto-to-crypto) is classified as a trade. misc.trade_category ("spot" / "linear") tells spot from derivative trades where it is set; Classic Spot accounts, and Unified-account trades imported before February 10, 2026, leave it unset. A spot trade has two parts and a linear trade one, on every account.
• Fees — fees[] (the trade or network fee; fiat_value in USD, plus the native fee asset and amount). On a spot trade (misc.origin_type TRADE, with two parts) the parts are the fill amounts before the fee, and fees[] is charged on top: deduct it from the balance of the asset in fees[].ticker. A convert (misc.origin_type CONVERT) carries its cost in the rate: its parts are the exact amounts exchanged.
• On-chain deposits / withdrawals carry the destination address in parts[].to_address and the blockchain hash in transaction_hash (Bybit's txID). There is no from_address and no misc.network (the chain is in the description). misc.origin_id is the Bybit id for the activity (execId / tradeId / withdrawId / txID); misc.origin_type is Bybit's raw activity type.

// One Vezgo transaction = a Bybit activity (a spot trade carries its two legs as parts)
const id   = tx.misc.origin_id;        // Bybit id (execId / tradeId / withdrawId / txID)
const kind = tx.misc.origin_type;      // raw Bybit type (TRADE, CONVERT, deposit_on_chain, TRANSFER_IN, REWARD, …)

const type  = tx.transaction_type;     // trade | deposit | withdrawal | reward | bonus
const parts = tx.parts ?? [];          // spot trade / convert = 2 legs; linear trade / deposit / withdrawal = 1
const fees  = tx.fees ?? [];           // trade / network fee; spot trades: charged on top — deduct it

if (tx.transaction_hash) { /* on-chain deposit/withdrawal — parts[].to_address is the destination */ }
// Bybit has no transaction_subtype (read buy/sell from parts[].direction) and no from_address.
// misc.trade_category = "spot" | "linear" where set (unset on Classic Spot accounts and on
// Unified-account trades imported before Feb 10, 2026): a spot trade has 2 parts, a linear trade 1.
// Unified-account trades: the sent part's amount is negative — use Math.abs(amount) with direction.