Authentication & Rate Limits
Learn how to authenticate with Mudrex API using API keys and understand the rate limits enforced for secure trading operations.
Authentication
Mudrex enforces strong security measures. To call any private endpoint, you must:
Verify your identity: Complete KYC verification (PAN & Aadhaar) and enable two-factor authentication for your Mudrex account.
Generate an API key: In your dashboard, create an API key. Copy the secret and store it securely, as it will not be displayed again.
All endpoints under /fapi/v1 require the following headers:
| Header | Value | Required |
|---|---|---|
| X-Authentication | your_api_secret | Yes |
| Content-Type | application/json | Only for POST/PATCH/DELETE requests |
Example Request
curl -X POST https://trade.mudrex.com/fapi/v1/futures/<asset_id>/order \
-H "Content-Type: application/json" \
-H "X-Authentication: <secret-key>" \
-d '{
"leverage": "5",
"quantity": "0.001",
"order_price": "107526",
"order_type": "LONG",
"trigger_type": "MARKET",
"is_takeprofit": true,
"is_stoploss": true,
"stoploss_price": "106900",
"takeprofit_price": "110000",
"reduce_only": false
}'Rate Limits
The following rate limits are enforced per API key.
Updated Rate Limits (All Endpoints)
All endpoints will use the following updated rate limits, except wallet endpoints listed separately below.
Limits
| Duration | Limit |
|---|---|
| Second | 10 |
| Minute | 500 |
| Hour | 30000 |
Wallet Rate Limits (/fapi/v1/wallet)
/fapi/v1/wallet)The following wallet endpoints use separate rate limits from the default API limits:
Limits
| Duration | Limit |
|---|---|
| Second | 2 |
| Minute | 50 |
| Hour | 1000 |
Notes
- Rate limits are applied per API key
- Wallet routes continue to use separate limits
- Exceeding limits may result in request throttling or temporary blocking
- Updated limits are designed to support higher throughput and trading activity