Vezgo now supports Hyperliquid. Users connect by pasting their wallet address —\nread-only, with nothing to install and nothing to approve.
\nWhat you get
\nAction required
\nNone. If you match assets by ticker, prefer ticker_address — it carries the\nHyperEVM contract address, or the HyperCore token id for tokens with no EVM\ndeployment. HyperCore tickers are short and collide with unrelated tokens\nlisted elsewhere.
Wealthsimple Crypto now connects through Wealthsimple's official OAuth.\nUsers sign in on Wealthsimple's own page and approve read-only access, rather\nthan entering their Wealthsimple credentials into Connect.
\nWhat changed
\nAction required
\nNone. Existing credential-based connections keep working and sync identically,\nwith no re-authentication required from your users.
\nWealthsimple Crypto data mapping →
", "url": "https://vezgo.com/docs/changelog/2026/08/08/wealthsimple-crypto-oauth", "title": "Wealthsimple Crypto connects through Wealthsimple sign-in", "summary": "Wealthsimple Crypto uses Wealthsimple's official OAuth, so users sign in with Wealthsimple instead of handing over their credentials.", "date_modified": "2026-08-08T00:00:00.000Z", "tags": [ "widget" ] }, { "id": "https://vezgo.com/docs/changelog/2026/07/21/okx-oauth", "content_html": "Vezgo is now an approved OKX OAuth broker. Users authorize on OKX's own\npage and come back connected — no API key, secret or passphrase to create and\npaste.
\nWhat changed
\nAction required
\nNone, and this is backward compatible: existing API-key connections keep working\nand sync identically. Nothing to re-authenticate, and nothing for your users to\ndo.
\nGlobal OKX accounts are covered. OKX US (app.okx.com) is not yet supported.
\n", "url": "https://vezgo.com/docs/changelog/2026/07/21/okx-oauth", "title": "OKX connects with one-click authorization", "summary": "Vezgo is an approved OKX OAuth broker, so users authorize on OKX instead of creating an API key, secret and passphrase.", "date_modified": "2026-07-21T00:00:00.000Z", "tags": [ "widget" ] }, { "id": "https://vezgo.com/docs/changelog/2026/06/15/webhook-static-source-ips", "content_html": "Webhook deliveries now come from a small, fixed set of static IP addresses\ninstead of a changing range, so they can be allowlisted on a firewall or\ningress. Each delivery also carries a new x-client-id header holding your\nclient app id.
What changed
\nx-client-id header containing your client app\nid, so a receiver handling more than one app can tell them apart without\nparsing the body.Action required
\nOnly if you restrict inbound traffic by source IP. Contact us for the current\naddress list and add it to your allowlist — we do not publish the addresses\nhere. We will give advance notice before they ever change.
\nIf you do not filter by source IP, nothing changes for you.
", "url": "https://vezgo.com/docs/changelog/2026/06/15/webhook-static-source-ips", "title": "Webhooks now come from a fixed set of source IPs", "summary": "Webhook deliveries originate from a small, static set of addresses that can be allowlisted, and each delivery carries an x-client-id header.", "date_modified": "2026-06-15T00:00:00.000Z", "tags": [ "api" ] }, { "id": "https://vezgo.com/docs/changelog/2026/04/14/duplicate-connection-id", "content_html": "Connecting an account that is already linked to a user has always been rejected\nwith 409 Conflict. That response now carries existing_institution_id, so\nyou can point the user at the account they already have.
Direct API
\nPOST /accounts and PUT /accounts/:id return it alongside the existing\nmessage:
{
\"message\": \"This connection is already linked to your account.\",
\"existing_institution_id\": \"<id of the already-linked account>\"
}
Connect widget
\nThe DUPLICATE_CONNECTION error event now includes it at the top level of the\npostMessage payload:
{
event: \"ERROR\",
data: {
type: \"DUPLICATE_CONNECTION\",
existing_institution_id: \"<id of the already-linked account>\",
error: { /* unchanged */ }
}
}
Action required
\nNone — this is purely additive and existing 409 handling keeps working. If you\nwant to use it, the field lets you replace a generic error with something like\n\"you already have this account connected\", linked to the existing connection.
On EVM chains, a transaction's native amount is now negative when the\nconnected wallet sent it, and positive otherwise. This corrects the direction\nreported for swaps.
What changed
\nfrom_address: if it matches the connected wallet, amount\nis negative; in every other case it stays positive.Action required
\nIf you derive direction from the sign of amount, check that your logic handles\nnegative values on these chains — previously an outgoing transfer could arrive\npositive.
Because only new transactions are affected, a wallet can hold both conventions\neither side of this date. If that matters for your reconciliation, contact us\nand we can reprocess the earlier transactions for an account.
", "url": "https://vezgo.com/docs/changelog/2026/01/28/evm-outgoing-amount-sign", "title": "Outgoing EVM transactions now report a negative amount", "summary": "On nine EVM chains, the native amount is negative when the connected wallet is the sender, fixing the direction of swap transactions.", "date_modified": "2026-01-28T00:00:00.000Z", "tags": [ "breaking" ] }, { "id": "https://vezgo.com/docs/changelog/2025/09/04/sui", "content_html": "Vezgo now supports Sui. Users connect by pasting their address — read-only,\nwith nothing to install and nothing to approve.
\nWhat you get
\nticker_address —\nits full Move coin type — alongside its tickerparts[], so a swap is one transaction rather than severalfees[], computed as computation + storage − storage rebate, and the\nblock digest in transaction_hashAction required
\nNone. Match coins on ticker_address, not ticker: Sui tickers come from on-chain\ncoin metadata and are not unique, so two unrelated coins can publish the same\nsymbol.
Everything that moves in a single on-chain transaction is now reported as one\nVezgo transaction, grouped by its hash, instead of one transaction per\nmovement.
\nWhat changed
\nmisc.tokenTransfers.misc.nftTransfers.{
\"misc\": {
\"tokenTransfers\": [
{
\"direction\": \"send\",
\"ticker\": \"USDT\",
\"token_name\": \"Tether USD\",
\"amount\": -106707.39014,
\"from_address\": \"0x<connected wallet>\",
\"to_address\": \"0x<counterparty>\",
\"fiat_ticker\": \"USD\",
\"fiat_value\": 106682.96961903569,
\"token_address\": \"0xdac17f958d2ee523a2206206994597c13d831ec7\",
\"possible_spam\": false,
\"verified_contract\": true
}
],
\"nftTransfers\": [
{
\"direction\": \"send\",
\"token_address\": \"0x<collection contract>\",
\"contract_type\": \"ERC721\",
\"amount\": 1,
\"from_address\": \"0x<connected wallet>\",
\"to_address\": \"0x0000000000000000000000000000000000000000\",
\"possible_spam\": false,
\"verified_collection\": false
}
]
}
}
Action required
\nIf you read token or NFT movements as transactions of their own, read\nmisc.tokenTransfers and misc.nftTransfers instead. Expect fewer transactions\nfor the same wallet — a swap that previously arrived as several rows is now one.
Vezgo now supports TON, listed as Gram (Toncoin). Users connect by pasting\ntheir wallet address — read-only, with nothing to install and nothing to\napprove.
\nWhat you get
\nticker_address\n— the jetton's contract — alongside its tickermisc.op_namemisc.aborted, since they still cost\na feeAction required
\nNone. Two points worth knowing: jetton amounts are not in the transaction\nfeed — a jetton transfer appears as its TON leg, so read jetton holdings from\naccount.balances[]. And match jettons on ticker_address rather than ticker,\nsince jetton tickers come from on-chain metadata and are not unique.
Vezgo now supports Hedera. Users connect with their account id — read-only,\nwith nothing to install and nothing to approve.
\nWhat you get
\nmisc.origin_idAction required
\nNone. One point worth knowing: a single on-chain transaction that moves both\nHBAR and an HTS token arrives as two Vezgo transactions — one per asset —\nsharing the same transaction_hash. Group on that field if you need the\non-chain transaction as a whole.
Vezgo now supports Coinbase Prime, Coinbase's institutional custody and\ntrading platform. Users connect with a Prime Access Key, Signing Key and\nPassphrase — a read-only View key is enough.
\nWhat you get
\ncrypto or\ncash_equivalentparts[], plus the activity\nfeed: deposits and withdrawals — external, internal, sweep and Coinbase-linked\n— and conversionsmiscAction required
\nPrime lists some network-specific assets under a prefixed symbol — ARBUSDC is\nUSDC on Arbitrum — and those arrive verbatim. There is no ticker_address or\nnetwork field to resolve them, so map those symbols to the underlying asset on\nyour side. Custodial holdings carry no ticker_address at all, so match on\nticker for this connector.
Vezgo now supports Swyftx. Users connect with a Swyftx API key — read-only,\nwith nothing to install and nothing to approve.
\nWhat you get
\ncash_equivalent and crypto typed crypto, so the two\nare separable without a symbol list of your ownAction required
\nSwyftx provides balances only — there is no transaction history. The\nprovider reports features.transactions: 0, so read that before building\nagainst /accounts/:id/transactions for this connector: it will return nothing.
The Binance connector now covers every major wallet type on the account,\nrather than spot alone — roughly six times the data it returned before.
\nWhat you get
\nAction required
\nNone, but expect more: a Binance connection will return more accounts,\npositions and transactions than it did before. If you present accounts\nindividually, check that the new wallet types appear sensibly in your UI.
", "url": "https://vezgo.com/docs/changelog/2024/02/15/binance-expanded-wallets", "title": "Binance covers every major wallet type", "summary": "Spot, Margin, Earn, Funding, Futures, NFTs and Auto-Invest, with real-time spot updates and historical orders.", "date_modified": "2024-02-15T00:00:00.000Z", "tags": [ "coverage" ] }, { "id": "https://vezgo.com/docs/changelog/2024/02/15/okx-transactions", "content_html": "OKX now returns transaction history for spot and staking.
\nAction required
\nNone, but note a hard limit we cannot work around: OKX's API exposes only the\nlast three months of trades. Older trades cannot be retrieved, so an OKX\naccount's balances will not be fully explained by its trade history.
", "url": "https://vezgo.com/docs/changelog/2024/02/15/okx-transactions", "title": "OKX transaction history for spot and staking", "summary": "Spot and staking transactions for OKX, with trades limited to the last three months by OKX's API.", "date_modified": "2024-02-15T00:00:00.000Z", "tags": [ "coverage" ] }, { "id": "https://vezgo.com/docs/changelog/2024/02/15/stellar", "content_html": "Vezgo now supports Stellar. Users connect by pasting their address.
\nWhat you get
\nAction required
\nNone.
", "url": "https://vezgo.com/docs/changelog/2024/02/15/stellar", "title": "Stellar is now available", "summary": "Balances, positions and transaction history for a Stellar address.", "date_modified": "2024-02-15T00:00:00.000Z", "tags": [ "new-connector" ] }, { "id": "https://vezgo.com/docs/changelog/2024/02/15/trezor-connect", "content_html": "Trezor hardware wallets now connect through Trezor Connect, the same way\nLedger connects through Ledger Live.
\nWhat you get
\nAction required
\nNone. Private keys never leave the device.
", "url": "https://vezgo.com/docs/changelog/2024/02/15/trezor-connect", "title": "Trezor connects through Trezor Connect", "summary": "Trezor hardware wallets connect through Trezor Connect, so users no longer have to find their public address in device settings.", "date_modified": "2024-02-15T00:00:00.000Z", "tags": [ "new-connector" ] }, { "id": "https://vezgo.com/docs/changelog/2023/10/25/arbitrum", "content_html": "Vezgo now supports Arbitrum, the Ethereum Layer 2. Users connect by pasting\ntheir address.
\nWhat you get
\nAction required
\nNone.
", "url": "https://vezgo.com/docs/changelog/2023/10/25/arbitrum", "title": "Arbitrum is now available", "summary": "Balances, positions and transaction history for an Arbitrum address.", "date_modified": "2023-10-25T00:00:00.000Z", "tags": [ "new-connector" ] }, { "id": "https://vezgo.com/docs/changelog/2023/10/25/binance-auto-invest", "content_html": "Binance Auto-Invest accounts — recurring purchases on a schedule — are now\nreturned, along with their transactions.
\nAction required
\nNone. A Binance connection with Auto-Invest plans will return more accounts and\ntransactions than it did before.
", "url": "https://vezgo.com/docs/changelog/2023/10/25/binance-auto-invest", "title": "Binance Auto-Invest accounts", "summary": "Auto-Invest plan accounts and their transactions are now returned for Binance.", "date_modified": "2023-10-25T00:00:00.000Z", "tags": [ "coverage" ] }, { "id": "https://vezgo.com/docs/changelog/2023/10/25/binance-orders", "content_html": "Order data for Binance — both live and historical — is now available on\ndemand, so open orders can be read rather than inferred from filled trades.
\nAction required
\nNone by default. This is opt-in — get in touch for access. See the Real-time\ndata and Order sections of the API documentation.
", "url": "https://vezgo.com/docs/changelog/2023/10/25/binance-orders", "title": "Binance live and historical orders", "summary": "Open and historical order data for Binance, on demand.", "date_modified": "2023-10-25T00:00:00.000Z", "tags": [ "api" ] }, { "id": "https://vezgo.com/docs/changelog/2023/10/25/bitmart-transactions", "content_html": "BitMart now returns transactions alongside balances and positions, for spot\nwallets.
\nAction required
\nNone.
", "url": "https://vezgo.com/docs/changelog/2023/10/25/bitmart-transactions", "title": "BitMart transaction history", "summary": "Balances, positions and transactions for BitMart spot wallets.", "date_modified": "2023-10-25T00:00:00.000Z", "tags": [ "coverage" ] } ] }