Bybit trading, from one binary
Crypto perps + spot. Backtest a strategy against stored Bybit data, run it on paper, then mount the same engine live — the code that trades is the code the backtest ran. Bybit mounts paper by default: credentials arm it, and a per-venue ceiling in your policy file caps it.
live exec + recon Live execution, with a reconciliation client that diffs the venue's own report against local state.
What the Bybit bridge does
Execution
Live REST + WS execution
Reconciliation
Dedicated recon client · immediate resync on WS reconnect
Market data
Live feeds
Broker attribution via X-Referer header; read-only reconcile smoke run against the live demo venue.
Order types and flags
What the Bybit bridge can send. These are the venue's own capabilities as the platform records them — where a venue cannot do something, the table says so instead of pretending otherwise.
| Order kinds | market · limit · stop |
|---|---|
| Triggers | stop-loss |
| Amend a resting order | supported — the quantity you send is the order's new TOTAL size |
| Post-only | not supported |
| Reduce-only | supported |
| Multi-leg / combo | not supported |
| Batch submit | no native batch endpoint — orders are sent one at a time |
| Order attribution | an HTTP header (X-Referer) |
Time in force
How each time-in-force resolves on Bybit. A coercion is stated rather than hidden: asking for one and silently getting another is the kind of divergence that shows up as a surprise fill.
| Requested | What happens | On the wire |
|---|---|---|
| GTC | sent as-is | GTC |
| IOC | sent as-is | IOC |
| FOK | sent as-is | FOK |
| GTD | not supported | — |
| DAY | not supported | — |
Margin, data and modelled cost
| Margin modes |
cross · isolated
default: cross
|
|---|---|
| Switching mode | set once, for the whole account |
| Live market data |
trades · bars · depth
|
| Historical backfill |
bars
|
| Modelled commission | 2 bps maker · 5.5 bps taker |
⚠ The commission row is the backtest model — what the simulator charges on a fill for this venue, from the schedule the platform ships. It is not a quote of Bybit's live pricing, it models commission only, and spread, slippage and perpetual funding are separate paths. Check the venue's own current terms before sizing anything on it.
Nothing arms Bybit by accident
Absent credentials are the gate
No Bybit keys in your local credential store, and the venue mounts paper. That is the mechanism, not a setting you have to remember to leave alone.
A ceiling that can only refuse
A per-venue entry in your policy file caps what Bybit may do. It can lower a venue to paper; it can never promote one. A box with no such table mounts every venue on paper.
Keys stay on your machine
One file in your own project folder. No cloud, no account. Keys reach child processes through the environment rather than the command line, and are redacted from logs.
Agent writes are previewed
If you drive Bybit from an agent, every order-writing call previews first and executes only against a token that preview issued. How that works.
Generated from the platform's own per-venue capability tables — this page cannot claim more than the code does. A venue cannot appear here without passing the execution and market-data conformance harnesses, and adding a venue fails those tables' tests until every one of them classifies it. Snapshot exported 2026-09-06.
Backtest Bybit. Then mount it.
Free. Source-available under FSL-1.1; every release becomes Apache-2.0 two years on.
Trading involves substantial risk of loss and is not suitable for every investor. Nothing on this page is investment, financial or trading advice. Vike is not affiliated with, endorsed by or acting as an agent of Bybit; the name is used only to identify the venue this software connects to. Venue availability, pricing and capabilities change — this page states what the shipped software wires today, not a promise about any venue's own service. Orders sent from your accounts remain your responsibility.