Skip to main content
Brokerage connections let you pull live portfolio data from your investment accounts. Unlike banking connections that sync transactions, brokerage connections provide access to your current holdings and trade history.
Brokerage accounts are available on the Professional plan (or during an active trial on any plan). See pricing for details.

​
Supported brokerages

Not all brokerages support both holdings and trades. The table below shows what each brokerage supports through SnapTrade.

​
Brokerages

​
Crypto exchanges

Brokerage support is provided by SnapTrade. Availability may change as SnapTrade adds or updates integrations.

​
Data available

Holdings

Current positions across your investment accounts: symbol, quantity, average price, market value, and unrealised P&L.

Trades

Historical trade records: buys, sells, quantities, prices, fees, and settlement dates.

​
How it works

Brokerage data is fetched live from your broker each time you request it. No investment data is stored on Redbark servers. When you connect a brokerage account, Redbark links to your broker through SnapTrade. SnapTrade handles the authentication with your brokerage and provides a secure connection for reading your portfolio data.

​
Holdings

A holding represents one instrument in one brokerage account. Some brokers report several positions for the same instrument, such as staked and unstaked units. Redbark returns one holding with aggregate totals and keeps the original rows in positions. Each holding includes: For an aggregate, quantity is the sum, averagePrice is weighted by quantity, and marketValue and unrealizedPnl are summed. currentPrice comes from the largest position. If any row omits an average price, market value, or unrealised P&L, that aggregate is null rather than a partial value. positions always contains at least one row.
All monetary values are returned as strings to preserve decimal precision. Parse them as decimals in your application.

​
Trades

A trade is a completed buy or sell order. Each trade includes:

​
Connecting a brokerage account

1

Go to Connections

Open the Connections page in the dashboard.
2

Add a brokerage connection

Click Add Connection and select Brokerage. This option is available on the Professional plan, or during an active trial.
3

Select your broker

Choose your brokerage from the list.
4

Authenticate

Log in to your brokerage account through the SnapTrade connection flow. Your credentials are handled by SnapTrade and are never stored on Redbark servers.
5

View your accounts

Once connected, your brokerage accounts appear on the Connections page alongside your bank accounts. Each account shows the institution name and account type.Some brokerages can take a couple of days to surface accounts after the initial connection — SnapTrade runs the account fetch in the background. You’ll receive an email when the accounts are ready.

​
Accessing brokerage data

Brokerage data is available through the REST API:
  • List Holdings returns current positions for a brokerage connection
  • List Trades returns paginated trade history with date filters
The /holdings and /trades endpoints require brokerage access: an active (or past_due) subscription on a Professional price, or an active trial on any plan. A Developer-plan key that has general API access but not brokerage gets a 403 professional_required. A key with no API access at all (for example a Saver-plan key) gets a 403 plan_upgrade_required.

​
Refreshing data

Holdings and trade data are fetched live from your broker on each API request. Responses are not cached, so every request reflects the latest data the broker exposes. Both endpoints use the “heavy” rate-limit preset and a separate per-key concurrency limiter that caps in-flight requests at 4. Excess concurrent requests receive a rate-limit error until a slot frees up.

​
Removing a brokerage connection

Select Delete from the three-dot menu on a brokerage connection card. This revokes the SnapTrade link to your broker. Any syncs that use accounts from this connection are immediately disabled. A background cleanup job then deletes only the syncs left with zero remaining accounts; a sync that still has accounts from another connection is kept.