RCXT
CoinW

CoinW

CoinW API Information

CoinW Api Link: https://www.coinw.com/api-doc/en/common/introduction

Main Endpoints

  • Base Endpoint: api.coinw.com

HTTP Response Codes and Error Handling

Interfaces indicating a successful operation usually return the following response:

  • {'code': 0, 'msg': ''}

Error code returned in case of rate limit exceeding and frequent access:

  • 29001: API access too frequent (Rate limit exceeded).
    • Message Example: {"code": 29001, "msg": "API access frequently"}

Rate Limits

Limits on CoinW are applied based on both IP Address and User ID (UID).

Global Rate Limits

Operation Type Limit Type Limit (Per Second) Note
Futures Trading Market Data (IP) 30 requests/sec Applicable for market data endpoints.
Futures Trading Other Endpoints (UID) 100 requests/sec Applicable for account and order operations.
Spot Trading IP Address 100 requests/sec Across all spot endpoints.
Spot Trading User ID (UID) 300 requests/sec Across all spot endpoints.

Excessive Access Policy (If Normal Usage Limit is Exceeded)

CoinW applies a tiered restriction when the 10-second error count threshold is exceeded:

  1. Warning Phase (5 Minutes):

    • Rate limits are reduced by 50%.
    • If errors continue during this phase, temporary ban begins.

  2. Temporary Ban (30 Seconds):

    • All API access is blocked for 30 seconds.

  3. Blacklist:

    • If the ban threshold is frequently exceeded within an 8-hour period (e.g., 10 times per UID), access is blocked for 8 hours.

RCXT CoinW API Information

There is 1 Base Endpoint for the CoinW exchange:

  • apiUrl: api.coinw.com

Rate Limits

The rate limit set for each endpoint on the CoinW exchange is as follows:

Limit (1 minute) Spot Usd Futures TransferIn TransferOut Ticker
Fetch Balances 1 Request Weight 1 Request Weight
Fetch Orders 1 Request Weight 1 Request Weight
Fetch Trades 1 Request Weight 1 Request Weight
Fetch DepositWithdrawals 1 Request Weight 1 Request Weight
Ticker 1 Request Weight

Fetch Balances

Spot Balance
  • The Base Endpoint is apiUrl (api.coinw.com).
  • The Endpoint used is /api/v1/private?command=returnCompleteBalances.
  • The RCXT Endpoint is api/v1/coinw/balances.

The user sends a GET request to query the CoinW wallet balances. This request must include the required header parameters:

  • The apiKey and secretKey values are taken from the header.

  • Limiter:

    • Each API endpoint is assigned a specific Request Weight value. The Request Weight value for Spot Balance is 1.
Usd Futures Balance
  • The Base Endpoint is apiUrl (api.coinw.com).
  • The Endpoint used is /v1/perpum/account/getUserAssets.
  • The RCXT Endpoint is api/v1/coinw/balances.

The user sends a GET request to query the CoinW wallet balances. This request must include the required header parameters:

  • The apiKey and secretKey values are taken from the header.

  • Limiter:

    • Each API endpoint is assigned a specific Request Weight value. The Request Weight value for Usd Futures Balance is 1.

Response Example:

{
  "spot": [
    {
      "coin": "BTTC", #asset
      "total": "208850.4"
    }
  ],
  "margin": null,
  "isolatedMargin": null,
  "futures": [
    {
      "coin": "USDT", # asset
      "total": "0.03733590"
    },
    {
      "coin": "DOGE", #asset
      "total": "2000.00000000"
    }
  ],
  "earnings": null
}

Fetch Trades

Spot Trades
  • The Base Endpoint is apiUrl (api.coinw.com).
  • The Endpoint used is /api/v1/private?command=getUserTrades.
  • The RCXT Endpoint is api/v1/coinw/trades.

The user sends a GET request to query the CoinW Spot trades. This request must include the required header parameters:

  • The apiKey and secretKey values are taken from the header.

  • The following query parameters are required:

    • startTime: The date from which we want to fetch data.
    • symbol: The symbol of the pair used in the trade (e.g., BTCUSDT).
    • orderId: Filters by the specified Order ID.
    • cursor: Used for pagination, specifies which page to fetch.
    • type: Options include spot, ufutures. spot should be selected for Spot Trades.

  • Limiter:

    • Each API endpoint is assigned a specific Request Weight value. The Request Weight value for Spot Trades is 1.
Usd Futures Trades
  • The Base Endpoint is apiUrl (api.coinw.com).
  • The Endpoint used is /v1/perpum/orders/archive.
  • The RCXT Endpoint is api/v1/coinw/trades.

The user sends a GET request to query the CoinW Usd Futures trades. This request must include the required header parameters:

  • The apiKey and secretKey values are taken from the header.

  • The following query parameters are required:

    • startTime: The date from which we want to fetch data.
    • symbol: The symbol of the pair used in the trade (e.g., BTCUSDT).
    • orderId: Filters by the specified Order ID.
    • cursor: Used for pagination, specifies which page to fetch.
    • type: Options include spot, ufutures. spot should be selected for Usd Futures Trades.

  • Limiter:

    • Each API endpoint is assigned a specific Request Weight value. The Request Weight value for Usd Futures Trades is 1.

Response Example:

{
  "trades": [
    {
      "orderId": "226664511", #orderId
      "tradeId": "27082209",
      "isBuyer": false,
      "isMaker": false,
      "price": "0.07610000", #price
      "quantity": "199.90000000", #origQty
      "symbol": "ACAUSDT", #symbol
      "time": 1737552748284, #time
      "commission": "0.01521239", #fee
      "commissionCurrency": "USDT" #side
    }
  ],
  "cursor": ""
}

Fetch Orders

Spot Orders
  • The Base Endpoint is apiUrl (api.coinw.com).
  • The Endpoint used is /api/v1/private?command=getUserTrades.
  • The RCXT Endpoint is api/v1/coinw/orders.

The user sends a POST request to query CoinW Spot orders. This request must include the required header parameters:

  • The apiKey and secretKey values are taken from the header.

  • The following query parameters are required:

    • startTime: The date from which we want to fetch data.
    • endTime: The date until which we want to fetch data.
    • symbol: The symbol of the pair used in the order (e.g., BTCUSDT).
    • page: Used for pagination, specifies the page to retrieve.
    • type: Options include spot, ufutures. spot should be selected for Spot Orders.
    • orderStatus: If orderStatus is “open”, it fetches Open Orders; if “closed”, it fetches Closed Orders.

  • Limiter:

    • Each API endpoint is assigned a specific Request Weight value. The Request Weight value for Spot Orders is 1.
Spot Open Orders
  • The Base Endpoint is apiUrl (api.coinw.com).
  • The Endpoint used is /api/v1/private?command=returnOpenOrders.
  • The RCXT Endpoint is api/v1/coinw/orders.

The user sends a POST request to query CoinW Spot Open orders. This request must include the required header parameters:

  • The apiKey and secretKey values are taken from the header.

  • The following query parameters are required:

    • startTime: The date from which we want to fetch data.
    • endTime: The date until which we want to fetch data.
    • symbol: The symbol of the pair used in the order (e.g., BTCUSDT).
    • page: Used for pagination, specifies the page to retrieve.
    • type: Options include spot, ufutures. spot should be selected for Spot Open Orders.
    • orderStatus: If orderStatus is “open”, it fetches Open Orders; if “closed”, it fetches Closed Orders.

  • Limiter:

    • Each API endpoint is assigned a specific Request Weight value. The Request Weight value for Spot Open Orders is 1.
Usd Futures Orders
  • The Base Endpoint is apiUrl (api.coinw.com).
  • The Endpoint used is /v1/perpum/orders/archive.
  • The RCXT Endpoint is api/v1/coinw/orders.

The user sends a GET request to query CoinW Usd Futures orders. This request must include the required header parameters:

  • The apiKey and secretKey values are taken from the header.

  • The following query parameters are required:

    • startTime: The date from which we want to fetch data.
    • endTime: The date until which we want to fetch data.
    • symbol: The symbol of the pair used in the order (e.g., BTCUSDT).
    • page: Used for pagination, specifies the page to retrieve.
    • type: Options include spot, uFutures. uFutures should be selected for Usd Futures Orders.
    • orderStatus: If orderStatus is “open”, it fetches Open Orders; if “closed”, it fetches Closed Orders.

  • Limiter:

    • Each API endpoint is assigned a specific Request Weight value. The Request Weight value for Usd Futures Orders is 1.
Usd Futures Open Orders
  • The Base Endpoint is apiUrl (api.coinw.com).
  • The Endpoint used is /v1/perpum/orders/open.
  • The RCXT Endpoint is api/v1/coinw/orders.

The user sends a GET request to query CoinW Usd Futures Open orders. This request must include the required header parameters:

  • The apiKey and secretKey values are taken from the header.

  • The following query parameters are required:

    • startTime: The date from which we want to fetch data.
    • endTime: The date until which we want to fetch data.
    • symbol: The symbol of the pair used in the order (e.g., BTCUSDT).
    • page: Used for pagination, specifies the page to retrieve.
    • type: Options include spot, uFutures. uFutures should be selected for Usd Futures Open Orders.
    • orderStatus: If orderStatus is “open”, it fetches Open Orders; if “closed”, it fetches Closed Orders.

  • Limiter:

    • Each API endpoint is assigned a specific Request Weight value. The Request Weight value for Usd Futures Open Orders is 1.

Response Example:

{
  "orders": [
    {
      "orderId": "1881364520706670592", #orderId
      "symbol": "XRPUSDT", #symbol
      "type": "MARKET", #type
      "price": "3.335", #price
      "side": "SELL", #side
      "time": 1737387230537, #time
      "status": "CLOSED", #status
      "executedQuantity": "2.7", #executedQty
      "quantity": "2.7" #origiQty
    }
  ],
  "cursor": ""
}

Fetch DepositWithdrawals

Transfer In
  • The Base Endpoint is apiUrl (api.coinw.com).
  • The Endpoint used is /api/v1/private?command=returnDepositsWithdrawals.
  • The RCXT Endpoint is api/v1/coinw/deposit-withdraw-history.

The user sends a POST request to query CoinW transfer-in data. This request must include the required header parameters:

  • The apiKey and secretKey values are taken from the header.

  • The following query parameters are required:

    • symbol: The symbol of the pair used in the order (e.g., BTCUSDT).
    • type: Options include transferIn and transferOut. transferIn should be selected for Transfer In.

  • Limiter:

    • Each API endpoint is assigned a specific Request Weight value. The Request Weight value for Transfer In is 1.
Transfer Out
  • The Base Endpoint is apiUrl (api.coinw.com).
  • The Endpoint used is /api/v1/private?command=returnDepositsWithdrawals.
  • The RCXT Endpoint is api/v1/coinw/deposit-withdraw-history.

The user sends a POST request to query CoinW transfer-out data. This request must include the required header parameters:

  • The apiKey and secretKey values are taken from the header.

  • The following query parameters are required:

    • symbol: The symbol of the pair used in the order (e.g., BTCUSDT).
    • type: Options include transferIn and transferOut. transferOut should be selected for Transfer Out.

  • Limiter:

    • Each API endpoint is assigned a specific Request Weight value. The Request Weight value for Transfer Out is 1.

Response Example:

{
  "depositWithdrawals": [
    {
      "fiatCurrency": "",
      "cryptoCurrency": "USDT", #coin
      "fiatAmount": "",
      "cryptoAmount": "10", #amount
      "price": "",
      "address": "TNZcfzLhPXVUVe1NLyjdGrjKkPLbHbncJk", #address
      "orderId": "",
      "transactionId": "e4e406a067ff5ce1c05abc6056e6041478153fc03ba996b565f4727b01a708d8", #txId
      "fee": "",
      "network": "TRC20", #network
      "status": "1", #status
      "time": 1726576711847 #insertTime
    }
  ],
  "cursor": ""
}

Fetch Ticker

Ticker

  • The Base Endpoint is apiUrl (api.coinw.com).

  • The Endpoint used is /api/v1/public?command=returnTicker.

  • The RCXT Endpoint is api/v1/coinw/ticker.

  • https://api.coinw.com/api/v1/public?command=returnTicker: Provides the symbol and current price for cryptocurrency pairs traded only with USDT.

  • The only query parameter required is symbol (e.g. BTCUSDT):

    • symbol: Specifies the symbol of the cryptocurrency pair.

Response Example:

{
  "symbol": "BTCUSDT", #symbol
  "price": "104562.53000000" #price
}
CoinTRCryptocom