Hive Blog Scraper
Pricing
from $3.00 / 1,000 results
Hive Blog Scraper
Scrape posts, author feeds, profiles, and communities from the Hive blockchain blogging network (hive.blog). Browse trending/hot/new posts by tag or community, pull an author's blog/feed/comments, look up single or batch posts by URL, fetch profile info, and browse the community directory.
Pricing
from $3.00 / 1,000 results
Rating
0.0
(0)
Developer
Crawler Bros
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a month ago
Last modified
Categories
Share
Scrape posts, author feeds, profiles, and communities from the Hive blockchain blogging network — the same public data that powers hive.blog, PeakD, and Ecency. Browse trending / hot / new posts by tag or community, pull a specific author's blog, feed, comments or replies, look up a single post or a batch of posts by URL, fetch author profile info, or browse the community directory. HTTP-only via the public api.hive.blog JSON-RPC API. No auth, no login, no cookies, no proxy.
What this actor does
- Eleven modes:
posts,byAccount,byPost,byPosts,profile,communities,byCommunity,tags,postComments,followers,following - Six post rankings: trending, hot, new, muted, highest-payout posts, highest-payout comments
- Six author-activity views: blog, feed, own posts, comments, replies received, payout-sorted
- Rich post metadata: payout value, vote count, tags, images, community, comment count, reputation
- Author profiles: bio, avatar/cover images, follower/following counts, post count, reputation
- Community directory: subscriber counts, admins, pending posts, NSFW flag
- Full comment threads: fetch every reply to a post (
postCommentsmode) with the same rich fields as top-level posts - Follower graph: list an account's followers or who it follows (
followers/followingmodes), including muted/ignored relationships - Filters: minimum payout, minimum votes, keyword match, required tag, payout-window status
- Empty fields are omitted — every record only contains fields that actually have data
Output fields
Posts (recordType: "post")
| Field | Description |
|---|---|
postId | author/permlink composite ID |
author, permlink | Post identity |
title, body | Post title and full markdown body |
bodyLength | Character length of the body |
category | Primary tag / community used for the post's main category |
community, communityTitle | Community ID and display name, if posted in a community |
tags[] | All tags from the post's metadata |
images[] | Image URLs extracted from post metadata |
created, updated | Timestamps |
depth | 0 for a top-level post, >0 for a comment |
commentCount | Number of direct replies |
reblogCount | Number of times reblogged |
totalVotes | Total vote count |
payoutValue | Current/pending payout in USD-equivalent |
pendingPayoutValue, authorPayoutValue, curatorPayoutValue | Raw payout strings (e.g. 10.780 HBD) |
maxAcceptedPayout | Author-set ceiling on total payout (e.g. 1000000.000 HBD) |
percentHbd | Percent of the payout taken in HBD vs. Hive Power (0-100) |
beneficiaries[] | Declared payout beneficiaries (account, percent) |
isPaidOut | Whether the 7-day payout window has closed |
payoutAt | UTC time the payout window closes (only while still open) |
authorReputation | Author's display reputation score |
authorTitle, authorRole | Community-assigned author title/role, if any |
sourceApp | App used to publish (e.g. peakd/2026.7.5) |
postUrl | Canonical https://hive.blog/... URL |
Profiles (recordType: "profile")
accountName, reputation, postCount, created, lastActive, followerCount, followingCount, rank, displayName, about, location, website, coverImage, profileImage, profileUrl
Communities (recordType: "community")
communityName, title, about, lang, admins[], isNsfw, authorCount, pendingPostCount, subscriberCount, pendingPayoutSum, createdAt, communityUrl
The single-community lookup (mode=byCommunity) additionally returns: description, flagText (posting/community rules), typeId, team[] ({account, role, title} per member — owner/admin/mod roster).
Tags (recordType: "tag", mode=tags)
tagName, commentCount, topPostCount, totalPayouts (raw string, e.g. "809.296 HBD"), tagUrl
Comments (recordType: "comment", mode=postComments)
Same fields as Posts above, plus parentAuthor and parentPermlink (the post/comment being replied to). The root post itself is excluded — use mode=byPost for that.
Follow relationships (recordType: "follower" / "following", mode=followers/following)
accountName, followType (blog or ignore), accountUrl
Every record also includes recordType and scrapedAt (UTC ISO timestamp).
Input
| Field | Type | Default | Description |
|---|---|---|---|
mode | string | posts | posts / byAccount / byPost / byPosts / profile / communities / byCommunity / tags / postComments / followers / following |
sortPosts | string | trending | mode=posts: trending / hot / created / muted / payout / payout_comments |
tag | string | – | mode=posts: tag or community ID (e.g. hive-142159); blank = site-wide feed. mode=byCommunity: the exact community ID to look up, required |
account | string | – | mode=byAccount / profile: Hive username, with or without @ |
sortAccount | string | blog | mode=byAccount: blog / feed / posts / comments / replies / payout |
postUrl | string | – | mode=byPost/postComments: full post URL or author/permlink shorthand |
postUrls | array | – | mode=byPosts: list of post URLs / shorthands |
followType | string | blog | mode=followers/following: blog (regular follows) or ignore (muted accounts) |
communityQuery | string | – | mode=communities: free-text filter over titles/about |
communitySort | string | rank | mode=communities: rank / new / subs |
minPayoutValue | number | – | Drop posts with payout below this USD value |
minVotes | integer | – | Drop posts with fewer total votes |
keyword | string | – | Case-insensitive substring match on title/body |
requiredTag | string | – | Drop posts missing this tag |
onlyActivePayout | boolean | false | Exclude posts whose payout window already closed |
maxItems | integer | 50 | Hard cap on emitted records (1–1000) |
Example: trending photography posts
{"mode": "posts","sortPosts": "trending","tag": "photography","minPayoutValue": 5,"maxItems": 25}
Example: an author's blog
{"mode": "byAccount","account": "monochromes","sortAccount": "blog","maxItems": 20}
Example: a single post by URL
{"mode": "byPost","postUrl": "https://hive.blog/@monochromes/monomad-august-5th-2026-make-sure-to-read-our-community-and-contest-rules-before-submitting-your-publications"}
Example: community directory search
{"mode": "communities","communityQuery": "photography","communitySort": "rank","maxItems": 20}
Example: single community lookup (rules, roster, subscriber count)
{"mode": "byCommunity","tag": "hive-142159"}
Example: browse trending tags
{"mode": "tags","maxItems": 50}
Use cases
- Content research — track trending topics and top-performing posts across Hive
- Author monitoring — pull a specific writer's full post history or reply activity
- Curation tools — build custom feeds filtered by payout, votes, or tags
- Community analytics — track subscriber growth and activity across Hive communities
- Content archiving — snapshot posts by URL for backup or analysis
FAQs
Does this require a Hive account, API key, or login?
No. All data comes from Hive's public api.hive.blog JSON-RPC API, which requires no authentication.
What is payoutValue?
Hive posts earn rewards from the network over a 7-day payout window, denominated in Hive Dollars (HBD) and Hive Power. payoutValue is the API's USD-equivalent estimate of the post's current/final payout.
Can I fetch comments, not just top-level posts?
Yes — comments are just posts with depth > 0. Use sortAccount: comments (mode=byAccount) to pull an author's comments, or byPost/byPosts with a comment's own URL.
Why do some posts have no payoutValue or tags?
Those fields are only included when the upstream API actually returns them. Very old posts, or posts missing standard JSON metadata, may not have every field.
Is this actor global? Yes — Hive is a single global blockchain network; there are no regional variants. Posts, authors, and communities are all part of one worldwide dataset.
Why do some profile coverImage / profileImage URLs return a broken image?
Those URLs are exactly what the account owner set in their own Hive profile metadata — they can point to any external host (Google Photos, Facebook CDN, a personal site, etc.), and Hive's API returns them verbatim. Some users' links are private, expired, or removed on the hosting side; that is a data-quality property of the source account, not something this actor can control or fix. website, about, and other free-text profile fields carry the same caveat.