Interface description
  • Cancel the order
Request URL:
  • https://apiv2.bitz.com/Trade/cancelEntrustSheet
Request Method:
  • POST
Parameter:
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
entrustSheetId yes string entrust id

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&id=302221&timeStamp=1510235730&nonce=309127&entrustSheetId=123 Apply for stitching secretKey

example:secretKey=aQmE8U7bxj16KdJcSd3yX8F8Sakd8aO6LopnHXh27d4kWyb28PxcaTvGrajLDvAw

sign url : apiKey=376892265asdad5d12726d8bbfbd8912b3&id=302221&timeStamp=1510235730&nonce=309127&entrustSheetId=123aQmE8U7bxj16KdJcSd3yX8F8Sakd8aO6LopnHXh27d4kWyb28PxcaTvGrajLDvAw

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":200,
    "msg":"",
    "data":{
        "updateAssetsData":{
            "coin":"bz",
            "over":"1000.00000000",
            "lock":"-1000.00000000"
        },
        "assetsInfo":{
            "coin":"bz",
            "over":"9999.99999999",
            "lock":"9999.99999999"
        }
    },
    "time":1535464383,
    "microtime":"0.91558000 1535464383",
    "source":"api"
}

results matching ""

    No results matching ""