Connect to Solana via Vezgo API

Data mapping

A field-level guide to the Vezgo API data for Solana — 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 the movements in one on-chain transaction (one signature) into a single Vezgo transaction. Read the native SOL movement from the transaction itself, and SPL token movements from misc:

• Native SOL — parts[0] always exists (ticker "SOL"; amount 0 when no net SOL moved) and holds the wallet's net SOL change with the network fee already subtracted. The fee is in fees[] (SOL) only when the connected wallet paid it.
• SPL token transfers — misc.tokenTransfers[]. On Solana, NFTs are SPL tokens, so NFT movements also appear here.
• SOL staking — stake / unstake appear as their own transactions (deposit / withdrawal of SOL).
• The signature is in transaction_hash and misc.origin_id; the on-chain program is in misc.source.

// One Vezgo transaction = one on-chain signature (tx.misc.origin_id)
const sig  = tx.misc.origin_id;        // == tx.transaction_hash (the signature)
const kind = tx.misc.origin_type;      // upstream provider's transaction type (e.g. TRANSFER, SWAP)

const native = tx.parts?.[0];          // native SOL transfer (ticker "SOL")
const gas    = tx.fees?.[0];           // network fee in SOL (only if the wallet paid it)

const tokenTransfers = tx.misc.tokenTransfers ?? [];  // SPL token movements

if (tx.misc.failed) { /* failed on-chain — no value moved, fee still spent */ }
// Solana has no internalTransfers / nftTransfers arrays (those are EVM-only).