RCXT
Probit

Probit

Probit API Information

Probit Api Link: https://docs-en.probit.com/reference/balance

HTTP API

  • Entry point: https://api.probit.com/api/exchange/v1/
  • All requests must use Content-Type: application/json.

Authorization is required for endpoints that need it. Refer to the HTTP API Reference for detailed endpoint info.

Error Codes

code data HTTP Status
DUPLICATE_ACCOUNT Accounts already exists. 400
DUPLICATE_ADDRESS Address already exists in withdrawal address list. 400
INVALID_ARGUMENT Invalid format, empty params, out of range, or unexpected param. 400
INVALID_CURRENCY Currency does not exist. 400
INVALID_MARKET Market does not exist. 400
INVALID_ORDER Order does not exist or not your order. 400
NOT_ALLOWED_COMBINATION Parameter combination not allowed (e.g., market sell + gtcpo). 400
NOT_ENOUGH_BALANCE not enough ;) 400
NOT_FOUND_DEPOSIT_ADDRESS Platform network not found. 400
MARKET_CLOSED Market is closed today ;) 400
MARKET_NOT_FOUND 400
UNAUTHORIZED Login required. 401
FORBIDDEN No permission. 403
TOO_MANY_OPEN_ORDERS Too many open orders. 403
UNKNOWN_USER_BLOCKED Account is blocked :( 403
withdrawal_not_found 404
PAYLOAD_TOO_LARGE Payload too big. 413
RESOURCE_LOCKED Resource is locked. 423
RATE_LIMIT_EXCEEDED Too many requests. Try later. 429
MARKET_UNAVAILABLE Market is closed today ;) 503
TRADING_UNAVAILABLE Server overloaded. 503
UNAVAILABLE 18, 15, 19 503

Rate Limits

Ratelimit Group 1

Applied to: ProBit Global account Rate: 10 req/sec, burst 10 Affected APIs:

  • Place new orders
  • Withdrawals
  • Transfer to ProBit Global
  • Staking / Unstaking

Ratelimit Group 2

Applied to: ProBit Global account Rate: 20 req/sec, burst 100 Affected APIs:

  • Cancelling orders

Ratelimit Group 3

Applied to: IP address Rate: 20 req/sec, burst 200 Affected APIs:

  • All APIs

Ratelimit Group 4

Applied to: Special Account Rate: 5 req/sec, burst 100 Affected APIs:

  • Placing new orders

RCXT Probit API Information

There is 1 Base Endpoint for the Probit exchange:

  • apiUrl: api.probit.com/api/exchange/v1
  • authUrl: accounts.probit.com

Rate Limits

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

Limit (1 minute) Spot TransferIn TransferOut Ticker
Fetch Balances 1 Request Weight
Fetch Orders 1 Request Weight
Fetch Trades 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.probit.com/api/exchange/v1).
  • The Endpoint used is /balance.
  • The RCXT Endpoint is api/v1/probit/balances.

The user sends a GET request to query the BingX 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.

Response Example:

{
  "spot": [
    {
      "coin": "SHIB", #asset
      "total": "41634.28"
    }
  ],
  "margin": null,
  "isolatedMargin": null,
  "futures": null,
  "earnings": null
}

Fetch Trades

Spot Trades
  • The Base Endpoint is apiUrl (api.probit.com/api/exchange/v1).
  • The Endpoint used is /trade_history.
  • The RCXT Endpoint is api/v1/probit/trades.

The user sends a GET request to query the BingX 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.
    • endTime: The date until which we want to fetch data.
    • symbol: The symbol of the pair used in the trade (e.g., BTCUSDT).
    • limit: Determines the maximum number of assets to be returned.
    • type: The type is set to spot for Spot Trades.

  • Limiter:

    • Each API endpoint is assigned a specific Request Weight value. The Request Weight value for Spot 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.probit.com/api/exchange/v1).

  • The Endpoint used is /order_history.

  • The RCXT Endpoint is api/v1/probit/orders. The user sends a GET request to query Probit 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).
    • limit: Determines the maximum number of assets to be returned.
    • type: Options include spot, cfutures, 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.probit.com/api/exchange/v1).
  • The Endpoint used is /open_order.
  • The RCXT Endpoint is api/v1/probit/orders.

The user sends a GET request to query Probit 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).
    • limit: Determines the maximum number of assets to be returned.
    • type: Options include spot, cfutures, 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.

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.probit.com/api/exchange/v1).
  • The Endpoint used is /transfer/payment.
  • The RCXT Endpoint is api/v1/probit/deposit-withdraw-history.

The user sends a GET request to query Probit 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:

    • startTime: The date from which we want to fetch data.
    • endTime: The date until which we want to fetch data.
    • limit: Determines the maximum number of assets to be returned.
    • 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.
    • A maximum of 1000 entries can be fetched per page.
Transfer Out
  • The Base Endpoint is apiUrl (api.probit.com/api/exchange/v1).
  • The Endpoint used is /transfer/payment.
  • The RCXT Endpoint is api/v1/probit/deposit-withdraw-history.

The user sends a GET request to query Probit 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:

    • startTime: The date from which we want to fetch data.
    • endTime: The date until which we want to fetch data.
    • limit: Determines the maximum number of assets to be returned.
    • type: Options include transferIn and transferOut. transferIn 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.
    • A maximum of 1000 entries can be fetched per page.

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.probit.com/api/exchange/v1).

  • The Endpoint used is /ticker.

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

  • https://api.probit.com/api/exchange/v1/ticker: 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
}
PionexRobinHood