MEXC · Rate Limits

Mexc Rate Limits

MEXC applies a weight-based rate limit model for the Spot REST API and a flat request-count model for the Futures REST API. Spot REST limits are enforced per IP (300 weight per 10 seconds) and per UID (500 weight per 10 seconds). Futures REST endpoints are limited to 20 requests per 2-second window. WebSocket connections are capped at 100 messages per second with a maximum of 30 channel subscriptions per connection. HTTP 429 indicates an exceeded limit; repeated violations escalate to temporary IP bans. Market Maker Program tiers (T1/T2/T3) receive elevated rate limits of 200, 300, and 400 requests per second respectively.

Mexc Rate Limits is the machine-readable rate-limit profile for MEXC on the APIs.io network, in the API Commons Rate Limits shape.

It captures 12 rate-limit definitions, measuring weight_per_10_seconds, requests_per_2_seconds, messages_per_second, concurrent_subscriptions, and hours.

Limit state is signalled in the apiKey and retryAfter response headers, and an exhausted limit returns HTTP 429.

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 7 backoff/retry policies defined and response codes documented for throttled.

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

12 Limits Exhausted: HTTP 429 apiKeyretryAfter
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

Spot REST — IP weight limit IP
weight_per_10_seconds
300
All IP-weighted Spot REST endpoints share 300 weight units per 10-second rolling window. Different endpoints consume varying weight based on resource intensity. Track via response headers.
Spot REST — UID weight limit account
weight_per_10_seconds
500
All UID-weighted Spot REST endpoints share 500 weight units per 10-second rolling window. Authenticated order-related endpoints are typically UID-weighted.
Futures REST — request rate limit IP
requests_per_2_seconds
20
Standard Futures (contract) REST endpoints are limited to 20 requests per 2-second window for both public market data and authenticated account/trading endpoints.
Spot WebSocket — message rate connection
messages_per_second
100
Each WebSocket connection is limited to 100 subscription/unsubscription messages per second. Connections that exceed this limit are disconnected.
Spot WebSocket — channel subscriptions connection
concurrent_subscriptions
30
A single WebSocket connection supports a maximum of 30 channel subscriptions. Create multiple connections to subscribe to more channels.
Spot WebSocket — connection duration connection
hours
24
WebSocket connections are valid for a maximum of 24 hours. Clients must re-establish connections after expiry.
API keys per account account
count
30
Each MEXC account may create up to 30 API keys. Each key supports up to 10 IP address restrictions.
Open orders per account account
count
500
Maximum of 500 active open orders per account at any time.
Sub-accounts per master account account
count
30
Each master account may create up to 30 sub-accounts.
Market Maker T1 — API rate limit account
requests_per_second
200
Market Maker Program T1 tier accounts receive an enhanced limit of 200 requests per second.
Market Maker T2 — API rate limit account
requests_per_second
300
Market Maker Program T2 tier accounts receive an enhanced limit of 300 requests per second.
Market Maker T3 — API rate limit account
requests_per_second
400
Market Maker Program T3 tier accounts receive the highest enhanced limit of 400 requests per second. All Market Maker tiers also include an account-level capacity of 50 requests per second.

Policies

Weight model (Spot REST)
Each Spot REST endpoint declares a weight value. IP-based limits aggregate to 300 weight per 10 seconds; UID-based limits aggregate to 500 weight per 10 seconds. Clients should track consumed weight and throttle proactively.
Backoff on 429
An HTTP 429 response is returned when rate limits are exceeded. The Retry-After header specifies the number of seconds to wait before retrying. Continuing to send requests during the backoff window is treated as abuse.
IP ban escalation
Repeatedly exceeding rate limits or failing to respect 429 responses results in temporary IP bans. Ban durations scale from 2 minutes up to 3 days for repeat offenders.
WebSocket keepalive
If no valid subscription exists on a WebSocket connection, the server disconnects after 30 seconds. If subscriptions are active but no data flows, disconnection occurs after 1 minute. Clients should send periodic ping frames to maintain the connection.
No sandbox environment
MEXC does not provide a sandbox or test environment. All API calls connect directly to the live production exchange.
recvWindow parameter
Signed Spot REST requests may include a recvWindow parameter (default 5,000 ms, maximum 60,000 ms) to control the validity window for timestamp-based replay protection.
Futures timestamp window
Futures REST authenticated requests must carry a Request-Time timestamp within 10 seconds of server time (adjustable up to 60 seconds via the recv-window header).

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/mexc-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.