Connect to TRON via Vezgo API

Data mapping

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

How to read a transaction

Each on-chain transaction maps to a single Vezgo transaction with one part. Read the movement from parts[0] and the network fee from fees[]:

• Value movement — parts[0] (direction sent/received, ticker, amount, fiat_value, from_address, to_address). Native transfers use ticker "TRX"; token transfers use the token's ticker.
• TRC-20 transfers — misc.trc20 is true and misc.tokenId holds the token contract address. from_address and to_address are the actual counterparties, not the contract.
• Staked TRX — freezing TRX for bandwidth or energy moves it out of the spendable balance and into the staked position; the staked balance covers Stake 2.0 freezes, legacy freezes and expired unstakes not yet withdrawn.
• Network fee — fees[] (always TRX), charged to the sender. A transaction covered entirely by free bandwidth reports a zero fee.
• misc.origin_type is the direction from the account's perspective (IN / OUT), and misc.possible_spam is set on transactions TRON's explorer flags as risky — unsolicited dust and lookalike-token airdrops are common on TRON.

// One Vezgo transaction = one on-chain transaction (tx.misc.origin_id = hash)
const hash = tx.misc.origin_id;        // == tx.transaction_hash
const kind = tx.misc.origin_type;      // "IN" | "OUT"

const move = tx.parts?.[0];            // value movement (TRX or a token)
const fee  = tx.fees?.[0];             // network fee, always in TRX (sender only)

if (tx.misc.trc20) {
  const contract = tx.misc.tokenId;    // TRC-20 contract — the token's real identity
}
if (tx.misc.possible_spam) { /* explorer-flagged; consider hiding by default */ }
// TRON has no tokenTransfers / nftTransfers / internalTransfers arrays.