LBank · Rate Limits

Lbank Rate Limits

LBank enforces per-endpoint request rate limits using a rolling 10-second window. Order creation and cancellation endpoints are limited to 500 requests per 10 seconds. All other REST endpoints are limited to 200 requests per 10 seconds. WebSocket connections require ping/pong heartbeat responses within 60 seconds to prevent disconnection. Error code 10004 is returned when request frequency limits are exceeded.

Lbank Rate Limits is the machine-readable rate-limit profile for LBank on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests_per_10_seconds and ping_interval.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Cryptocurrency, Exchange, Trading, Market Data, and Rate Limiting.

3 Limits Throttle: 10004
CryptocurrencyExchangeTradingMarket DataRate Limiting

Limits

Order Create / Cancel (REST, per API key) account
requests_per_10_seconds
500
Applies to POST /v2/supplement/create_order.do and POST /v2/supplement/cancel_order.do and equivalent v1 order creation and cancellation endpoints. 500 requests maximum in any rolling 10-second window per API key.
General REST Endpoints (per API key / IP) account
requests_per_10_seconds
200
All REST endpoints other than order creation and cancellation are limited to 200 requests per 10-second rolling window. This covers market data, account info, order queries, wallet operations, and all other endpoints.
WebSocket Heartbeat connection
ping_interval
60
The LBank WebSocket server sends periodic ping messages. Clients must respond with a matching pong within 60 seconds. Failure to respond causes the server to close the connection. Clients may also initiate pings to verify connection health.

Policies

Rolling window enforcement
Rate limits are enforced against a rolling 10-second window, not a fixed-second boundary. Clients should implement request pacing and backoff logic to avoid triggering error 10004.
Error 10004 handling
When the rate limit is exceeded, the API returns error code 10004 ("Request too frequent"). Clients should implement exponential backoff and reduce request frequency before retrying.
WebSocket reconnect
Clients must implement automatic WebSocket reconnection logic and re-subscribe to all channels after reconnection since subscription state is not persisted across connections.
Multiple base URLs for redundancy
LBank provides three interchangeable REST base URLs (https://api.lbkex.com/, https://www.lbkex.net/, https://api.lbank.info/) to allow failover and redundancy. Rate limits apply per API key regardless of which base URL is used.

Sources