Connect your broker

CSV imports work well for a one-off history load or when no API exists. They fail as a weekly habit: missed files, wrong date ranges, and no automatic capture of new trades. A broker connection keeps Wolfora closer to your custodian’s books without turning Wolfora into a trading terminal.

Your broker’s own app is fine for one account. The gap appears when you also hold a bank PEA, an old neo-broker history, or crypto elsewhere. Connecting a broker into Wolfora is about consolidation — not replacing where you execute orders.

Depending on the broker and the permissions you grant, Wolfora can import transactions and positions, and reuse official performance series when the platform exposes them.

The connection is read-oriented. Wolfora does not place orders on your behalf. Custody and trading stay at your broker; Wolfora stores synced data for analytics in your portfolio accounts.

After the first sync, verify positions and a recent trade against your broker’s statement before you trust long-horizon charts.

In Wolfora, open Portfolio setup and choose your broker from the list. Complete the consent flow your broker requires — often OAuth — for the environment your account actually uses (demo vs live must match).

Grant only what is needed for portfolio sync. Prefer least privilege.

After consent, run a sync. Positions and history should appear under your linked portfolio account in Wolfora. If nothing lands, check environment mismatch first, then re-consent, then contact support with any broker-side error message.

Label the Wolfora account clearly (for example “Bank PEA” or “Global brokerage”) so envelope semantics stay readable when you add other brokers or CSV accounts later.

If a broker hosts your PEA, keep that legal wrapper in mind when you analyse tax — Wolfora consolidates numbers; it does not turn a PEA into a CTO. See the PEA vs brokerage guide for envelope strategy.

If you hold both a PEA and a CTO — even at the same institution — prefer separate Wolfora accounts that mirror those envelopes, then use the global portfolio view for totals.

Treat your broker as source of truth for executions. If a fill looks wrong in Wolfora, compare with the broker trade history before editing by hand.

Re-sync after heavy trading days or corporate actions. Spot-check dividends and splits rather than assuming perfection on day one.

Combine automatic sync with CSV imports for brokers without APIs so each venue is one pillar of a multi-broker tracker, not a silo. Read the multi-broker overview if you are structuring accounts for the first time.

Complete consent only on the real Wolfora domain you trust. Check the URL before approving broker access.

If you revoke access at the broker, reconnect in Wolfora promptly so sync does not silently stall while you keep trading.

When you close a broker account, disconnect the integration in Wolfora so stale positions do not linger in consolidated allocation.

Open positions in Wolfora match your broker within normal FX and mark timing.

Recent fills appear without duplicate rows from a parallel CSV import of the same period.

Your global allocation chart includes this broker plus every other venue you care about — not one account alone in a silo you still open three apps to interpret.