Bybit API · 9 min
Bybit V5 API: what actually changes when you move a bot to it
One account model, one set of endpoints, and a handful of details that silently break bots ported from earlier versions.
Blog
V5 REST and WebSocket in practice: signing, streams, fills, limits and the errors that survive testing.
One account model, one set of endpoints, and a handful of details that silently break bots ported from earlier versions.
A dropped WebSocket is not an error to log. It is a moment when your bot's picture of the world and reality quietly diverge.
A limit order that fills halfway leaves you with a position nobody planned, a stop sized for a position you do not have, and an average price your code has not recomputed.
Limits never bite when the market is calm. They bite in the minute when your bot urgently needs to cancel, and that is the minute the design has to be built for.
Two independent legs on one symbol sound like more control. Sometimes they are. Often they are a way to pay funding on both sides while feeling hedged.
Most key incidents are not sophisticated. A key ends up in a repository, a chat message, or an environment that more people can read than anyone intended.
We write about what we build. If you need it built, get in touch — scoping is free.