Changes to Fiat Payments History (USER_DATA)

Changed in 2 of the 26 revisions of this API.▲9●2○19

1. Sep 19, 2023558ab69ec555▲3●2
2. Oct 25, 2021a484ce871a72▲6○19

What changed

• Sep 19, 2023558ab69ec555▲3●2See the full diff
  • ▲

    removed the enum value 0 from the query request parameter transactionType

    request-parameter-enum-value-removed

  • ▲

    removed the enum value 1 from the query request parameter transactionType

    request-parameter-enum-value-removed

  • ▲

    for the query request parameter transactionType, the type changed from string to integer, and format from no format to int32

    request-parameter-type-changed

  • ●

    for the query request parameter transactionType, the max was set to 1.00

    request-parameter-max-set

  • ●

    for the query request parameter transactionType, the min was set to 0.00

    request-parameter-min-set

• Oct 25, 2021a484ce871a72▲6○19See the full diff
  • ▲

    for the query request parameter beginTime, the format changed from no format to int64

    request-parameter-type-changed

  • ▲

    for the query request parameter endTime, the format changed from no format to int64

    request-parameter-type-changed

  • ▲

    for the query request parameter page, the format changed from no format to int32

    request-parameter-type-changed

  • ▲

    for the query request parameter recvWindow, the format changed from no format to int64

    request-parameter-type-changed

  • ▲

    for the query request parameter rows, the format changed from no format to int32

    request-parameter-type-changed

  • ▲

    for the query request parameter timestamp, the format changed from no format to int64

    request-parameter-type-changed

  • ○

    the response property code became required for the status 200

    response-property-became-required

  • ○

    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 data became required for the status 200

    response-property-became-required

  • ○

    the response property data/items/createTime became required for the status 200

    response-property-became-required

  • ○

    the response property data/items/cryptoCurrency became required for the status 200

    response-property-became-required

  • ○

    the response property data/items/fiatCurrency became required for the status 200

    response-property-became-required

  • ○

    the response property data/items/obtainAmount became required for the status 200

    response-property-became-required

  • ○

    the response property data/items/orderNo became required for the status 200

    response-property-became-required

  • ○

    the response property data/items/price became required for the status 200

    response-property-became-required

  • ○

    the response property data/items/sourceAmount became required for the status 200

    response-property-became-required

  • ○

    the response property data/items/status became required for the status 200

    response-property-became-required

  • ○

    the response property data/items/totalFee became required for the status 200

    response-property-became-required

  • ○

    the response property data/items/updateTime became required for the status 200

    response-property-became-required

  • ○

    the response property message 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

  • ○

    the response property success became required for the status 200

    response-property-became-required

  • ○

    the response property total became required for the status 200

    response-property-became-required