What happened
Zapper has shut down. As of 3 August 2026 the company's products and services stopped, including the web and mobile applications and the Zapper API. The address this page's visit link points to now serves a farewell notice and nothing else, so there is no product left to try, no account to open and no key to request.
The notice is signed by the co-founder and chief executive and gives the arc rather than a cause: nearly seven years, more than two million monthly active users at its peak, and more than $13 billion in transaction volume at its best. The only explanation offered is that Zapper did not realise its mission in the way the team originally hoped. No successor product was announced, and the two things the notice does point to are migration paths rather than a revival.
What it was, and why a prediction market reader cared
Zapper was one of the earliest and best-known onchain portfolio trackers: connect a wallet and see tokens, DeFi positions, NFTs and transaction history across many chains in one view, with the data also available to developers through a GraphQL API. For most of its life that made it a general-purpose tool rather than a prediction market one.
What earned it a place in this directory was a later addition: Polymarket position tracking inside the dashboard. Rather than keeping prediction market exposure in a separate tab or a separate product, Zapper read a wallet's open Polymarket positions and showed them beside everything else — the markets held, the side taken, the current value and the performance of the position. Zapper's own social account promoted it, and prediction market directories catalogued it as a Polymarket dashboard. That combination was unusual, and it is the part of Zapper this page exists to record.
The shape of the coverage while it ran
Zapper claimed support for 50-plus blockchains, most of them EVM, and its coverage was broader in chain terms than deep in protocol terms. Zerion's pre-shutdown comparison of the two APIs, published in March 2026, describes the same split: Zapper reached non-EVM chains such as Bitcoin for basic balances, while a general-purpose tracker's depth on long-tail DeFi protocols lagged behind rivals that tracked thousands of them. Two documented limitations are worth noting because they shaped what users actually saw: Solana support returned token positions only, without transaction history or price data, and Bitcoin support returned balances only.
On the portfolio side the API grouped positions by app, with each position broken into meta-types such as supplied, locked, claimable and borrowed, alongside token balances, NFT collections and human-readable transaction descriptions. For a prediction market user the practical consequence was that a Polymarket position could appear as an app position in the same response as a lending deposit — a genuinely useful unification, and one that depended entirely on Zapper maintaining the Polymarket integration.
Where its users were told to go
Two exits were published, and both still matter to anyone who had money or code tied to Zapper. Former API customers are directed to Zerion, which maintains a migration guide mapping Zapper's main queries — the portfolio query for token, app and NFT balances, and the transaction history query — onto its own endpoints, with copy-pasteable code and field-level mappings, and which offers migration discounts to teams making the switch. Former Zapper Wallet users are directed to Privy to export their private keys.
For readers who simply want to see a Polymarket position, the venue's own interface and API do that directly, and the other tools listed in this directory were built for it. Zapper was the convenient general-purpose option, not the purpose-built one.
Why this page still exists
Directories that quietly delete dead products leave their readers worse off in two ways: inbound links rot, and people who remember the name find nothing that tells them what happened. This entry stays as a record — the shutdown date, the scope of what stopped, what the Polymarket integration did, and the migration paths the vendor itself published — with no live-tool framing and no suggestion that anything here can still be used.





































