MEXC API
Spot v3 + Contract v1 · widest small-cap listing · public endpoints open to server IPs
Create a key safely
- Profile → API Management → Create API key.
- Tick the permission groups explicitly — MEXC keys start with nothing enabled; grant read groups first.
- Bind your server IP; unbound keys are short-lived by policy.
- Sign requests with HMAC-SHA256 over the query string, key in the X-MEXC-APIKEY header.
- Store the secret at creation — it is shown once.
Permissions: what to grant
- Account: Read — balances and history; enough for portfolio views. Without this group even a valid signature gets error 700007.
- Trade scope: only if you run strategies live; spot and futures are separate permission groups.
- Withdrawal scope: never. We refuse keys that have it enabled.
Worth knowing before you code
- Spot v3 (api.mexc.com) and Contract v1 (contract.mexc.com) are separate APIs with separate base URLs.
- Public market data needs no key and answers datacenter IPs directly — unlike the exchange's web pages.
- Known for listing small caps earliest of the four — verify pair liquidity via the order-book endpoint before sizing.
Never grant withdrawal permission to anyone. Not to us, not to any service. Our connect flow refuses keys that have it. A trading key can lose a trade; a withdrawal key can lose the account.
Connect this key to our engine → Official API docs Create a MEXC account
Other guides: Gate.io API · OKX API · Bybit API · Compare their fees