SnapTrade review

SnapTrade is a hosted API for brokerage connectivity, not a brokerage or a self-hosted server. It sits between your app and supported brokerages: your product connects a user's account through SnapTrade, then accesses investment data or trading operations where the brokerage supports them. SnapTrade says it connects to 40+ brokerages and more than 450 million investor accounts.

The API addresses a common integration problem: each brokerage can expose different account data and trading capabilities. SnapTrade provides balances, holdings, orders and transactions, and says it normalizes security tickers, currencies and exchanges. Its connectivity features also include webhooks and secure authentication. Trading can cover stocks, ETFs, crypto and options where supported.

That makes it a fit for portfolio tracking, investment analysis, holdings validation and embedded trading. It does not remove the need to check individual brokerage coverage: a connection or trading feature in one institution does not guarantee availability at another.

The integration surface is SnapTrade's API, with SDKs and webhooks listed as supporting features. The homepage says developers can start with SDKs “in your language of choice,” but does not name languages. Confirm current SDK language support and the API's request and response details in SnapTrade's docs before selecting a stack. The homepage does not name a CLI, plugin system or a specific API protocol, so plan around the API and verify the exact integration options with the vendor.

The data model is intended to reduce brokerage-specific normalization work: SnapTrade unifies security tickers, currencies and exchanges, and provides balances, holdings, orders and transactions according to the app's use case and syncing needs. Webhooks are listed among its connectivity features; confirm event coverage, delivery behavior and retry handling in the docs before relying on them for state changes.

A practical integration review should also check which brokerages support the exact data and trading operations your product needs. SnapTrade's “where supported” qualification matters: coverage for account data and for placing trades may differ.

Build costs $0 per month and includes up to five brokerage connections, real-time data, trading and Discord community support. It is the free option for developing and testing integrations, but the five-connection limit makes it a test tier rather than a plan for an expanding commercial app.

Launch costs $100 per month, plus connected-user charges. Real-time access with trading is $2 per user per month; Daily access is $1 per user per month and read-only. Daily manual sync costs $0.05 per connection per sync. Personal/OAuth users are listed as free for a limited time, so confirm the terms before counting on that rate in a production forecast. Launch includes unlimited connected users, but that does not mean unlimited usage is free.

Custom pricing is tailored and includes volume discounts, higher rate limits, dedicated Slack and priority support, and integration assistance. The pricing page lists monthly billing; it does not list annual billing. Ask SnapTrade for the Custom quote and applicable rate limits before sizing a production deployment.

SnapTrade is presented as a hosted API, not as software to install in your own environment. The vendor does not publish a source licence or self-hosting option in its product information, so teams should plan for a vendor-managed dependency rather than assume they can run the connectivity layer themselves.

The integration also introduces some lock-in: your app depends on SnapTrade's brokerage coverage, normalized data model and supported trading operations. Keep your own internal account and portfolio models, and avoid making SnapTrade-specific response shapes the only representation of financial data in your application. That makes it easier to replace the provider or add another integration later.

Before signing, ask how users' data can be exported, what happens to connected accounts and stored data when service ends, and whether SnapTrade assists with migration. The vendor's published plan details do not describe a self-service migration path.

SnapTrade says it has connection success rates above 95% and long-lived connections. Those are vendor claims, not a guarantee for every institution or user. A Reddit commenter described a Wealthsimple connection through SnapTrade as stable over a year, while a separate thread reports that Questrade was not onboarding new API developers at the time of the discussion. Treat brokerage-specific access as a production dependency and verify the current status directly.

The Build plan caps access at five brokerage connections. Launch pricing identifies per-user and manual-sync charges; Custom includes higher rate limits, but the vendor does not publish numeric quotas in the plan details. Ask for endpoint-level limits, webhook delivery and retry behavior, sync timing, incident response and service commitments before launch.

The homepage lists secure authentication, but teams should review the vendor's security and compliance documentation for their requirements. Also test failure handling in your own integration: users need clear recovery paths when an institution disconnects or an operation is unavailable.