Connect to Base via Vezgo API

Data mapping

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

How to read a transaction

Vezgo consolidates every movement that shares one on-chain transaction hash (misc.origin_id) into a single Vezgo transaction. Read the native movement from the transaction itself, and the token / NFT / internal movements from misc:

• Native ETH transfer — on the transaction itself: parts[] (ticker "ETH", amount, fiat_value, from/to) and gas in fees[] (always ETH).
• ERC-20 token transfers — misc.tokenTransfers[].
• NFT transfers — misc.nftTransfers[].
• Internal (contract-triggered) ETH transfers — misc.internalTransfers[] (also flagged by misc.hasInternalTransaction).

// One Vezgo transaction = all movements sharing one hash (tx.misc.origin_id)
const hash = tx.misc.origin_id;        // on-chain transaction hash
const kind = tx.misc.origin_type;      // chain-level category (see list below)

const native = tx.parts?.[0];          // native ETH transfer (ticker "ETH")
const gas    = tx.fees?.[0];           // gas fee, always in ETH

const tokenTransfers = tx.misc.tokenTransfers   ?? [];  // ERC-20 movements
const nftTransfers   = tx.misc.nftTransfers     ?? [];  // NFT movements
const internal       = tx.misc.internalTransfers ?? []; // internal ETH transfers

if (tx.misc.isSwap) { /* DEX swap — tokenTransfers usually holds both legs */ }
if (tx.misc.failed) { /* reverted: ignore parts + all *Transfers (they may still be present); only gas (fees[]) was spent */ }