Bybit's v5 unified API covers spot, USDT perpetuals, inverse contracts and options over REST and WebSocket, with low derivatives fees. Here's how to get keys and what it costs.
| Use | Costo |
|---|---|
| Market data (REST/WS) | Gratuito |
| Spot trading fee | ~0.1% |
| Perpetuals (taker) | ~0.055% |
| API access | Gratuito |
1. Sign up / log in at bybit.com and complete verification.
2. Vai a Account → API (API Management).
3. Clic Create New Key → System-generated API Keys.
4. Set permissions (Read-Only, or Read & Trade) and add an IP whitelist (required for trade keys).
5. Copia il API Key E Secret — the secret is shown once.
Use Read-Only keys for data/analytics bots. For trading, IP-whitelist is mandatory and worth it. Never enable withdrawal permission unless required. Store the secret in an env var, never in client-side code or git.
Binance has deeper spot liquidity; OKX adds a unified options suite. For just prices, CoinGecko. See Binance E OKX.
Yes. Creating keys and calling market-data endpoints costs nothing — you only pay the normal trading fees on orders the API places, around 0.1% for spot and 0.055% taker on USDT perpetuals.
Log in at bybit.com, go to Account → API, click Create New Key → System-generated API Keys, set permissions (Read-Only or Read & Trade) and an IP whitelist for trade keys, then copy the key and secret — the secret is shown only once.
There is no single global limit. Public market-data endpoints are capped per IP address (commonly around 600 requests per 5 seconds), while private trading endpoints are capped per UID per endpoint per second, with higher ceilings at higher VIP tiers. Exceeding a limit returns HTTP 429.
Use Read-Only keys for data or analytics bots, require an IP whitelist for any trading key, never enable withdrawal permission unless you specifically need it, and store the secret in an environment variable rather than in client-side code or a git repo.
Browse all API guides → · trade safely — size positions with RektCalc.
Not affiliated with Bybit. Exchange link is a referral link.
Bybit enforces rate limits per endpoint, tracked separately by UID (your authenticated account) for trading endpoints and by IP address for public market-data endpoints. There is no single global number: order placement, cancellation, position, and query endpoints each carry their own per-second allowance, and Bybit returns the current state in response headers such as X-Bapi-Limit, X-Bapi-Limit-Status, E X-Bapi-Limit-Reset-Timestamp.
Limits are tiered and increase with account activity and VIP level:
Exceed an endpoint's limit and Bybit responds with HTTP 429 (or an API return code such as 10006/10018) indicating too many requests, so you should throttle using the reset headers and, for high-frequency trading, use WebSocket streams instead of polling REST. If you are checking Bybit API rate limits, the key point is that limits are per-endpoint and tiered by VIP level, not a single account-wide cap.
Compare Bybit with our Binance, OKX, and Bybit-vs-competitors exchange API guides to match rate limits to your trading strategy.