Bybit

Automate a Bybit account
you already hold

Both unified and classic accounts connect the same way, and each is treated as its own risk book with its own ceilings.

The connection

What we ask for, and what we refuse.

Trade scope only
A key with trade permission. Vectorhelm places and cancels orders and does nothing else with the account.
Trade scope only
Unified and classic
Both are supported and both carry their own caps, so moving between them does not silently change your risk configuration.
Own caps
Revocable from your side
Revoke at Bybit and the routes stop immediately.
Your control

Bybit specifics

Two account types and a strict clock. Both cause connection problems that look like key problems.

Unified vs classic
A Unified Trading Account shares collateral across products; a classic account keeps them separate. The same strategy sizes differently on each, so the account type is worth knowing before you deploy.
Account type
The 5-second timestamp window
Bybit rejects a request whose timestamp is more than about five seconds from its server clock — returned as retCode 10004, which reads like a signature error. It is clock drift, not credentials.
retCode 10004
The 20-second heartbeat
Bybit closes an idle WebSocket after roughly twenty seconds without a ping. A stream that dies quietly and reconnects is normal; one that dies and does not is what the route halts on.
WebSocket
Perps carry funding
Perpetual funding is charged periodically and is a real cost. It appears in your P&L here because a figure that ignores funding is not a figure about your account.
Charged

Connect Bybit, deploy a strategy on demo, and see how unified-account sizing behaves before you point it at funds.