Connect to Coinbase via Vezgo API

Data mapping

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

How to read a transaction

Each Coinbase 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, amount, fiat_value). A buy/sell trade has two parts (the crypto leg + the fiat/quote leg); other activities have one.
• Type — transaction_type (trade / deposit / withdrawal / reward / staking / unstaking) with a finer transaction_subtype (buy, sell, fiat_deposit, transfer_in, transfer_out, onchain_deposit, onchain_withdrawal, vault_deposit, vault_withdrawal, staking_reward, interest_income, …). Some raw types (e.g. pro_withdrawal, exchange_deposit, cardspend, transfer) have no normalized subtype and resolve to transaction_type "other".
• Fees — fees[] (the trade / transaction fee).
• misc.origin_id is the Coinbase transaction id (a reconciled trade uses a combined id); misc.origin_type is Coinbase's raw type. On-chain sends/receives also include transaction_hash and from/to addresses on the part.

// One Vezgo transaction = a Coinbase activity (buy/sell legs reconciled into one)
const id   = tx.misc.origin_id;         // Coinbase tx id (or combined id for a trade)
const kind = tx.misc.origin_type;       // Coinbase raw type (buy, sell, send, fiat_deposit, …)

const type    = tx.transaction_type;    // trade | deposit | withdrawal | reward | staking | …
const subtype = tx.transaction_subtype; // buy | sell | fiat_deposit | transfer_in | …
const parts   = tx.parts ?? [];         // trade = 2 legs (crypto + fiat); else 1
const fees    = tx.fees ?? [];          // e.g. buy/sell fee

if (tx.transaction_hash) { /* on-chain send/receive — parts carry from/to addresses */ }
// Coinbase has no tokenTransfers / nftTransfers / internalTransfers arrays.