Use a separate read-only key for each exchange, connect it once, then verify the first import before trusting any statistic. Trader’s Second Brain supports direct Binance and Bybit connections, keeps the accounts distinguishable inside one journal, and checks active connections on a 15-minute schedule. API availability, rate limits, account mode, and the exchange’s history window can delay or narrow a sync, so “connected” and “complete” are not the same status.
This guide covers the international Binance and Bybit routes shown in the server-rendered cards below. Residence and legal entity can change product access, API domains, and even whether a third-party connection is available. Confirm the exact account in the exchange UI and in TSB’s live source directory before creating a credential.
What Binance and Bybit API Sync Actually Does
API sync removes repeat data entry. TSB’s server asks the exchange for permitted account history, normalizes supported fills and closed positions, and writes new or updated journal records. Binance can be scoped to spot and/or derivatives; the current connector covers spot, USD-M futures, and COIN-M futures. The Bybit V5 route covers spot, linear and inverse derivatives, plus supported options history.
That does not mean every exchange event becomes one perfect “trade.” Exchanges expose fills, orders, realized P&L, commissions, and funding through different endpoints. A journal has to group those events into positions and avoid attaching one fee to the wrong close. TSB records incomplete-surface and ambiguous-cost warnings instead of silently manufacturing certainty. The broader crypto trading journal workflow explains how to turn that reconciled ledger into a review process.
| Question | Reliable answer | What to check |
|---|---|---|
| Is the connection automatic? | Yes, after a successful setup; TSB’s current policy schedules Binance and Bybit checks every 15 minutes. | Last checked, last successful import, warnings, and next scheduled check. |
| Is it instant? | No. Exchange publication delays, rate limits, retries, and worker timing can add latency. | Compare the exchange close time with the journal’s latest imported record. |
| Is all history included? | Not automatically. Initial and manual backfill scopes are bounded by provider and connector rules. | Reconcile counts by market, symbol, date range, and account. |
| Are fees and funding included? | They are imported where the exchange exposes them and they can be attached without false attribution. | Gross P&L, commission asset, funding rows, and net P&L. |
The Safe Permission Model
Both exchanges separate read access from transaction authority. Binance documents private account history under USER_DATA and says API keys can be restricted by endpoint type; Bybit’s API-key response explicitly distinguishes read-only from read-and-write keys. Use that separation aggressively:
- Create one new key only for TSB. Do not reuse a bot, tax-service, or trading-terminal key.
- Enable reading only. Leave order placement, cancellation, withdrawals, transfers, and every other write-capable permission off.
- Never paste the key or secret into support chat, email, notes, or a screenshot. Enter them only in the authenticated TSB exchange-connection form.
- Revoke first if either value may have leaked. Read-only sharply limits transaction authority, but exposed balances, positions, and history are still sensitive.
- Use IP restrictions only with the sync server’s correct egress address. Whitelisting your laptop’s IP does not help when TSB’s server makes the API request.
How TSB stores the credential: the connection endpoint tests the supplied pair, then encrypts the API key and secret before persistence using the application’s current authenticated encryption format. This is defense in depth, not permission to create a write-enabled key.
See Binance’s official request-security documentation and Bybit’s API-key information contract for the current provider fields. Exchange controls can change; their live permission screen is controlling.
Connect Binance to TSB
- Open Binance API Management on the web and create a dedicated system-generated key with a descriptive name such as
TSB journal read only. - Complete Binance’s identity and two-factor checks.
- Keep reading enabled. Leave spot/margin trading, futures trading, transfers, and withdrawals disabled. Journal access does not require order authority.
- Copy the key and secret once. Keep the Binance tab open until the TSB test succeeds.
- In TSB, open Settings → Exchanges, choose Binance, select Spot, Derivatives, or both, and enter the credential pair.
- Connect, then review the detected product surfaces and the first sync status. Do not delete the Binance key until the test and reconciliation are complete.
Binance spot history is symbol-scoped. TSB discovers a bounded set of active or previously known symbols rather than pretending a BTC-only request represents the whole account. A newly connected automatic scan is deliberately narrow, while manual replay offers explicit date and symbol controls. If an inactive pair is absent, run a symbol replay or use the exchange export instead of assuming the account had no trades.
Connect Bybit to TSB
- Open Bybit API Management in a web browser; Bybit’s current help center says new API keys are created on the website, not in the mobile app.
- Create a system-generated key for a third-party application or the available equivalent for your legal entity.
- Select read-only and leave contract, spot, options, wallet-transfer, and withdrawal write permissions off.
- Complete two-factor verification, then copy the key and secret.
- In TSB Settings → Exchanges, choose Bybit, choose the required market scope, and connect.
- Read the account-mode result. A key/domain mismatch, unsupported regional endpoint, unmatched IP, or incompatible account mode can prevent a valid-looking key from working.
Bybit V5 unifies spot, derivatives, and options APIs, but legal-entity domains and account capabilities still differ. The current Bybit documentation lists separate regional endpoints and reports whether a key is read-only, IP-bound, and attached to a unified account. If you trade on a regional Bybit entity that the connector does not yet route, use a supported export path rather than sharing broader permissions.
For a venue-level decision beyond journaling, read the exact-scope Bybit vs Binance comparison. The exchange cards here supply current catalog facts; they do not automatically change this setup guidance or its security verdict.
Initial Sync, History, and Backfill
There is no honest universal promise such as “Binance gives six months and Bybit gives two years.” Endpoint retention, symbol requirements, account mode, market, pagination, and the journal’s replay guardrails all matter. TSB’s current manual backfill control offers 7, 14, 30, 90, or 180 days for Binance and Bybit. Deeper replays can require an exact symbol; the product deliberately rejects unsupported whole-account requests rather than returning a complete-looking partial answer.
| Task | Best route | Acceptance check |
|---|---|---|
| Keep new activity current | Automatic API checks | Last checked advances; latest closed activity reconciles after provider delay. |
| Replay a recent gap | Manual API backfill for the exact market and date window | Compare imported, updated, skipped, and warning counts. |
| Recover an older or inactive symbol | Symbol-specific replay where supported | Match execution IDs, dates, quantity, and costs. |
| Load history outside the reliable API surface | Official exchange export plus CSV import | Use a representative file first; prevent duplicates at the overlap. |
The safest migration is API for ongoing activity plus a controlled file backfill for missing history. Follow the CSV mapping and reconciliation guide, and keep a small overlap window so duplicate protection can be checked before a full import.
Reconcile the First Sync
Do not validate with total P&L alone. Two wrong groupings can cancel each other and produce a correct-looking total. Choose a short period containing at least one partial close, one fee, and—if relevant—one funding event. Compare:
- Population: same account, market, symbols, and closed-event date range.
- Identity: exchange execution or order IDs and no duplicated overlap rows.
- Economics: side, quantity, entry, exit, realized P&L, commission currency, and funding.
- Time: raw exchange timestamp, journal timezone, and session date.
- Grouping: partial exits and position flips form the intended journal trade.
- Health: last checked, last successful import, warning text, and next scheduled check tell a consistent story.
If a field is unavailable, treat it as unavailable—not zero. Funding that cannot be attached unambiguously should remain separate or flagged. This evidence discipline is what makes the later performance-analysis workflow useful rather than merely polished.
Troubleshooting by Failure Class
| Symptom | Likely class | Next action |
|---|---|---|
| Invalid key or signature | Whitespace, wrong secret, wrong environment/domain, or clock/signature mismatch | Revoke if exposed; otherwise recreate the pair and reconnect from the correct entity. |
| Permission denied | Required read surface is unavailable or account mode is incompatible | Confirm read access for the chosen market. Do not solve it by enabling order or withdrawal authority. |
| Unmatched IP | The exchange whitelist does not include the server making the request | Use the exact TSB egress address if provided, or remove the restriction and keep the key strictly read-only. |
| Connected, no rows | No closed activity in the window, wrong market scope, new inactive symbol, or provider delay | Check exchange history, scope, last checked, then run a narrow replay. |
| Only some rows arrive | Pagination, rate limit, endpoint failure, retention floor, or incomplete surface | Read the warning; replay a smaller date/symbol slice or use an official export. |
| P&L mismatch | Fees, funding, settlement currency, or partial-close grouping | Reconcile raw events before editing the journal result. |
Manage Binance and Bybit in One Journal
Create two separate connections and give each a clear account label. That preserves source identity while allowing one review surface across venues. Analyze combined results only after both sources pass the same reconciliation checklist; otherwise a clean Binance feed can hide an incomplete Bybit window, or vice versa.
TSB has processed 600K+ imported trades across its import history, and the canonical registry recognizes 328 exact broker, exchange, platform, and prop-export profiles. These are imported trades and recognized routes—not users, not a claim that every route is automatic, and not trades analyzed by Coach.
The real payoff begins after the ledger is clean. TSB’s AI Coach becomes the decision layer: it routes the selected evidence through data quality, plan compliance, setup risk, market regime, rule testing, and setup-decay lenses, then turns supported findings into a concrete Current Focus. Ask it where fee drag is concentrated, whether a pattern survives by venue or market regime, or which underlying trades support the conclusion. When required evidence is missing, Coach identifies the gap and turns it into a collection task, keeping every surfaced signal traceable. That combination—deep analysis plus evidence integrity—is a serious product advantage.
Bottom Line
For Binance and Bybit, the durable workflow is: dedicated read-only key, exact market scope, successful connection test, first-sync reconciliation, then scheduled API checks with narrow backfills when needed. Use CSV for history the API cannot prove. Once the records reconcile, TSB turns the connection into a continuously reviewable evidence base—and Coach can extract specific, defensible next actions without inventing a story around missing rows.
Disclosure: Trader’s Second Brain is our product. Exchange catalog facts and verified dates render server-side from canonical records; unavailable values show Not verified. The editorial setup sequence, security warnings, and verdict are versioned separately and do not change automatically with the catalog. Product behavior was checked against the local connection, sync-policy, adapter, warning, and encryption contracts on September 10, 2026. See our editorial methodology.
