How to Look Up Crypto Holder Counts with the Mboum API

A holder panel places the holder count beside the address list and uses total as the length of that list. Those two figures answer different questions, and the panel keeps them apart.

key is required. This request sends bitcoin. The counts arrive on meta, and the address rows arrive in data.

To access this endpoint, you must obtain an API key: Get your API key

Read the counts from meta

holderCount is the holder figure. dailyActive is the separate daily figure beside it. Neither number is the length of the address list.

Attach the address rows from data

Each printed address row has address, balance, and share. Balance and share on the printed row are numbers, so the panel copies them as they are. The script keeps meta.total as the list length instead of measuring a shortened excerpt.

import requests

url = "https://api.mboum.com/v1/crypto/holders"
headers = {"Authorization": "Bearer YOUR_API_KEY"}
params = {"key": "bitcoin"}

response = requests.get(url, headers=headers, params=params)
response.raise_for_status()
payload = response.json()
meta = payload["meta"]

addresses = []
for row in payload["data"]:
    addresses.append({
        "address": row["address"],
        "balance": row["balance"],
        "share": row["share"],
    })

panel = {
    "holders": meta["holderCount"],
    "daily_active": meta["dailyActive"],
    "listed": meta["total"],
    "addresses": addresses,
}
print(panel)

Treat total as the address-list length

The excerpt keeps the one address the file prints in full, plus the three meta counts the panel uses. total counts the address list. It is not a second copy of holderCount, so the panel labels them separately.

{
  "meta": {
    "holderCount": 48834937,
    "dailyActive": 963625,
    "total": 100
  },
  "data": [
    {
      "address": "34xp4vRoCGJym3xR7yCVPFHoCNxv4Twseo",
      "balance": 248597.3905837,
      "share": 1.18
    }
  ]
}

Further addresses are not printed in the file. The panel does not invent them, and it does not treat the holder count as the number of rows.

Learn more or explore other endpoints: crypto holders