Connect to Algorand via Vezgo API

Accounts

Positions

Transactions

Support for Accounts, Positions and Transactions enabled.

  • Retrieves a maximum of 1000 transactions per sync.
  • Maximum 5000 transactions allowed per account.

Full List of Integrations

Data mapping

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

DataWhere to read itSource on Algorand
Account & walletaccount.wallets[].addressThe connected Algorand account address (58-character base32 with checksum). One address is one account; wallet.address is the stable identity reused across syncs and reconnects.
Balances / positionsaccount.balances[]Native ALGO plus Algorand Standard Assets (ASAs) the account has opted into, from the live on-chain snapshot. Each balance has ticker, amount, decimals and fiat_value (USD); ASAs add ticker_address — the asset's creator account.
TransactionsGET /accounts/:id/transactionsALGO payments, ASA transfers, account close-outs and the ALGO/ASA movements nested inside application calls, one Vezgo transaction per value movement. See "How to read a transaction" below.
Assets / securitiesbalance.ticker · balance.ticker_addressNative ALGO uses ticker ALGO. ASAs use the asset's unit name as ticker and carry ticker_address (the creator account); an ASA with no on-chain unit name falls back to its asset path (algorand/asset/<id>) as the ticker.

How to read a transaction

Each value movement touching the connected account maps to a single Vezgo transaction. 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). ALGO uses ticker "ALGO"; ASAs use their unit name.
  • Multi-movement transactions — an application (smart-contract) call that moves several assets for the account, or a payment combined with an account close-out, produces one Vezgo transaction per movement. They share the same on-chain transaction id prefix in misc.origin_id (suffixed per inner movement) and the network fee is attached to the first one only.
  • Account close-outs — the remainder sent when an account is closed arrives as a normal received payment at the destination.
  • Fee-only transactions — an application call with no value movement for the account still costs a fee; it appears as a transaction with a zero-amount ALGO part and the fee in fees[].
  • Network fee — fees[] (always ALGO). Only the sender pays a fee on Algorand; incoming transactions carry no fee even though the counterparty paid one.
  • The on-chain transaction id is in misc.origin_id; 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 txn id (suffixed per inner movement for multi-leg calls)
const kind = tx.misc.origin_type;      // deposit | withdrawal | fee

const move = tx.parts?.[0];            // value movement (ticker "ALGO" or the ASA unit name)
const gas  = tx.fees?.[0];             // network fee, always in ALGO (sender only)

if (move.amount === "0" && gas) { /* fee-only app call — nothing moved, fee still spent */ }
// Algorand has no tokenTransfers / nftTransfers / internalTransfers arrays.
Where to read itAttributesWhat it is
tx.parts[0]direction, ticker, ticker_address, amount, fiat_value, from_address, to_addressValue movement. from_address is set on received movements, to_address on sent ones.
tx.fees[0]ticker ("ALGO"), amount, fiat_valueNetwork fee — always ALGO; present only when the connected account paid it (sender), and on the first movement of a multi-movement transaction.

misc.origin_type is the movement direction from the account's perspective:

  • deposit
  • withdrawal
  • fee

Supported

  • Native ALGO balances and transfers
  • Algorand Standard Asset (ASA) balances and transfers
  • ALGO and ASA movements nested inside application (smart-contract) calls
  • Account close-out remainders
  • Network fees (reported in ALGO)
  • USD fiat valuation for native ALGO balances and transactions

Notes & limitations

  • ASA balances reflect the current on-chain snapshot; opted-in assets with a zero balance are omitted.
  • fiat_value is provided for ALGO only — ASA balances and ASA transaction parts are unvalued (null).
  • Asset opt-outs (closing an ASA position to another account) do not carry the closed amount on-chain, so the final outgoing movement of an ASA opt-out may not appear as a transaction.
  • Transaction history is imported from newest to oldest across successive syncs. A maximum of 2,500 transactions are imported per account (a lifetime cap); accounts with more history than that keep receiving new transactions but their oldest history is not fetched.
  • Only the sender is charged the network fee (ALGO); fee-only transactions (application calls with no value movement) are reported with a zero-amount part.
See the full Vezgo object reference

Try to connect to Algorand in our Demo Sandbox

Open Demo

Let's get you started

To get your API Keys, sign up on the portal or reach out to the team at sales@vezgo.com

You have questions? Contact us