Interface description:
  • Get user history entrust
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
coinFrom no string eos、vtc
coinTo no string btc、eth trade area
type no integer 1:buy,2:sell If no type defined, will return all data
page no integer current page
pageSize no integer show number max:100
startTime no string start time
endTime no string end time
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&nonce=309127&coinFrom=eth&coinTo=btc&type=1&page=1&pageSize= 10&startTime=1510235730&endTime=1510237730 Apply for stitching secretKey


sign url : apiKey=376892265asdad5d12726d8bbfbd8912b3&nonce=309127&coinFrom=eth&coinTo=btc&type=1&page=1&pageSize=10&startTime=1510235730&endTime=1510237730aQmE8U7bxj16KdJcSd3yX8F8Sakd8aO6LopnHXh27d4kWyb28PxcaTvGrajLDvAw

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:
                "status":"3", //0:unfilled, 1:partial deal, 2:all transactions, 3:already cancelled
    "microtime":"0.15305300 1533279329",

results matching ""

    No results matching ""