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, in the API Commons Rate Limits shape.

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

An exhausted limit returns HTTP 10004.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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 Exhausted: HTTP 10004
Method: generated, dated 2026-06-13.
Written by API Evangelist on 2026-06-13 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
CryptocurrencyExchangeTradingMarket DataRate Limiting

Limits

Order Create / Cancel (REST, per API key) account
requests_per_10_seconds · per 10s
500/10s
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 · per 10s
200/10s
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 · per 60s
60/60s
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

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/lbank-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.