Changes to Query Subscription Record (USER_DATA)

Changed in 1 of the 26 revisions of this API.▲6●1○11

1. Oct 25, 2021a484ce871a72▲6●1○11

What changed

• Oct 25, 2021a484ce871a72▲6●1○11See 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 timstamp from the response with the 200 status

    response-optional-property-removed

  • ○

    the response property amount 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 fee became required for the status 200

    response-property-became-required

  • ○

    the response property id 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 nav became required for the status 200

    response-property-became-required

  • ○

    the response property tokenName became required for the status 200

    response-property-became-required

  • ○

    the response property totalCharge became required for the status 200

    response-property-became-required

  • ○

    added the required property timestamp to the response with the 200 status

    response-required-property-added