Connect to Binance US via Vezgo API

Accounts

Positions

Transactions

Support for Accounts, Positions and Transactions enabled.

Support for Positions & Balances:

Spot
Staking

Supported transaction types:

Spot: deposit/withdrawals, fiat payments, trades (including OCBS), staking, unstaking & rewards.

We're working actively on enriching the supported transaction types.

Full List of Integrations

Data mapping

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

Data	Where to read it	Source on Binance US
Account & wallets	`account.wallets[]`	Binance US connects with an API key + secret (no OAuth, no wallet address); a read-only key is recommended, and the keys must be Binance.US keys (Binance.com global keys are rejected). Binance US exposes two wallets — Spot and Earn (Savings / Staking) — and Vezgo surfaces each present wallet as an entry in account.wallets[] (key on wallet.id). Only the Spot wallet's balances are reconciled from transaction history; the Earn wallet is the exchange-reported snapshot. wallet.is_reconciled is surfaced only for specially-enabled connections and is normally absent.
Balances / positions	`account.balances[]`	Per-asset balances within the Spot and Earn wallets. Each has ticker, amount, decimals and fiat_value (USD). asset_type includes "crypto" (spot / flexible-Earn holdings), "staked" (Earn staking — provider_ticker carries a .staked suffix, e.g. ticker ETH, provider_ticker ETH.staked), "cash" (USD fiat) and "cash_equivalent" (non-USD fiat held in Spot). There are no derivative positions (no futures / options). No ticker_address — exchange holdings are identified by ticker.
Transactions	`GET /accounts/:id/transactions`	Spot trades (including OCBS conversions, reconciled as trades), crypto and fiat deposits / withdrawals, and staking / unstaking with staking rewards. A trade's two legs are reconciled into one transaction. See "How to read a transaction" below.
Assets / securities	`balance.ticker`	Identified by ticker (e.g. BTC, ETH). No ticker_address — custodial exchange balances are not on-chain tokens.

How to read a transaction

Each Binance US activity maps to a Vezgo transaction. Read the value movement from parts[], and classify with transaction_type / transaction_subtype:

Value movement — parts[] (direction sent/received, ticker, provider_ticker, amount, fiat_value in USD). A trade has two parts (the base leg + the quote leg); staking / unstaking also have two legs that share the base ticker but differ by provider_ticker (base vs base.staked). Deposits, withdrawals and rewards have one part.
Type — transaction_type (trade / deposit / withdrawal / staking / unstaking / reward / other). Trades carry no transaction_subtype (read each leg's direction from parts[]). transaction_subtype refines the rest (common values, non-exhaustive): fiat_deposit / fiat_withdrawal, onchain_deposit / onchain_withdrawal (deposits / withdrawals); income_reward, staking_reward (rewards); fees, refund (other).
Fees — fees[] (USD fiat_value); the fee's native asset and amount come from Binance US's original network / trade fee.
Crypto deposits / withdrawals are on-chain: the part carries from_address / to_address and misc.network (the chain), and the on-chain hash is misc.origin_id (the txId). Fiat deposits / withdrawals use the fiat ticker and have no address.
misc.origin_id is the txId for on-chain deposits / withdrawals, the order number for fiat, or the trade id for trades; misc.origin_type is the raw type (deposit, withdraw, trade, fiat_deposit, staking, …).

// One Vezgo transaction = a Binance US activity (a trade's two legs reconciled into one)
const id   = tx.misc.origin_id;         // txId (on-chain), order no (fiat), or trade id
const kind = tx.misc.origin_type;       // raw type (deposit, withdraw, trade, staking, reward, …)

const type    = tx.transaction_type;    // trade | deposit | withdrawal | staking | unstaking | reward | other
const subtype = tx.transaction_subtype; // fiat_deposit | onchain_withdrawal | staking_reward | … (trades none)
const parts   = tx.parts ?? [];         // trade / staking / unstaking = 2 legs; else 1
const fees    = tx.fees ?? [];          // network / trade fee (fiat_value in USD)

const onchain = tx.parts?.find(p => p.from_address || p.to_address); // crypto deposit/withdrawal
if (onchain) { /* misc.network = chain; misc.origin_id = on-chain txId */ }
// Binance US has no tokenTransfers / nftTransfers / internalTransfers arrays, and no
// top-level transaction_hash (the on-chain hash is in misc.origin_id).

Where to read it	Attributes	What it is
`tx.parts[]`	`direction, ticker, provider_ticker, amount, fiat_value, from_address, to_address`	Value movement. Trades, staking and unstaking have 2 legs (staking legs share ticker, differ by provider_ticker base vs base.staked); other activities have 1. from_address / to_address are present only on on-chain crypto deposits / withdrawals.
`tx.transaction_type · transaction_subtype`	`trade/deposit/withdrawal/staking/unstaking/reward/other · fiat_deposit, onchain_deposit, income_reward, staking_reward, …`	Normalized classification — prefer these over the raw misc.origin_type. Subtypes refine non-trade activity; trades carry no subtype. Read each leg's direction from parts[].
`tx.fees[]`	`ticker, amount, fiat_value`	Network / trade fee. fiat_value is USD; ticker / amount are the native fee asset.

misc.origin_type is the raw activity type from Binance US / the connector. It is open-ended, so always classify off transaction_type, not origin_type. Common values:

deposit
withdraw
trade
fiat_deposit
fiat_withdrawal
staking
unstaking
reward

Supported

Two wallets — Spot and Earn (Savings / Staking)
Crypto and fiat (cash) balances
Spot trades, including OCBS conversions (legs reconciled into one transaction)
Crypto deposits / withdrawals (on-chain, with from / to address and network) and fiat deposits / withdrawals
Staking / unstaking and staking rewards
USD fiat valuation for balances and transactions

Notes & limitations

Balances are the exchange's reported (custodial) holdings — there is no on-chain wallet address for balances.
API keys must be Binance.US keys; Binance.com (global) keys are rejected. A read-only key is recommended; the write-permission check is best-effort and gated per client.
There is no top-level transaction_hash — the on-chain hash for crypto deposits / withdrawals is misc.origin_id (the txId), with from / to address on the part and the chain in misc.network.
Only Spot and Earn (Savings / Staking) are supported — no Funding, Margin, Futures, Delivery, Options or Auto-Invest, and no derivative positions or dividends.

See the full Vezgo object reference

Try to connect to Binance US 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

Talk to Sales Explore a Demo