Changelogs

Release Summary

---

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 5, 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.

• Updated Rate Limits:

2. Wallet Endpoint Rate Limits

Wallet endpoints continue to use separate rate limits from the default API limits.

• Endpoints:

  • POST /fapi/v1/wallet/funds
  • POST /fapi/v1/wallet/futures/transfer

• Wallet 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 /fapi/v1/futures/positions/:position_id/riskorder
  • 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 /fapi/v1/futures/:asset_id/leverage
  • POST /fapi/v1/futures/:asset_id/leverage

• Updated Rate Limits:

  Duration	Limit
  Second	5
  Minute	125
  Hour	2500
  Day	25000

• Unchanged:

  All other endpoints continue to use existing rate limits.

  Duration	Limit
  Second	2
  Minute	50
  Hour	1000
  Day	10000

Migration Notes

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

2. Removed PnL data from the response.

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

---

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 funds transfer endpoint

• Endpoint:POST /fapi/v1/wallet/futures/transfer
• Changed status code and message for successful fund movement 200 OK → 202 Accepted 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

• Endpoint: POST /fapi/v1/futures/positions/:positionID/add-margin
• Request Body:
  JSON

  {
    "margin": 10.2
  }

  • margin (float): Positive value adds margin, negative value reduces margin
• Response: Returns updated initial_margin and liquidation_price

2. Estimated Liquidation Price API

• Endpoint: GET /fapi/v1/futures/positions/:positionID/liq-price?ext_margin=2.1
• Query Parameters:
  • ext_margin (float, optional): Hypothetical margin change
    • Positive value simulates adding margin
    • Negative value simulates reducing margin
    • If not provided or 0, returns current liquidation price
• Response: Returns estimated liquidation price as string

3. Symbol-First API Trading Support

The following endpoints now support trading by asset symbol instead of asset ID:

• GET /fapi/v1/futures/:id
• GET /fapi/v1/futures/:id/leverage
• POST /fapi/v1/futures/:id/leverage
• POST /fapi/v1/futures/:id/order

Usage: Add query parameter ?is_symbol (presence-based, value is ignored)
Note: Asset-ID-based flows remain fully functional for backward compatibility

If the query param is passed, even if the value is false, F, f, False, 0 etc. the system will treat as a symbol-first trading. Please use the flag only when trading via symbols.

Changed

1. Get Assets (Listing) & Get Asset Info

• Endpoints:
  • GET /fapi/v1/futures?limit=10&offset=0
  • GET /fapi/v1/futures/:asset_id
• Removed Fields:
  • contract_multiplier
  • price_scale
• Fixed Fields:
  • min_funding_rate and max_funding_rate now return correct minimum and maximum funding rates

2. Place Order

• Endpoint: POST /fapi/v1/futures/:asset_id/order
• Change: Success status code updated from 200 OK to 202 Accepted

3. Get Orders History

• Endpoint: GET /fapi/v1/futures/orders/history
• Removed Fields:
  • desired_amount
  • liquidation_price

4. Get Open Positions

• Endpoint: GET /fapi/v1/futures/positions
• Removed Field: closed_price

5. Get Closed Positions (Position History)

• Endpoint: GET /fapi/v1/futures/positions/history
• Removed Field: unrealised_pnl

6. Place / Amend Risk Order

• Endpoints:
  • POST /fapi/v1/futures/positions/:position_id/riskorder
  • PATCH /fapi/v1/futures/positions/:position_id/riskorder
• Request Body Changes: The following fields are now ignored if sent:
  • user_id
  • order_id
  • exchange_order_id
  • id
• Error Handling Improvements:
  • 404 Not Found when position_id is invalid or position doesn't exist
  • 400 Bad Request when position is not in OPEN state
  • More descriptive error messages for invalid requests

7. Reverse Position

• Endpoint: POST /fapi/v1/futures/positions/:position_id/reverse
• Change: Success status code updated from 200 OK to 202 Accepted

Fixed

• General improvements to validation and error messaging for invalid requests

Migration Notes

• Status Codes: Update clients to accept 202 Accepted for order placement and reverse position operations
• Removed Fields: Stop relying on fields that have been removed from responses
• Backward Compatibility: Existing asset-ID-based flows continue to work without changes

---

Changelog — v1.0.0

Wallet

• GET /wallet/funds: Fetch spot wallet balances.
• POST /wallet/futures/transfer: Transfer funds between spot and futures wallets.

Futures

• GET /futures/funds: Fetch futures wallet balances and available transfer amount.

Assets

• GET /futures: List all futures assets (supports sorting and pagination).
• GET /futures/:asset_id: Retrieve detailed information for a specific asset.

Leverage

• GET /futures/:asset_id/leverage: Get current leverage and margin type for an asset.
• POST /futures/:asset_id/leverage: Set leverage and margin type for an asset.

Orders

• POST /fapi/v1/futures/:asset_id/order: Place new orders (market or limit).
• Order Management: Endpoints to list open orders, retrieve order history, fetch individual order details, amend orders, and cancel orders.

Positions

• GET /fapi/v1/futures/positions: List open positions.
• Position Management: Endpoints to view position history, place or amend risk orders, close positions (full or partial), and reverse positions.

Fees

• GET /fapi/v1/futures/fee/history: Retrieve trading fee history with limit and offset parameters.