Interface description
  • Add trade
Request URL:
Request Method:
  • POST
Parameter Whether or not Type Remarks
apiKey yes string user request for apiKey
timeStamp yes string current timeStamp
nonce yes string random 6 bit character
sign yes string signature of request parameter
type yes string buy type 1 buy 2 sell
price yes float commission price
number yes float quantity entrusted
symbol yes string transaction pair eth_btc、ltc_btc
tradePwd yes string transaction password
How to sign a request parameter

User-submitted parameters are required to sign in addition to sign.

First, the signature string is required to be sorted by parameter name (comparing the first letter of all parameter names, in abcd order. If the first letters are the same, then it depends on the second letter, and so on, for each of the parameters).

For example: for the following parameters for the signature:

apiKey=376892265asdad5d12726d8bbfbd8912b3&timeStamp=1510235730&nonce=309127&type=in&price=0.04751351&number=10&symbol=eth_btc&tradePwd=asdf Apply for stitching secretKey


sign url : apiKey=376892265asdad5d12726d8bbfbd8912b3&timeStamp=1510235730&nonce=309127&type=in&price=0.04751351&number=10&symbol=eth_btc&tradePwd=asdfaQmE8U7bxj16KdJcSd3yX8F8Sakd8aO6LopnHXh27d4kWyb28PxcaTvGrajLDvAw

The "sign" is the must transferred signature parameters.

Finally, the 32-bit md5 algorithm is used to sign the final signature string to get the signature result string (the string is assigned to the parameter sign).

Return results sample
        "id":"693248739",     //order id
        "uId":"2074056",    //uid
        "price":"100",      //price
        "number":"10",      //number
        "numberOver":"10",  //undealed
        "flag":"sale",      //flag
        "status":0,         //unfilled
        "numberDeal":"0"    //dealed
    "microtime":"0.41892000 1533035297",

results matching ""

    No results matching ""