Bluesky Scraper — Posts, Graphs & AT Protocol
Pricing
from $1.00 / 1,000 profile results
Bluesky Scraper — Posts, Graphs & AT Protocol
Scrape public Bluesky profiles, posts, threads, search, followers, likes, reposts, lists, feeds, trends, and AT Protocol repository records with stable DID and AT URI provenance.
Pricing
from $1.00 / 1,000 profile results
Rating
0.0
(0)
Developer
ScrapingMonkey
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
23 days ago
Last modified
Categories
Share
Bluesky Scraper - Profiles, Posts, Search, Followers and Feeds
Collect public Bluesky profiles, posts, threads, search results, interactions, social graph data, lists, feeds, trends, and AT Protocol repository records.
- Extract profile identity, bio, verification data, audience counts, avatars, and banners
- Collect author feeds, individual posts, complete threads, parents, replies, media, links, and engagement counts
- Search public posts or accounts with available sorting, language, and date filters
- Export likes, reposts, quotes, followers, follows, list members, and suggested accounts
- Discover public lists, custom feeds, popular feeds, and current trend records
- Read public AT Protocol repository collections directly from each actor's discovered PDS
- No Bluesky account, app password, cookies, browser, or user-supplied proxy is required; requests use the built-in Apify Residential Proxy
- Export results to JSON, CSV, Excel, XML, RSS, or access them through the Apify API
What can you do with this Actor?
| Mode / action | Input | Output | Best for |
|---|---|---|---|
profiles | Handles, DIDs, or profile URLs | profile rows | Profile metrics and creator research |
authorFeeds | Handles, DIDs, or profile URLs | Paginated post rows | Publishing analysis and monitoring |
posts | AT URIs or public post URLs | Complete post rows | Batch post enrichment |
threads | AT URIs or public post URLs | Root, parent, and reply post rows | Conversation and reply analysis |
postInteractions | AT URIs or public post URLs plus interaction types | interaction rows | Likes, reposts, and quote relationships |
searchPosts | Search terms and optional filters | Matching post rows | Topic research and social listening |
searchActors | Search terms | Matching profile rows | Account discovery |
followers / follows | Handles, DIDs, or profile URLs | Connected profile rows | Public audience and network analysis |
lists / listItems | Actors or public list AT URIs | list or member profile rows | Curated network research |
actorFeeds / popularFeeds | Actors or no specific target | Public feed rows | Feed discovery and cataloging |
customFeed | Public feed-generator AT URIs | Feed post rows | Custom-feed content analysis |
trends | No target beyond the selected mode | Public trend rows | Topic and trend tracking |
suggestedFollows | Handles, DIDs, or profile URLs | Suggested profile rows | Account discovery and graph expansion |
repoRecords | Actors and public AT Protocol collections | repoRecord rows from each actor's PDS | Protocol research and public record export |
auto | Mixed public profile and post URLs | profile or post rows selected from each URL | Batch processing mixed known targets |
Choose one mode per run. Multiple actors, posts, lists, feeds, or search terms can be processed in one run, and maxItems applies separately to each input target or collection.
Quick start
- Open the Actor and click Try for free.
- Keep Author Feeds selected or choose another public Bluesky workflow.
- Enter handles, DIDs, URLs, AT URIs, or search terms and set the result limit.
- Click Start.
- Preview the single Results table or download it in your preferred format.
The default input collects recent public posts from bsky.app and is ready to run.
Input examples
Profiles and counts
Recent author posts
Search posts
Thread and replies
Followers
Public repository
Post details
Likes, reposts, and quotes
Search actors
Accounts followed by an actor
Lists created by an actor
Members of a public list
Feed generators created by an actor
Posts from a custom feed
Popular public feeds
Public trends
Suggested follows for an actor
Auto-detect mixed public URLs
The examples cover every supported mode. One dataset row represents a profile, post, interaction, list, feed, trend, or repository record and always uses the same 63-field top-level contract.
Complete output examples
Every result row contains exactly 63 top-level fields. The same complete key set makes mixed result types predictable in JSON exports and keeps every field visible in the single Results view.
Complete profile row — 63 top-level fields
Complete post row — 63 top-level fields
Complete interaction row — 63 top-level fields
Complete list row — 63 top-level fields
Complete feed row — 63 top-level fields
Complete trend row — 63 top-level fields
Complete repoRecord row — 63 top-level fields
What data can you extract?
| Category | Fields |
|---|---|
| Source and capture | recordType, sourceMode, sourceTarget, sourceUrl, sourceEndpoints, capturedAt |
| Profile identity | did, handle, displayName, description, profileUrl, avatarUrl, bannerUrl, indexedAt, createdAt, labels, verification |
| Profile metrics | followersCount, followsCount, postsCount |
| Posts and threads | uri, cid, postUrl, text, languages, replyCount, repostCount, likeCount, quoteCount, author, embed, facets, reply, threadRootUri, threadDepth |
| Social interactions | interactionType, targetUri, edgeActor |
| Search provenance | searchTerm |
| Lists | listUri, listName, listPurpose, listAvatar |
| Feeds | feedUri, feedName, feedDescription, feedCreator |
| Trends | trendTopic, trendDisplayName, trendDescription, trendLink, trendStatus, trendPostCount |
| Repository records | repoDid, collection, recordKey, pds, recordValue |
| Monitoring and diagnostics | isPartial, monitorStatus, changedFields, previousCapturedAt, raw |
Nested fields such as labels, verification, author, embed, facets, reply, edgeActor, feedCreator, recordValue, and optional raw retain the public AT Protocol object structure. Their nested keys and union variants are source-controlled and can change; the 63 top-level keys above are fixed by the Actor.
Input parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
mode | string | No | "authorFeeds" | Select one of the 18 public Bluesky or AT Protocol workflows listed above. |
actors | string[] | In actor-based modes | ["bsky.app"] | Bluesky handles, DIDs, or profile URLs. |
postUris | string[] | In post modes | [] | AT URIs or public bsky.app post URLs. |
listUris | string[] | In listItems | [] | Public at:// list URIs. |
feedUris | string[] | In customFeed | [] | Public at:// feed-generator URIs. |
searchTerms | string[] | In search modes | [] | Queries for public post or actor search. |
startUrls | string[] | In auto | [] | Mixed public profile or post URLs. |
maxItems | integer | No | 100 | Maximum retained records per target or collection, from 1 to 100,000. |
maxPages | integer | No | 20 | Maximum XRPC cursor pages per endpoint, from 1 to 1,000. |
searchSort | string | No | "latest" | latest or top for public post search. |
language | string | No | "" | Optional BCP 47 language filter for post search. |
since | string | No | "" | Optional ISO date/timestamp lower bound for post search. |
until | string | No | "" | Optional ISO date/timestamp upper bound for post search. |
feedFilter | string | No | "posts_with_replies" | posts_with_replies, posts_no_replies, posts_with_media, or posts_and_author_threads. |
threadDepth | integer | No | 20 | Requested child depth for threads, from 0 to 1,000. |
parentHeight | integer | No | 20 | Requested parent height for threads, from 0 to 1,000. |
interactionTypes | string[] | No | ["likes", "reposts", "quotes"] | Public relationship types extracted by postInteractions. |
collections | string[] | In repoRecords | ["app.bsky.feed.post"] | Public AT Protocol collections requested from each actor's PDS. |
maxConcurrency | integer | No | 10 | Concurrent public targets, from 1 to 50. |
country | string | No | "US" | Two-letter ISO country used for the internal residential proxy region. |
includeRaw | boolean | No | false | Include the redacted public source object; increases dataset size. |
monitorMode | string | No | "off" | off, onlyNew, or newAndChanged. |
monitorKey | string | With monitoring | "default" | Stable comparison-state namespace for recurring runs. |
maxSessionRotations | integer | No | 3 | Fresh residential sessions tried after blocks, from 1 to 6. |
requestTimeoutSecs | integer | No | 45 | Per-request timeout in seconds, from 15 to 120. |
Pay-per-event result types
| Event | Charged when |
|---|---|
profile-result | One profile row is accepted by the Dataset. |
post-result | One post row is accepted by the Dataset. |
interaction-result | One interaction row is accepted by the Dataset. |
list-result | One list row is accepted by the Dataset. |
feed-result | One feed row is accepted by the Dataset. |
trend-result | One trend row is accepted by the Dataset. |
repo-record-result | One repoRecord row is accepted by the Dataset. |
The Actor does not emit a paid error event. Failed targets are counted by category in RUN_SUMMARY; successful targets continue. Actual event prices are shown on the Actor's Pricing tab.
Use cases
Social listening and content research
Search public posts, collect author feeds, and analyze text, embeds, replies, reposts, likes, quotes, and thread structure.
Creator and network intelligence
Enrich profiles and export public follower, following, list, and interaction relationships for graph or audience analysis.
Feed and trend discovery
Catalog public custom feeds, popular feeds, suggested accounts, and current trend records.
AT Protocol research
Export public repository records with DID, collection, record key, PDS, CID, and complete public record values.
Data and automation pipelines
Send normalized rows to Google Sheets, Airtable, Make, Zapier, n8n, Airbyte, webhooks, or a data warehouse.
Performance and cost
Direct HTTP generally uses substantially less memory and bandwidth than launching a browser, but source response size, retries, optional enrichment, raw objects, and pagination determine actual cost. Start with a small limit, inspect the Dataset and RUN_SUMMARY, then scale. Lower concurrency is usually more reliable on stricter public sites.
API usage
Replace YOUR_USERNAME with the publishing Apify username after publication:
The request body is the same JSON used in Apify Console. Read results from the run's default Dataset or use the output link that opens view=overview.
Best for / not for
Best for: public profiles and posts, threads, interactions, search, public graph data, lists, feeds, trends, and AT Protocol repository exports.
Not for: notifications, bookmarks, chats, private data, account writes, moderation actions, or endpoints that require an authenticated Bluesky session.
Limits and good to know
Only anonymous public AppView, PLC, and PDS endpoints are used. Authenticated notifications, private data, writes, moderation actions, chat, and endpoints that reject anonymous traffic are outside scope. A row can be marked isPartial when a host stops later cursor pages.
A missing public value is returned as null or an empty array. One failed input does not create a frightening error row in Results. If every input fails, the run fails after writing diagnostic counts to RUN_SUMMARY.
Frequently asked questions
What input should I provide?
Depending on the mode, provide handles, DIDs, profile URLs, AT URIs, public post URLs, list or feed AT URIs, search terms, or public repository collection names.
How many results can I extract?
maxItems accepts 1-100,000 per input target or collection and maxPages accepts 1-1,000. Public endpoint limits, cursor exhaustion, moderation, and host availability can reduce the result count.
Can I process multiple inputs?
Yes. All target fields are arrays, and independent targets continue when one target or endpoint fails.
Can I schedule recurring runs?
Yes. Use Apify schedules and webhooks. For delta output, set monitorMode and reuse a stable monitorKey across runs.
Does this Actor open a browser?
No. Runtime extraction uses direct HTTP only and contains no Playwright, Selenium, Chromium, or browser installation.
Do I need an account or cookies?
No. The supported modes use public pages and anonymous endpoints. Cookies or authorization values from research captures are never embedded in the release.
Do I need to configure a proxy?
No. On Apify, the Actor creates a Residential Proxy configuration internally and does not expose proxy settings in Input. Local developers may privately point the documented test-only environment variable at a proxy file; that variable is not an Actor input and is ignored on the platform.
Why are some fields empty?
The single Results view covers every result type. Fields that do not apply to a row remain empty, while the complete key set is preserved in JSON.
Responsible use
Collect only public Bluesky data you are permitted to process. Respect applicable law, privacy rights, platform terms, rate limits, and intellectual-property rights. This Actor is not affiliated with or endorsed by Bluesky.
Support
For a reproducible issue, include the Apify run ID, mode, a non-sensitive public target, expected result, and actual result. Never send account credentials, cookies, access tokens, proxy passwords, or private content.
Local development
For local read-only smoke tests only, BLUESKY_TEST_PROXY_FILE may point to a private file containing one login:password@host:port proxy per line. The file is never read on Apify and must not be committed.
