Connect to XRP Ledger via Vezgo API

Data mapping

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

How to read a transaction

Each XRP Ledger transaction maps to a single Vezgo transaction. Read the value movement from parts[]; cross-currency self-payment swaps produce two parts (sent + received):

• Value movement — parts[] (direction sent/received, ticker, amount, fiat_value). XRP uses ticker "XRP"; issued tokens use their decoded currency code.
• Swaps — misc.swap and the two-leg parts[] are set only for a successful cross-currency Payment to your own account (Account == Destination; one leg XRP, one leg a token); a failed swap carries misc.failed and a single part instead. OfferCreate / OfferCancel DEX orders are NOT emitted as two-leg swaps.
• Network fee — fees[] (always XRP; only the sender pays a fee on the XRP Ledger).
• The transaction hash is in transaction_hash and misc.origin_id; misc.origin_type is the XRPL transaction type.

// One Vezgo transaction = one XRPL transaction (tx.misc.origin_id = hash)
const hash = tx.misc.origin_id;        // == tx.transaction_hash
const kind = tx.misc.origin_type;      // XRPL TransactionType (e.g. Payment, OfferCreate)

const parts = tx.parts ?? [];          // value movement; swaps have sent + received legs
const gas   = tx.fees?.[0];            // network fee, always in XRP (sender only)

if (tx.misc.swap)   { /* cross-currency self-payment swap — parts holds both legs */ }
if (tx.misc.failed) { /* tx did not succeed (misc.txResult != tesSUCCESS) — no value moved */ }
// XRPL has no tokenTransfers / nftTransfers / internalTransfers arrays.