How to Scrape Bluesky Posts by Keyword or Profile

Bluesky is small enough to study and large enough to matter for some communities. If you do social listening, research or an archive, you want posts with their engagement, links and media — not a pile of screenshots. You also should not have to hand a scraper your app password. This guide shows how to scrape Bluesky posts by keyword, hashtag or profile, with no login.

You will use the Bluesky Post Scraper on Apify. Search by keyword or hashtag (latest or top), or export a profile's feed. Each post can include text, date, likes, reposts, replies, quotes, author, hashtags, links, images, video and link cards. Language and date filters are available.

By the end of this article you will have a CSV or JSON file on your machine, and a short Python snippet you can rerun or schedule. The same Actor is also callable from JavaScript and from AI agents through the Apify MCP server.

What you need

  • An Apify account. The Free plan is enough to try a small run.
  • A list of inputs for the Actor (URLs, IDs or search terms — details in the steps below).
  • Optional: Python 3 with the apify-client package if you want to automate the run.

No Bluesky account or app password is required. A search query is enough for a first run.

How to run it in the Apify Console

Step 1: Open the Actor

Open https://apify.com/veenkes/veenkes-bluesky-posts and click Try for free.

Step 2: Add queries or profiles

A keyword such as web scraping or a hashtag works. You can also paste profile handles to export their posts.

Step 3: Filter and cap

Choose latest or top sort, a language, and optional since / until dates. Set max posts per source to 20 or 50 for a test. Decide whether a profile export should include replies or reposts.

Step 4: Export CSV

Start the run and download CSV or JSON. Engagement fields are already on the row, so you can sort by likes or reposts in a spreadsheet.

Language and date filters keep a listening job from drifting. Large profile backfills should be dated or capped rather than pulled in one unlimited run.

How to run it from Python

Install the official client and call the Actor by its Store id veenkes/veenkes-bluesky-posts. Replace YOUR_APIFY_TOKEN with a token from Apify Console > Integrations. Do not commit the token to a public repository.

pip install apify-client 
from apify_client import ApifyClient client = ApifyClient("YOUR_APIFY_TOKEN") run = client.actor("veenkes/veenkes-bluesky-posts").call(run_input={ "searchQueries": [ "web scraping" ], "sort": "latest", "maxPostsPerSource": 50 }) # Write every dataset item, then export from the Console or keep going in code. for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) 

The JavaScript client (apify-client on npm) uses the same Actor id and the same input object. You can also start the run with a plain HTTP POST to the Apify API if you prefer.

Sample output

Here is a shortened example of one dataset record (field values are illustrative of the schema, taken from a real sample run shape):

{ "sourceType": "profile", "source": "bsky.app", "url": "https://bsky.app/profile/bsky.app/post/3n22yg6lg2k2f", "uri": "at://did:plc:z72i7hdynmk6r22z27h6tvur/app.bsky.feed.post/3n22yg6lg2k2f", "text": "Rolling out now: a new notifications screen.\n\nFilter by type (replies, follows, post alerts) or see only people you follow. Similar notifications are now grouped, so there’s less n…", "createdAt": "2026-11-11T22:19:56.200Z", "indexedAt": "2026-11-11T22:20:13.482Z", "languages": [ "en" ], "authorHandle": "bsky.app", "authorName": "Bluesky", "authorDid": "did:plc:z72i7hdynmk6r22z27h6tvur", "authorAvatar": "https://cdn.bsky.app/img/avatar/plain/did:plc:z72i7hdynmk6r22z27h6tvur/bafkreihwihm6kpd6zuwhhlro75p5qks5qtrcu55jp3gddbfjsieiv7wuka", "likeCount": 2007, "repostCount": 357, "replyCount": 172, "quoteCount": 126, "bookmarkCount": 134, "isReply": false, "replyToUri": null, "isRepost": false, "repostedBy": null, "hashtags": [], "mentions": [], "links": [], "images": [ { "url": "https://cdn.bsky.app/img/feed_fullsize/plain/did:plc:z72i7hdynmk6r22z27h6tvur/bafkreidzepcnqoulesvkdth6qfayrmwc4ovirli27ervs72r4msrvlxnu4", "alt": "Screenshots from the redesigned notifications, showing the \"all\" tab and the \"follows\" tab. Four users have liked a post that says, \"delivered a pizza in 29 minutes. do not ask abo…" } ], "video": null, "externalLink": null, "quotedPostUrl": null, "labels": [], "scrapedAt": "2026-11-12T22:33:41.380Z" } 

Once the run has finished, open the dataset in the Console and use Export > CSV if a spreadsheet is your destination. JSON is usually better for code and for language models.

What to use the data for

Community managers listen for product or brand mentions. Researchers sample discourse around a topic or hashtag. Journalists archive a public figure's posts. Marketers study which posts in a niche get quotes and link cards. A scheduled search with a since date is a simple daily digest.

Pricing

Pay-per-result pricing starts at $0.60 per 1,000 posts on the Apify Free plan, with lower unit prices on paid Apify plans, plus a small per-run start fee. Always check the live pricing on the Actor page, because plans and unit prices can change. For a first test, keep the input tiny so you can inspect the schema before you scale up.

Scheduling and automations

In the Apify Console you can schedule the Actor (daily or hourly) and leave the same input in place. For incremental jobs, prefer a "since" or "posted after" style filter when the Actor offers one, so you are not paying to re-collect old rows. When a run finishes you can send a webhook, or connect the Actor in Zapier, Make or n8n. AI agents can discover and call veenkes/veenkes-bluesky-posts through Apify's MCP server using the same input.

Good practices and limits

Only public posts are in scope. Respect authors' copyright and Bluesky's terms, and be careful with personal data in post text or profiles. The Actor is not affiliated with Bluesky.

If a run returns fewer rows than you expected, check the input caps, language or country filters, and the Actor log. A zero-row run is usually a filter or an unavailable source, not a silent crash — read the log before you increase limits.

Next step

Open the Actor and run a small job: Bluesky Post Scraper: Search Posts & Profile Feeds.

If you later want this on a schedule, save the input that worked, add a date filter where it applies, and export CSV automatically from the dataset or from the API snippet above.