Bluesky Scraper: Posts, Profiles, Threads & Followers
DeprecatedPricing
Pay per usage
Bluesky Scraper: Posts, Profiles, Threads & Followers
DeprecatedAll-in-one Bluesky extractor on the official AT Protocol public API. Search posts (keyword, hashtag, author, domain, date), pull an account feed, scrape a post's reply thread, read custom feeds, or list profiles and followers. Clean JSON with engagement & media — no login, no proxies.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Nomad.Devs
Maintained by CommunityActor stats
0
Bookmarked
3
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Features
Share
Bluesky Scraper — Posts, Profiles, Threads & Followers
Start with one input and output
An Apify account is required. Use your Apify API token when calling the API; Console runs do not need that token pasted into the input. Basic collection needs no Bluesky login, proxy or AI key. Optional AI analysis needs your own provider key and has separate provider costs.
Free-tier event rates checked 2026-10-04: result $0.002; actor-start $0.005. Scale and Business plans pay less per result event: $0.15 and $0.1 per 1,000.
Cost: Total = Actor event charges + platform usage if separately billed + any BYO-provider charges. See “Current costs” for your event rates, plan tiers and a calculation. A sample does not promise future billable volume.
Input and output below were read from the same successful run 55nCtANEimWKwWJKd (2026-10-04, immutable build EWJ2GCtSOer47h7g5). This is an observed example, not a guarantee that repeating it returns this row. It used the selected build at capture time.
Input JSON
{"mode": "search","includeReplies": false,"maxItems": 100,"threadDepth": 6,"parentHeight": 0,"sort": "latest","minLikes": 0,"minReposts": 0}
Matching output excerpt
Long strings and arrays are shortened for display; this is not a complete dataset fixture.
{"mode": "search","uri": "at://did:plc:bwr4uw4uuyv3qz4i3f73wmov/app.bsky.feed.post/3mx2v7phr3l2l","cid": "bafyreibse5fzij3ehnk2frr2lm2vj7kuwxxrc3lvo6oow6nm7fmdfseehi","url": "https://bsky.app/profile/spaisee.bsky.social/post/3mx2v7phr3l2l","authorHandle": "spaisee.bsky.social","authorDid": "did:plc:bwr4uw4uuyv3qz4i3f73wmov","authorDisplayName": "spaisee.bsky.social","text": "AI safety claims need receipts. A GPT-6.1 report and OpenAI documents appear to tell very different stories.\n\n#AI #AISafety #TechNews https://spaisee.com/article/openai-s-gpt-6-1-story-shows-why-ai-safety-reporting-needs-receipts","createdAt": "2026-10-04T17:07:02.638Z","indexedAt": "2026-10-04T17:07:03.061Z","langs": [],"replyCount": 0,"repostCount": 0,"likeCount": 0,"quoteCount": 0,"bookmarkCount": 0,"replyParentUri": null,"replyRootUri": null,"tags": ["AI","AISafety"],"mentions": [],"links": ["https://spaisee.com/article/openai-s-gpt-6-1-story-shows-why-ai-safety-reporting-needs-receipts"],"embedType": "external","mediaUrls": [],"mediaAlt": [],"externalUrl": "https://spaisee.com/article/openai-s-gpt-6-1-story-shows-why-ai-safety-reporting-needs-receipts?utm_source=bluesky&utm_medium=social","externalTitle": "OpenAI’s GPT-6.1 Story Shows Why AI Safety Reporting Needs Receipts","quotedUri": null}
Extract Bluesky data in one Actor: search posts by keyword or hashtag, pull any account's post feed, scrape a post's reply thread to the requested depth, read a custom/algorithmic feed, fetch profile details, or list followers and following — all through the official AT Protocol public API. No login, no cookies, no proxies.
Claude / Codex skill to describe and setup this actor: SKILL.md
What Bluesky data does this scraper extract?
Post records (search, authorFeed, thread and feed modes) — one flat JSON record per post:
| Field | Meaning |
|---|---|
uri / cid | Stable AT Protocol identifiers of the post |
url | Direct bsky.app link to the post |
authorHandle / authorDid / authorDisplayName | Who posted it |
text | Full post text |
createdAt / indexedAt | When it was posted / indexed |
likeCount / repostCount / replyCount / quoteCount / bookmarkCount | Engagement counts |
langs | Declared post languages |
tags / mentions / links | Hashtags, @-mention DIDs and hyperlinks parsed from the post's richtext facets |
embedType / mediaUrls / mediaAlt / externalUrl / externalTitle / quotedUri | Media & embeds: images/video/gallery URLs and alt text, external link cards, and quoted-post URIs |
replyParentUri / replyRootUri | The post this replies to, and the thread root (null if not a reply) |
isRepost / feedOf | Repost flag and source handle/feed (authorFeed, feed modes) |
depth / parentUri / rootUri / isRoot / threadUri | Thread structure (thread mode) |
mode | Which mode produced the record |
Profile records (profile, followers, following modes): did, handle, url, displayName, description, avatar, createdAt, plus followersCount / followsCount / postsCount in profile mode and subjectHandle in follower/following modes.
Modes
| Mode | What it returns | Key inputs |
|---|---|---|
search | Posts matching a keyword/hashtag, with date, author, mention, language, domain/url/tag and engagement filters | query, postedWithin, fromAuthor, mentionsAuthor, language, domain, url, tag, sort, minLikes, minReposts |
authorFeed | Posts by one or more accounts | handles, includeReplies, minLikes, minReposts |
thread | A post plus replies to the requested depth (and optional ancestors) | threadUris, threadDepth, parentHeight |
feed | Posts from a custom/algorithmic feed generator | feedUris |
profile | Profile details (bio, counts) per account | handles |
followers | Accounts following the given handles | handles |
following | Accounts the given handles follow | handles |
Search supports Bluesky query operators typed straight into query — #hashtag, "exact phrase", from:user.bsky.social, mentions:user.bsky.social, lang:en, and more. The most common ones also have dedicated inputs so you don't have to remember the operator syntax:
fromAuthor— only posts written by this handle (same asfrom:). UsessearchPosts' ownauthorfilter param, not just a query-string trick.mentionsAuthor— only posts that mention this handle (same asmentions:). Uses thementionsfilter param.language— only posts declared in this ISO 639-1 language code (same aslang:). Uses thelangfilter param.
Search requires a non-empty query, including when using dedicated filters: they narrow that query. An author-only request belongs in authorFeed mode with handles. The #ai fallback applies only to an otherwise plain search; it does not replace an explicitly empty query or choose a topic for a filter-only request.
These compose safely with query, postedWithin and sort in the same request. The searchPosts endpoint's dedicated domain/url/tag filters are also wired up as first-class inputs:
domain— only posts linking to this domain (e.g.nytimes.com).url— only posts linking to this exact URL.tag— only posts carrying these hashtags (enter each without the leading#).
Bluesky's unauthenticated search API does not allow cursor paging, so the Actor transparently paginates latest searches by walking the time window backwards — you still just set maxItems. top sort is not time-ordered and returns up to 100 posts per run.
minLikes / minReposts filter posts client-side, after they're fetched from the API — set either to skip low-engagement noise in the search, authorFeed, thread and feed post modes. Filtered-out posts are never pushed to the dataset, so you aren't billed for them.
Thread & custom-feed modes
thread mode returns a post and available replies to the requested depth via the AT Protocol getPostThread endpoint. Put post links or at:// URIs in threadUris, set threadDepth for how many reply levels to fetch, and parentHeight to also pull ancestor posts above the requested one. Every record carries depth (0 = the requested post, 1+ = replies, negative = ancestors), parentUri, rootUri and isRoot, so you can rebuild the returned conversation tree. Count, deadline, charge and source limits can stop collection before the requested depth is reached.
feed mode reads a custom/algorithmic feed generator via getFeed. Put feed links (https://bsky.app/profile/<handle>/feed/<rkey>) or at://.../app.bsky.feed.generator/... URIs in feedUris; handles are resolved to DIDs automatically. Records include feedOf (the feed) and isRepost.
How to scrape Bluesky with this Actor
- Click Try for free / Run — no Bluesky account needed, only public data is read.
- Pick a
mode, set aqueryorhandles, adjustmaxItemsor keep the defaults. - Run it and export the dataset as JSON, CSV or Excel, or read it over the API.
Run it from your own code:
from apify_client import ApifyClientclient = ApifyClient("<YOUR_APIFY_TOKEN>")run = client.actor("nomad-agent/bluesky-scraper").call(run_input={"mode": "search","query": "#ai","postedWithin": "7d","maxItems": 200,})for item in client.dataset(run["defaultDatasetId"]).iterate_items():print(item["authorHandle"], "—", item["text"][:80], item["url"])
Or a single HTTP call that runs the Actor and returns items in one response:
curl -X POST \"https://api.apify.com/v2/acts/nomad-agent~bluesky-scraper/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \-H "Content-Type: application/json" \-d '{"mode": "authorFeed", "handles": ["bsky.app"], "maxItems": 50}'
Run the same search again and you get only posts and accounts you have not received yet; set dedupe.enabled to false to see everything again.
Input
General fields (apply across modes):
| Field | Type | Default | Notes |
|---|---|---|---|
mode | string | search | One of search, authorFeed, thread, feed, profile, followers, following. |
handles | array | — | Handles or DIDs for authorFeed/profile/followers/following. Leading @ optional. |
includeReplies | boolean | false | Include the author's replies in authorFeed mode. |
maxItems | integer | 100 | Maximum source records for the run. Set 0 to remove only the count limit; deadline, charge and source limits still apply. |
Thread & feed fields:
| Field | Type | Default | Notes |
|---|---|---|---|
threadUris | array | — | Post URLs / at:// URIs whose reply thread to scrape (thread mode). |
threadDepth | integer | 6 | Levels of replies to fetch below the post (thread mode). |
parentHeight | integer | 0 | Ancestor posts above the requested one to include (thread mode). |
feedUris | array | — | Feed URLs / at:// generator URIs to read (feed mode). |
Search fields (search mode; minLikes/minReposts also apply to authorFeed/thread/feed):
| Field | Type | Default | Notes |
|---|---|---|---|
query | string | #ai when omitted in a plain search | Keyword/hashtag for search mode. Supports Bluesky search operators. The advertised #ai example is used for empty API input; an explicit blank query or an alternate search target is preserved. |
postedWithin | string | (omitted; form prefill any) | Only posts created inside this window. any for no date filter, or a duration — 1h, 24h, 3d, 2w, 6m. |
fromAuthor | string | — | Only posts written by this handle (from: operator / author param). |
mentionsAuthor | string | — | Only posts that mention this handle (mentions: operator / mentions param). |
language | string | — | Only posts in this ISO 639-1 language code (lang: operator / lang param). |
domain | string | — | Only posts linking to this domain (domain param). |
url | string | — | Only posts linking to this exact URL (url param). |
tag | array | — | Only posts carrying these hashtags, entered without # (tag param). |
sort | string | latest | latest (newest first) or top (by relevance) for search mode. |
minLikes | integer | 0 | Drop posts with fewer likes than this (compares likeCount). 0 = no filter. |
minReposts | integer | 0 | Drop posts with fewer reposts than this (compares repostCount). 0 = no filter. |
Output example
{"mode": "search","uri": "at://did:plc:z72i7hdynmk6r22z27h6tvur/app.bsky.feed.post/3lb2abcxyz","cid": "bafyreib2rxk3rw6...","url": "https://bsky.app/profile/bsky.app/post/3lb2abcxyz","authorHandle": "bsky.app","authorDid": "did:plc:z72i7hdynmk6r22z27h6tvur","authorDisplayName": "Bluesky","text": "Introducing new moderation tools...","createdAt": "2026-06-15T18:02:11.000Z","indexedAt": "2026-06-15T18:02:12.345Z","langs": ["en"],"replyCount": 412,"repostCount": 1287,"likeCount": 9034,"quoteCount": 187,"bookmarkCount": 54,"replyParentUri": null,"replyRootUri": null,"tags": ["moderation"],"mentions": [],"links": ["https://bsky.social/about/blog"],"embedType": "external","mediaUrls": [],"mediaAlt": [],"externalUrl": "https://bsky.social/about/blog","externalTitle": "Bluesky Blog","quotedUri": null}
Compatibility
This release returns source data without built-in AI analysis. The former aiSentiment, aiTopics and aiSummary fields are no longer emitted; old AI settings are ignored, and source text remains available for your own analysis. postedWithin is the date control shown in the input form. Saved API inputs using since and until retain their absolute date bounds when postedWithin is absent; an explicitly supplied postedWithin, including any, takes precedence.
Pricing
Check the Actor's current Apify pricing panel for per-run and per-record rates. Your run's maximum total charge limits billed output.
minLikes and minReposts are applied before records are pushed, so filtered-out posts are never billed.
Integrations
Export the dataset as JSON, CSV, Excel or HTML, pull it over the Apify API (including run-sync-get-dataset-items for a single blocking call), wire it into Make, Zapier or n8n, or call it as a tool from an AI agent via the Apify MCP server.
Use cases
- Brand, keyword and hashtag monitoring on Bluesky
- Social listening and sentiment datasets for AI/LLM pipelines
- Influencer discovery via follower/following graphs and engagement counts
- Exporting an account's available posts within run and source limits
- Trend and virality analysis with like/repost/reply counts
FAQ
Is it legal to scrape Bluesky?
This Actor reads only publicly available data through Bluesky's own public AT Protocol API (public.api.bsky.app) — the same data any logged-out visitor can see. No authentication is used and no private data is touched. Review Bluesky's terms and your local regulations for your specific use case.
Do I need a Bluesky account? No. All seven modes use unauthenticated public endpoints.
How fresh is the data?
Every run reads the live API. search with sort: latest requests the newest indexed matches; source indexing and pagination determine which posts are available.
How many records can I get?
maxItems caps the record count; set 0 to remove that count limit. Pagination still stops at the Actor's 200-second collection deadline, the run's charge cap, or source pagination limits. A note row reports when the collection deadline stops a run; it is not a post. Full account or follower archives are not guaranteed.
What about deleted or blocked accounts? Handles that cannot be resolved (typos, deactivated accounts) are logged and skipped — one bad handle never fails the whole run.
Which search operators are supported as dedicated inputs?
fromAuthor, mentionsAuthor, language, domain, url and tag map to searchPosts' own author, mentions, lang, domain, url and tag filter params (verified against the live API) — equivalent to from:, mentions:, lang:, domain: and #tag in query, but composable with it via proper params instead of string-building.
Something broken or missing? Open an issue on the Actor's Issues tab — it is monitored and reliability fixes ship fast.
Credits
Independent implementation on the official AT Protocol public API. Design informed by the MIT-licensed deepfates/bsky-scraper firehose archiver — see LICENSE for the attribution note.
Fast setup and source code
Public repository · Agent setup skill.
Use the Actor’s current input form for filters, or start with its documented API example. Select latest for bluesky-scraper and record the immutable build ID and number returned by your run. Inspect the dataset and any run summary the Actor documents together; a successful status alone does not establish complete source coverage.
Restrictive filters or source availability can produce zero results. Diagnostic and note rows are uncharged status records and do not count as posts. This Actor returns source data without built-in AI analysis or translation.
Product guides and related tools
Current costs
Current Actor event rates, checked 2026-10-16. USD; use the Pricing tab for your plan and later changes.
| Event | Free | Bronze | Silver | Gold | Platinum | Diamond |
|---|---|---|---|---|---|---|
Bluesky record (result) | $0.0002 | $0.0002 | $0.00015 | $0.0001 | $0.0001 | $0.0001 |
Actor start (actor-start) | $0.00005 | $0.00005 | $0.00005 | $0.00005 | $0.00005 | $0.00005 |
For example, 100 × result, 1 × actor-start totals $0.205 in Actor event charges on Free. This is an arithmetic example, before any waiver; actual charged events depend on the run and selected options. It is not a promise of output or a charge for simply setting an item cap.
Your total is the charged Actor events, plus platform usage only if this Actor’s Pricing tab bills it separately, plus any external provider you use with your own key. Do not add platform usage twice when it is included. Apify credits and plan discounts affect your invoice. Set a run cost limit in Console before starting.