Statistic List (USER_DATA)

Weight(IP): 5

get/sapi/v1/mining/statistics/user/status

Query parameters

algostring required

Algorithm(sha256)

userNamestring required

Mining Account

recvWindowinteger

Example:5000

The value cannot be greater than 60000

timestampinteger required

UTC timestamp in ms

signaturestring required

Signature

Response

Mining account statistics

codeinteger required

msgstring required

Example response

{
  "data": {
    "fifteenMinHashRate": "457835490067496409.00000000",
    "dayHashRate": "214289268068874127.65000000",
    "invalidNum": 17562,
    "profitToday": {
      "BTC": "0.00314332",
      "BSV": "56.17055953",
      "BCH": "106.61586001"
    },
    "profitYesterday": {
      "BTC": "0.00314332",
      "BSV": "56.17055953",
      "BCH": "106.61586001"
    },
    "userName": "test",
    "unit": "h/s",
    "algo": "sha256"
  }
}

Changes

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

Oct 25, 2021a484ce871a72222See the full diff
- ▲
  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 timestamp, the type/format was changed from integer/ to integer/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/algo became required for the status 200
  response-property-became-required
- ○
  the response property data/dayHashRate became required for the status 200
  response-property-became-required
- ○
  the response property data/fifteenMinHashRate became required for the status 200
  response-property-became-required
- ○
  the response property data/invalidNum became required for the status 200
  response-property-became-required
- ○
  the response property data/profitToday became required for the status 200
  response-property-became-required
- ○
  the response property data/profitToday/BCH became required for the status 200
  response-property-became-required
- ○
  the response property data/profitToday/BSV became required for the status 200
  response-property-became-required
- ○
  the response property data/profitToday/BTC became required for the status 200
  response-property-became-required
- ○
  the response property data/profitYesterday became required for the status 200
  response-property-became-required
- ○
  the response property data/profitYesterday/BCH became required for the status 200
  response-property-became-required
- ○
  the response property data/profitYesterday/BSV became required for the status 200
  response-property-became-required
- ○
  the response property data/profitYesterday/BTC became required for the status 200
  response-property-became-required
- ○
  the response property data/unit became required for the status 200
  response-property-became-required
- ○
  the response property data/userName became required for the status 200
  response-property-became-required
- ○
  the response property data/validNum became required for the status 200
  response-property-became-required
- ○
  the response property msg 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

Full history