Bitexen

RCXT

Bitexen

Bitexen API Information

Bitexen API Link: https://docs.bitexen.com/#introduction

Main Endpoints

Base Endpoint: https://www.bitexen.com

Generating an API Key

For private API calls you need to sign your request with parameters below:

API Key (Will be generated by Bitexen upon creating API key)
Secret Key (Will be generated by Bitexen upon creating API key)
Passphrase (Will be provided by you upon creating API key)

Creating a Request

All private API calls must contain the following headers:

ACCESS-USER → Username as a string.
ACCESS-PASSPHRASE → The passphrase you specified when creating the API key.
ACCESS-TIMESTAMP → A timestamp for your request.
ACCESS-SIGN → The base64-encoded signature (see Signing a Message).
ACCESS-KEY → The api key as a string.

Content-Type should be set as application/json

Signing a Message

The ACCESS-SIGN header should be generated by using HMAC-SHA256 of api_key + username + pass_phrase + timestamp + body (where + represents string concatenation)

The timestamp value should be the same in the ACCESS-TIMESTAMP header.
The body is the request body string as JSON or “{}” if there is no request body.

LIMITS

Do not make more than 60 requests per 1 minute or you will get a rate limit error(HTTP 429). We expect you won’t encounter rate limits in normal usage.

: Too Many Requests(429) – The user has sent too many requests in a given amount of time (“rate limiting”).

HTTP Return Code

Bitexen Api Link: https://docs.bitexen.com/#response

400 Bad Request – This response means that server could not understand the request due to invalid syntax
401 Unauthorized – Authentication is needed to get requested response. This is similar to 403, but in this case, authentication is possible.
403 Forbidden – Client does not have access rights to the content so server is refusing to give proper response.
404 Not Found – Server cannot find the requested resource.
405 Method Not Allowed – The request method is known by the server but has been disabled and cannot be used. Double check your method type (i.e. GET, POST, PUT, DELETE)
429 Too Many Requests – The user has sent too many requests in a given amount of time (“rate limiting”).
500 Internal Server Error – The server has encountered a situation it doesn’t know how to handle.
503 Service Unavailable – The server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded.

RCXT Bitexen API Information

There is 1 Base Endpoint for the Bitexen Exchange:

apiUrl: www.bitexen.com

Rate Limits

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

Limit (1 minute)	Spot	FiatBuyFiatSell	Ticker
Fetch Balances	60 Request Weight
Fetch Orders	60 Request Weight
Fetch Trades	60 Request Weight
Fetch DepositWithdrawals		60 Request Weight
Ticker			60 Request Weight

Fetch Balances

Spot Balance

The Base Endpoint is apiUrl (www.bitexen.com).
The Endpoint used is /api/v1/balance/.
The RCXT Endpoint is api/v1/bitexen/balances.

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

The apiKey, secretKey, password, and username values are obtained from the header.
Limiter:
- Each API endpoint is assigned a specific Request Weight value. The Request Weight value for Spot Balance is 60.

Response Example:

{
  "spot": [
    {
      "coin": "LTC", #currency_code
      "total": "0.04015223" #balance
    }
  ],
  "margin": null,
  "isolatedMargin": null,
  "futures": null,
  "earnings": null
}

Fetch Trades

Spot Trades

The Base Endpoint is apiUrl(www.bitexen.com).
The Endpoint used is /api/v1/orders/Main/C/ + pageNumber + /.
The RCXT Endpoint is api/v1/bitexen/trades.

The request includes the following values from the header:

apiKey, secretKey, and password.

Query parameters include:

username: Bitexen username (email address).
pairSymbol: Specifies the symbol pair for the trade (e.g. BTCUSDT).
pageNumber: Used for pagination, specifies the page number to be fetched.
Limiter:
- Each API endpoint is assigned a specific Request Weight value. The Request Weight value for Spot Trades is 60.

If our side is “buy,” the commission currency (counter_currency) in a pair like BTCTRY is TRY. If the side is “sell,” the commission currency (base_currency) is BTC. Response Example:

{
 "trades": [
   {
     "orderId": "19312553710", #order_number
     "tradeId": "19312553710", #order_number
     "isBuyer": true, #buy_sell
     "isMaker": false, #buy_sell
     "price": "4274.57", #price
     "quantity": "0.04027305", #volume_executed
     "symbol": "LTCTRY", #market_code
     "time": 1737380406277, #add_date
     "commission": "0.000120816", #fee_amount
     "commissionCurrency": "LTC" #base_currency , counter_currency
   }
 ],
 "cursor": ""
}

Fetch Orders

Spot Orders

The Base Endpoint is apiUrl(www.bitexen.com).
The Endpoint used is /api/v1/orders/Main/O/ + pageNumber + /.
The RCXT Endpoint is api/v1/bitexen/orders.

The request includes the following values from the header:

apiKey, secretKey, and password.

Query parameters include:

username: Bitexen username (email address).
pairSymbol: Specifies the symbol pair for the trade (e.g. BTCUSDT).
singleOrderId: Used to filter by a specific order OrderID.
pageNumber: Used for pagination, specifies the page number to be fetched.
orderStatus: If orderStatus is “open”, fetches Open Orders, if “closed”, fetches Closed Orders.
Limiter:
- Each API endpoint is assigned a specific Request Weight value. The Request Weight value for Spot Orders is 60.

Spot Open Orders

The Base Endpoint is apiUrl(www.bitexen.com).
The Endpoint used is /api/v1/orders/Main/C/ + pageNumber + /.
The RCXT Endpoint is api/v1/bitexen/orders.

The request includes the following values from the header:

apiKey, secretKey, and password.

Query parameters include:

username: Bitexen username (email address).
pairSymbol: Specifies the symbol pair for the trade (e.g. BTCUSDT).
singleOrderId: Used to filter by a specific order OrderID.
pageNumber: Used for pagination, specifies the page number to be fetched.
orderStatus: If orderStatus is “open”, fetches Open Orders, if “closed”, fetches Closed Orders.
Limiter:
- Each API endpoint is assigned a specific Request Weight value. The Request Weight value for Spot Open Orders is 60.

Response Example:

{
  "orders": [
    {
      "orderId": "19312553710", #order_number
      "symbol": "LTCTRY", #market_code
      "type": "market", #order_type
      "price": "4274.57", #price
      "side": "BUY", #buy_sell
      "time": 1737380406277, #add_date
      "status": "CLOSED", #status
      "executedQuantity": "0.04027305", #volume_executed
      "quantity": "0.04027305" #volume
    }
  ],
  "cursor": ""
}

Fetch DepositWithdrawals

FiatBuy FiatSell

The Base Endpoint is apiUrl(www.bitexen.com).
The Endpoint used is /api/v1/orders/Main/C/ + pageNumber + /.
The RCXT Endpoint is api/v1/bitexen/deposit-withdraw-history.

The request includes the following values from the header:

apiKey, secretKey, and password.

Query parameters include:

username: Bitexen username (email address).
pairSymbol: Specifies the symbol pair for the trade (e.g. BTCUSDT).
pageNumber: Used for pagination, specifies the page number to be fetched.
transactionType: The available values are fiatBuy and fiatSell. Choose fiatBuy for Fiat Buy and fiatSell for Fiat Sell.
Limiter:
- Each API endpoint is assigned a specific Request Weight value. The Request Weight value for FiatBuyFiatSell is 60.

Response Example:

{
  "depositWithdrawals": [
    {
      "fiatCurrency": "TRY", #counter_currency
      "cryptoCurrency": "LTC", #base_currency
      "fiatAmount": "172.14", #total
      "cryptoAmount": "0.04027305", #volume_executed
      "price": "4274.57", # price
      "address": "",
      "orderId": "",
      "transactionId": "19312553710",
      "fee": "0.000120816", #fee_amount
      "network": "", #
      "status": "Completed",
      "time": 1737380406277 #add_date
    }
  ],
  "cursor": ""
}

Ticker

Ticker

The Base Endpoint is apiUrl(www.bitexen.com).
The Endpoint used is /api/v1/ticker/ + symbol + /.
The RCXT Endpoint is api/v1/bitexen/ticker.

The request includes the following query parameter:

symbol: Specifies the symbol of the cryptocurrency pair (e.g. BTCUSDT).

Response Example:

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

BingX Bitfinex