Connect to Stellar via Vezgo API

Data mapping

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

How to read a transaction

Each value movement touching the connected account 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). The native asset uses ticker "XLM"; issued assets use their asset code.
• Multi-operation transactions — one Stellar transaction can move value several times for the account, and each movement becomes its own Vezgo transaction. A single-movement transaction keeps the on-chain hash as misc.origin_id; a multi-movement one uses the per-operation event id instead (the hash with a leg suffix), so misc.origin_id and transaction_hash are not a bare hash there. Movements belonging to other accounts in the same transaction are not reported.
• Path-payment swaps — sending one asset and receiving another arrives as two separate Vezgo transactions (the sent leg and the received leg) sharing the same on-chain hash prefix, not as one transaction with two parts.
• Account creation and account merge — the funding of a new account and the remainder sent when an account is merged appear as ordinary received or sent movements.
• Fee-only transactions — trustline changes, Soroban contract calls with no represented movement and failed operations still cost a fee; they appear as a transaction with a zero-amount XLM part and the fee in fees[].
• Network fee — fees[] (always XLM). Only the transaction's source account pays a fee on Stellar, so incoming transactions carry no fee even though the counterparty paid one; on a multi-movement transaction the fee is attached to the first movement only.
• misc.origin_type is the movement direction (deposit / withdrawal / fee).

// One Vezgo transaction = one value movement for the account
const id   = tx.misc.origin_id;        // on-chain hash, or the per-leg event id on multi-movement txs
const kind = tx.misc.origin_type;      // deposit | withdrawal | fee

const move = tx.parts?.[0];            // value movement (ticker "XLM" or the issued asset's code)
const gas  = tx.fees?.[0];             // network fee, always in XLM (source account only)

if (move.amount === "0" && gas) { /* fee-only tx — nothing moved, fee still spent */ }
// A path-payment swap arrives as two transactions (sent leg + received leg), not two parts.
// Stellar has no tokenTransfers / nftTransfers / internalTransfers arrays.