Connect to Hedera via Vezgo API

Data mapping

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

How to read a transaction

Each successful HBAR or HTS token movement maps to a Vezgo transaction. Read the value movement from parts[0]:

• Value movement — parts[0] (direction sent/received, ticker, amount, fiat_value in USD). Each transaction carries a single part: the wallet's net change in one asset (HBAR, or one HTS token).
• Native vs token — a single on-chain transaction (one transaction_hash) that moves both HBAR and an HTS token is surfaced as two Vezgo transactions (one HBAR, one token) that share the same transaction_hash and misc.origin_id. The HBAR network fee is on the HBAR transaction.
• Type — transaction_type is deposit (net received) or withdrawal (net sent), derived from the wallet's net movement. There is no transaction_subtype, and a swap appears as a separate withdrawal + deposit, not a single trade.
• Network fee — fees[] (HBAR), charged on the wallet's outgoing (withdrawal) transactions. The transaction hash is in transaction_hash; misc.origin_id is the Hedera transaction id (e.g. 0.0.12345@1700000000.000000000) and misc.origin_type is the Hedera transaction type (e.g. CRYPTOTRANSFER).

// One Vezgo transaction = one asset movement (HBAR or one HTS token) for the wallet
const hash = tx.transaction_hash;      // Hedera transaction hash
const id   = tx.misc.origin_id;        // Hedera transaction id (0.0.x@seconds.nanos)
const kind = tx.misc.origin_type;      // Hedera transaction type (e.g. CRYPTOTRANSFER, TOKENMINT)

const type = tx.transaction_type;      // deposit | withdrawal (net direction)
const part = tx.parts?.[0];            // single asset movement (HBAR or one token)
const fee  = tx.fees?.[0];             // network fee in HBAR (on withdrawals)

// A single on-chain tx moving HBAR + a token = two Vezgo txns sharing transaction_hash / origin_id.
// Hedera parts carry no from/to address and no transaction_subtype; only successful txns are imported.