Skip to content

Connect Bybit

Bybit, filed like the rest of your money

A read-only key, and Bybit becomes ledger lines: fills, fees, deposits and withdrawals, priced and kept for the tax year.

Read only, and refused if the key can trade or withdraw. How we check that is below.

Connections · Bybit

The Bybit card on the Connections screen and its drawer: what Orla reads, what it never does, and the read-only key it asks for. Nothing is saved until Bybit has answered what the key may do, and a key with more than read rights is refused.

What lands, and what does not

Spot comes across. Perpetuals do not, and we would rather say so here

Bybit is a derivatives venue first, and that decides what can be imported.

  • Spot fills arrive as two legs, what left and what arrived, so a disposal carries the price it happened at.
  • Perpetuals and futures are not imported as trades. A position is not a disposal.
  • Your balance mirrors from Bybit either way, so net worth is right even with gaps in history.
  • Deposits and withdrawals arrive as transfers and pair up with your own wallets.
  • The first sync reaches back to 1 January of the previous calendar year, then keeps up hourly.

The key you give us

Bybit marks a key read only. We read that mark and believe nothing else

Promising read only is easy. This is what we do instead of promising.

Before the connection exists
The key is tried against Bybit first, and nothing is stored until it answers.
What we ask Bybit
Their own answer: Bybit reports whether a key is read only, and a key that comes back as read and write is rejected outright.
If the flag is missing
Refused. An answer without that flag is treated as no answer, because a venue that renamed it would otherwise pass every key as read only.
Where the secret lives
Encrypted at rest once it is accepted, and never returned by our API again, not to you and not to us.
If the key stops working
Sync stops after repeated auth failures, the space owner gets one message, and you replace the key in place.

One thing worth knowing

Sending coins from Bybit to your own wallet is not a sale

Paired, it is one move; unpaired, it is left out of the disposals instead of being counted as a sale.

Questions

The questions people ask before they connect it

Can Orla trade or withdraw on my Bybit account?

No. Bybit reports whether an API key is read only, and a key that comes back as read and write is rejected before the connection is created. If that flag is missing from the answer, the key is refused as well: an answer we cannot read is treated as no answer.

Does it import my history or just the balance?

Both, and the history is the point. Fills, deposits and withdrawals become transactions in the ledger, so the capital gains engine can work a cost basis out by lot. The first sync reaches back to 1 January of the previous calendar year, which covers the current tax year and the one before it as well.

Will moving coins to my own wallet look like a sale?

No. The withdrawal is matched to the arrival on the other side, by transaction hash where the venue gives one and by coin, amount and date where it does not, and the pair becomes one internal move. An unmatched withdrawal is left out of disposals rather than counted as a sale of any kind.

Other exchanges

Connect Bybit, and see the year add up

Exchanges connect on every plan, the free one included. A plan counts the rows synced in a month, not the connections.

Binance →
Spot fills as two legs, fees on their own line, transfers joined to the wallet.
OKX →
Key, secret and passphrase, with the permission list read before any is saved.
Coinbase →
Fills, fees and transfers as transactions, rather than a balance that answers nothing when January comes.
Kraken →
Publishes no key permissions, so Orla asks the venue itself with two requests that cannot execute.
Hyperliquid →
No key at all: equity, deposits and daily results from a public address.

See it on your own books

Thirty minutes: we connect an account, drop a real bill in, and close a month together.