Changelogs

Release Summary

---

Changelog - v1.0.9

Release Date: June 26, 2026

Breaking Changes: No

Deprecations: No

Public, read-only market-data surface — independent of the authenticated trading API and of margin currency. No API key or authentication header is required.

Added

1. Historical klines (REST)

• Endpoint: GET /fapi/v1/price/kline
• Returns up to 1440 candles per asset; each candle is a 6-element array [open_time, open, high, low, close, volume]. Invalid/empty symbols are omitted.

2. Historical mark-price klines (REST)

• Endpoint: GET /fapi/v1/price/mark-kline
• Same shape as klines but OHLC only — each candle is a 5-element array.

3. Live streaming (WebSocket)

• Endpoint: wss://trade.mudrex.com/fapi/v1/price/ws/linear
• Streams: kline@1s / kline@1m, markKline@1s / markKline@1m, and ticker@1s / ticker@5s.
• Methods: SUBSCRIBE, UNSUBSCRIBE, LIST_SUBSCRIPTIONS. Keepalive: server closes after 40s idle; recommended PING every 20s. Subscriptions are per-connection and not persisted.

---

Changelog - v1.0.8

Release Date: June 16, 2026

Breaking Changes: No

Deprecations: No

Backward compatibility. Existing USDT-only requests behave exactly as before. When trade_currency is omitted, requests return USDT data. Responses gain only additive fields; no field is renamed or removed. No client migration is required.

Added

1. Currency parameter

• Add trade_currency (USDT | INR) to operate in a given currency.
  • Query parameter on GET; body field on POST / PATCH / DELETE.
  • Omitted defaults to USDT.
  • Unsupported values return 400 Invalid trade currency.
• The spot balance read (GET /wallet/funds) uses the currency query parameter (USDT | INR).

2. INR wallet reads

• GET /wallet/funds?currency=INR — INR spot wallet balance.
• GET /futures/funds?trade_currency=INR — INR futures wallet balance (balance, locked_amount, first_time_user).

3. INR transfers

• Endpoint: POST /futures/transfers/inr
• Body: amount, from_wallet_type, to_wallet_type (SPOT / FUTURES).
• Response: 202 Accepted with { "id": "<transaction_id>" }.
• The USDT transfer path POST /wallet/futures/transfer does not accept INR.

4. Futures transactions

• GET /futures/transactions?trade_currency=INR with type (DEPOSIT / WITHDRAW), status, sort_by, sort_order, limit filters.

5. Per-(asset, currency) leverage

• GET / POST /futures/{asset_id}/leverage accept trade_currency; INR and USDT leverage are independent.
• Response includes margin_type, leverage, collateral_currency_id.
• Leverage never set for an (asset, currency) returns 404 leverage not found.

6. INR-margin order & position lifecycle

• Order create/amend/cancel, open orders, order history, order-by-id.
• Open positions, position history, liquidation price, add/reduce margin, set/edit SL/TP, partial close, reverse, square off.
• Fee history.
• All accept and/or return INR per the currency parameter.

7. Additive response fields

• trade_currency tag on orders, positions, and fee records.
• FX rate: hedge_rate (orders); entry_hedge_rate / exit_hedge_rate (positions / history).
• gst_amount on INR fee records.
• collateral_currency_id on leverage responses.

Changed

• Currency-scoped list endpoints — GET /futures/orders, /futures/orders/history, /futures/positions, /futures/positions/history, /futures/fee/history, /futures/transactions return one currency per call, default to USDT, never mix currencies, and tag each item with trade_currency.

Migration Notes

• No changes required. Omitting trade_currency preserves existing USDT behaviour.

---

Changelog - v1.0.7

Release Date: June 2, 2026

Breaking Changes: No

Deprecations: No

Changed

Fee History API Response Enhancement

Enhanced Fee History API response with additional fee-level metadata, including order details and GST information.

• Endpoint: GET /fapi/v1/futures/fee/history
• Added Fields:
  • id – Unique identifier for a fee
  • order_type – Type of order (LONG, SHORT, STOPLOSS, TAKEPROFIT)
  • trigger_type – Trigger type of the order (MARKET, LIMIT)
  • gst_amount – GST charged for the order
• Notes: order_type and trigger_type are applicable only when fee_type is TRANSACTION or REBATE.

Migration Notes

• No changes required. Existing integrations continue to work without modification.

---

Changelog - v1.0.6

Release Date: May 12, 2026

Breaking Changes: No · Deprecations: No

Changed

1. Default API Rate Limits Updated

Enhanced default API rate limits across all endpoints to support higher throughput and trading activity.

2. Wallet Endpoint Rate Limits

Wallet endpoints (POST /fapi/v1/wallet/funds, POST /fapi/v1/wallet/futures/transfer) continue to use separate rate limits.

Migration Notes

• No changes required. Existing integrations continue to work without modification.

---

Changelog - v1.0.5

Release Date: April 21, 2026

Breaking Changes: No · Deprecations: No

Added

• Mudrex Python SDK initial release; TradeClient for Futures API interaction; API secret–based authentication (direct + environment variable support).
• Core SDK methods: place order, set leverage, get leverage, fetch positions, cancel order.
• Error handling: MudrexAPIError, MudrexRequestError.

---

Changelog - v1.0.4

Release Date: April 15, 2026

Breaking Changes: No · Deprecations: No

Changed

1. Rate Limits Update for Trading Endpoints

Enhanced rate limits for core trading endpoints to support higher throughput.

• Endpoints: POST /fapi/v1/futures/:asset_id/order, DELETE /fapi/v1/futures/orders/:order_id, POST /fapi/v1/futures/positions/:position_id/add-margin, POST & PATCH /fapi/v1/futures/positions/:position_id/riskorder, POST /fapi/v1/futures/positions/:position_id/reverse, POST /fapi/v1/futures/positions/:position_id/close/partial, POST /fapi/v1/futures/positions/:position_id/close, GET & POST /fapi/v1/futures/:asset_id/leverage.

• Unchanged: all other endpoints continue to use existing limits (Second 2, Minute 50, Hour 1000, Day 10000).

2. Removed PnL data from the response

• Endpoint: GET /fapi/v1/futures/positions
• Removed stale PnL data from the response to avoid inaccurate position reporting.

Migration Notes

• No changes required. Existing integrations continue to work without modification.

---

Changelog - v1.0.3

Release Date: January 22, 2025

Breaking Changes: No · Deprecations: No

Added

• MCP Server Integration Guide.

---

Changelog - v1.0.2

Release Date: December 8, 2025

Breaking Changes: No · Deprecations: No

Changed

• Status code and message for POST /fapi/v1/wallet/futures/transfer: 200 OK → 202 Accepted; message internal_wallet_fund_transfer_request successful → internal wallet fund transfer request accepted.

---

Changelog - v1.0.1

Release Date: December 5, 2025

Breaking Changes: No · Deprecations: No

Added

1. Add / Reduce Margin API — POST /fapi/v1/futures/positions/:positionID/add-margin (margin float; positive adds, negative reduces). Returns updated initial_margin and liquidation_price.
2. Estimated Liquidation Price API — GET /fapi/v1/futures/positions/:positionID/liq-price?ext_margin=2.1 (ext_margin optional hypothetical margin change; if omitted or 0, returns current liquidation price).
3. Symbol-First API Trading Support — ?is_symbol (presence-based) on GET /fapi/v1/futures/:id, GET/POST /fapi/v1/futures/:id/leverage, POST /fapi/v1/futures/:id/order. Asset-ID flows remain functional.

Changed

• Get Assets / Asset Info — removed contract_multiplier, price_scale; fixed min_funding_rate / max_funding_rate.
• Place Order — success status 200 OK → 202 Accepted.
• Order History — removed desired_amount, liquidation_price.
• Open Positions — removed closed_price.
• Position History — removed unrealised_pnl.
• Place / Amend Risk Order — user_id, order_id, exchange_order_id, id now ignored; improved errors (404 invalid position, 400 not OPEN).
• Reverse Position — success status 200 OK → 202 Accepted.

Migration Notes

• Update clients to accept 202 Accepted for order placement and reverse position operations. Stop relying on removed fields. Existing asset-ID-based flows continue to work.

---

Changelog - v1.0.0

Release Date: Nov 5, 2025

Initial API trading support — Wallet (GET /wallet/funds, POST /wallet/futures/transfer), Futures (GET /futures/funds), Assets (GET /futures, GET /futures/:asset_id), Leverage (GET/POST /futures/:asset_id/leverage), Orders (place / list / history / detail / amend / cancel), Positions (list / history / riskorder / close / partial / reverse), Fees (GET /fapi/v1/futures/fee/history).