Discover/Hyperstats API
live

Hyperstats APIhyperstats.org

Access data from hyperstats.org.

Endpoint health
monitored
get_live_activity
get_wallet_activity
get_wallet_orders
get_wallet_overview
get_wallet_positions
Checks pendingself-healing
Endpoints
5
Updated
3h ago
This call costs1 credit / call— charged only on success
Try it
Restrict events to one coin ticker (e.g. HYPE); values come from available_coins. Omitted = all coins.
Events per page, 1-500.
Number of events to skip (offset pagination).
Comma-separated list of 1-50 Hyperliquid wallet addresses (0x-prefixed, 40 hex chars), e.g. 0xabc...,0xdef.... Do NOT pass an array.
api.parse.bot/scraper/e18f9a3a-a3c0-457b-aa92-58573cfc9983/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/e18f9a3a-a3c0-457b-aa92-58573cfc9983/get_wallet_activity?addresses=0xcf3f419d08a5bdc2c6e5fbd9ad70904c5420f95f' \
  -H 'X-API-Key: $PARSE_API_KEY'
All endpoints · 5 totalmissing one? ·

Returns position-change events (opened, increased, decreased, closed) for one or more tracked wallet addresses, newest first, one record per detected change with before/after size, entry price, margin and position value plus realized PnL on closes/decreases. This is the trade feed a copy-trading bot polls. Paginated by offset over the wallets' full event history; pagination.total and pagination.has_more come from the site. available_coins lists the coins the given wallets have traded. One round trip per call.

Input
ParamTypeDescription
coinstringRestrict events to one coin ticker (e.g. HYPE); values come from available_coins. Omitted = all coins.
limitintegerEvents per page, 1-500.
offsetintegerNumber of events to skip (offset pagination).
addressesrequiredstringComma-separated list of 1-50 Hyperliquid wallet addresses (0x-prefixed, 40 hex chars), e.g. 0xabc...,0xdef.... Do NOT pass an array.
Response
{
  "type": "object",
  "fields": {
    "changes": "array of position-change events; each has id, wallet_address, coin, change_type (opened|increased|decreased|closed), side (long|short), size_before/size_after/size_change, value_change, entry_price_before/after, mark_price, realized_pnl (null unless position reduced/closed), leverage, margin_used_before/after/delta, position_value_before/after, detected_at (ISO 8601), trader_rank, trader_grade. Numeric amounts are decimal strings.",
    "pagination": "object with total, limit, offset, has_more from the site",
    "available_coins": "array of coin tickers traded by the requested wallets"
  },
  "sample": {
    "data": {
      "changes": [
        {
          "id": "2199-0xREDACTED_SECRET-HYPE-increased-long-1788878182696",
          "coin": "HYPE",
          "side": "long",
          "leverage": 5,
          "mark_price": "83.568",
          "size_after": "50000",
          "change_type": "increased",
          "detected_at": "2026-09-08T14:36:22.696Z",
          "size_before": "45000",
          "size_change": "5000",
          "trader_rank": 849,
          "realized_pnl": null,
          "trader_grade": "A+",
          "value_change": "417840",
          "wallet_address": "0xREDACTED_SECRET",
          "entry_price_after": "83.4778",
          "margin_used_after": "839966.202292",
          "margin_used_delta": "83565.66136099992",
          "entry_price_before": "83.4625",
          "margin_used_before": "756400.540931",
          "position_value_after": "4178400",
          "position_value_before": "3760470"
        }
      ],
      "pagination": {
        "limit": 3,
        "total": 12547,
        "offset": 0,
        "has_more": true
      },
      "available_coins": [
        "BTC",
        "DOGE",
        "ETH",
        "HYPE",
        "PAXG",
        "PUMP",
        "SOL",
        "SUI",
        "TAO",
        "XRP"
      ]
    },
    "status": "success"
  }
}

About the Hyperstats API

The Hyperstats API on Parse exposes 5 endpoints for the publicly available data on hyperstats.org. Calls return JSON over HTTPS and are billed per successful response.

Pin a release with the API-Snapshot-Version header so canonical updates don't silently change your contract.