Bit2Me APIRate limits
Starter, Medium, and Pro request-per-minute limits for the Bit2Me API.
All gateway HTTP endpoints enforce usage limits. Exceeding them can return:
| Code | Meaning |
|---|---|
| 429 | Too many requests in the timeframe |
| 418 | The user has been banned from accessing the API |
| Tier | Max RPM |
|---|---|
| Starter | 600 |
| Medium | 800 |
| Pro | 1000 |
To request a new tier, contact support. Do not assume an ad-hoc raise.
If you receive 429, back off and retry. Check status.bit2me.com if failures cluster. If this persists, open a support ticket.
Stay inside the published limits: repeated violations get you banned with 418.
Spot Trading API
Pro REST also limits some endpoints per user account or per IP (for example 15 order creations per second), and each market limits open orders. See Spot Trading API rate limits.
WebSockets
WebSocket connections are limited by IP and share the rate limiter with HTTP calls:
- More than 50 concurrent connections from the same IP → handshake 429
- More than 50 messages per second on a connection → close 4001
The Spot Trading API WebSocket (wss://ws.bit2me.com/v1/trading) also limits each command per connection, from 1 to 50 messages per second, and aborts the connection when a limit is reached. See Spot Trading API WebSocket rate limits.