BLVT

Redemption Record (USER_DATA)

Only the data of the latest 90 days is available

Weight(IP): 1

get/sapi/v1/blvt/redeem/record

Query parameters

tokenNamestring

BTCDOWN, BTCUP

idinteger

startTimeinteger

UTC timestamp in ms

endTimeinteger

UTC timestamp in ms

limitinteger

default 1000, max 1000

recvWindowinteger

Example:5000

The value cannot be greater than 60000

timestampinteger required

UTC timestamp in ms

signaturestring required

Signature

Response

List of redemption record

idinteger required

tokenNamestring required

amountstring required

Redemption amount

navstring required

NAV of redemption

feestring required

Reemption fee

netProceedstring required

Net redemption value in usdt

timestampinteger required

Example response

[
  {
    "id": 1,
    "tokenName": "LINKUP",
    "amount": "0.54216292",
    "nav": "18.36345064",
    "fee": "0.00995598",
    "netProceed": "9.94602604",
    "timestamp": 1599128003050
  }
]

Changes

Changed in 1 of the 26 revisions of this API.6111

Oct 25, 2021a484ce871a726111See the full diff
- ▲
  for the query request parameter endTime, the type/format was changed from integer/ to integer/int64
  request-parameter-type-changed
- ▲
  for the query request parameter id, the type/format was changed from integer/ to integer/int64
  request-parameter-type-changed
- ▲
  for the query request parameter limit, the type/format was changed from integer/ to integer/int32
  request-parameter-type-changed
- ▲
  for the query request parameter recvWindow, the type/format was changed from integer/ to integer/int64
  request-parameter-type-changed
- ▲
  for the query request parameter startTime, the type/format was changed from integer/ to integer/int64
  request-parameter-type-changed
- ▲
  for the query request parameter timestamp, the type/format was changed from integer/ to integer/int64
  request-parameter-type-changed
- ●
  removed the optional property items/timstamp from the response with the 200 status
  response-optional-property-removed
- ○
  the response property code became required for the status 400
  response-property-became-required
- ○
  the response property code became required for the status 401
  response-property-became-required
- ○
  the response property items/amount became required for the status 200
  response-property-became-required
- ○
  the response property items/fee became required for the status 200
  response-property-became-required
- ○
  the response property items/id became required for the status 200
  response-property-became-required
- ○
  the response property items/nav became required for the status 200
  response-property-became-required
- ○
  the response property items/netProceed became required for the status 200
  response-property-became-required
- ○
  the response property items/tokenName became required for the status 200
  response-property-became-required
- ○
  the response property msg became required for the status 400
  response-property-became-required
- ○
  the response property msg became required for the status 401
  response-property-became-required
- ○
  added the required property items/timestamp to the response with the 200 status
  response-required-property-added

Full history