# Bluesky Scraper (Profiles, Posts, Followers, Feeds) (`scrapyx/bluesky-scraper`) Actor

Scrape Bluesky (AT Protocol) with no login and no API key. Full profiles, a user's post timeline with engagement counts, followers and following, account search, a post's full reply thread, the accounts that liked/reposted/quoted a post, and every post in a custom feed or curated list.

- **URL**: https://apify.com/scrapyx/bluesky-scraper.md
- **Developed by:** [Ibnu Adzim](https://apify.com/scrapyx) (community)
- **Categories:** Social media, Marketing, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.10 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Bluesky Scraper (Profiles, Posts, Followers, Feeds)

Scrape **[Bluesky](https://bsky.app)** / the AT Protocol with **no login and
no API key**. This Actor only calls methods the public AppView
(`public.api.bsky.app`) serves to anonymous clients — every other Bluesky
scraper on the Store signs in with an app password.

- **Profiles** — full profile for each handle / DID (follower & post counts,
  bio, avatar, verification, list/feed counts, pinned post)
- **Author posts** — a user's timeline with per-post engagement counts, embeds,
  links, hashtags, reply refs
- **Followers / Following** — the follow graph for each account
- **Search users** — `searchActors` for each query
- **Thread** — a post plus its full reply tree, flattened with a depth column
- **Post engagement** — the accounts that liked or reposted a post, or the
  posts that quoted it
- **Feed** — every post in a custom feed generator *or* a curated list
  (auto-detected)

| Record type | One per | Carries |
| --- | --- | --- |
| `SEARCH_SUMMARY` | work unit (account / query / post / feed) | `rowsReturned`, `requestsMade`, `truncated`, context (`subject` / `query` / `rootUri` / `feedUri` …) |
| `PROFILE` | account | `did`, `handle`, `displayName`, `description`, counts, `verifiedStatus`, `labels`, `profileUrl`, `relation` (`self` / `follower` / `follows` / `search-result` / `reposted-by` / `liked-by`) |
| `POST` | post | `uri`, `rkey`, `author`, `text`, `langs`, `likeCount` / `repostCount` / `replyCount` / `quoteCount` / `bookmarkCount`, `isReply` + reply refs, `embedType` + images / external link / quoted post, `facetLinks`, `hashtags`, `feedReason`, `postUrl` |
| `ERROR` | bad input / missing account or post | `_error` + `_errorDetail` |

Every `PROFILE` / `POST` row keeps the verbatim AppView object in `raw` (turn
off with `slimOutput`).

### Inputs by mode

| Mode | Needs | |
| --- | --- | --- |
| `profiles` | `identifiers` | handles, DIDs or profile URLs; batched 25 per request |
| `author-posts` | `identifiers` | `feedFilter` (validated — see below) |
| `followers` / `following` | `identifiers` | `maxItems` per account |
| `search-users` | `searchQueries` | `maxItems` per query |
| `thread` | `postUris` | post URLs or `at://` URIs; `threadDepth`, `threadParentHeight` |
| `post-engagement` | `postUris` | `engagementType` = `likes` / `reposts` / `quotes` |
| `feed` | `feedUris` | feed-generator or list URLs / URIs |

### Things the AppView will mislead you about

Each is measured, and each has a scenario in
`tests/smoke/bluesky-scraper_traps.sh` (14/14 passing).

**Full-text post search (`searchPosts`) is NOT available to anonymous
clients.** It returns a `403` HTML block page, not an XRPC error, on every
endpoint and TLS profile. Post discovery here is via `author-posts` (a user's
timeline) and `feed` (any custom feed or list) — both work unauthenticated.

**An unknown `feedFilter` is SILENTLY IGNORED** by Bluesky (HTTP 200, default
feed). This Actor rejects an unknown value before spending a request.

**A missing account is `400` `{"error":"InvalidRequest","message":"Profile
not found"}`; a missing post is `400` `{"error":"NotFound","message":"Post
not found: <uri>"}`** — a different error *name* at the *same* status. Both
become `not_found` rows.

**`getFollowers` / `getFollows` silently drop tombstoned accounts**, so a
request for 100 can return ~90 — the Actor keeps paging on the cursor until it
has `maxItems` or the feed ends (which is why a large follower pull takes more
requests than `ceil(maxItems / 100)`).

**Counts live on the post, text lives on `post.record`.** `limit` caps at 100;
`getProfiles` / `getPosts` batch at 25. A feed item is a `{post, reason?}`
wrapper — a repost is recorded as `feedReason: repost` with `feedReasonBy`.

### Notes on cost

One request per 25 profiles; one request per 100 rows for the paged modes
(more when tombstones shrink pages); one request per thread. No proxy needed —
the public AppView has no anti-bot layer.

# Actor input Schema

## `mode` (type: `string`):

`profiles` = full profile per handle/DID. `author-posts` = a user's post timeline. `followers` / `following` = the follow graph. `search-users` = find accounts by query. `thread` = a post + its replies. `post-engagement` = who liked/reposted/quoted a post. `feed` = every post in a custom feed or list.

## `identifiers` (type: `array`):

`profiles`, `author-posts`, `followers`, `following`. One per line: a handle (`bsky.app`, `@jay.bsky.team`), a DID (`did:plc:...`), or a profile URL (`https://bsky.app/profile/bsky.app`).

## `searchQueries` (type: `array`):

`search-users` mode. One query per line — matched against handle, display name and bio.

## `postUris` (type: `array`):

`thread` and `post-engagement` modes. One per line: a post URL (`https://bsky.app/profile/<handle>/post/<rkey>`) or an AT-URI (`at://did:plc:.../app.bsky.feed.post/<rkey>`).

## `feedUris` (type: `array`):

`feed` mode. One per line: a custom feed URL (`https://bsky.app/profile/<handle>/feed/<rkey>`), a list URL (`.../lists/<rkey>`), or the equivalent `at://` URI. Feed generators and curated lists are auto-detected.

## `feedFilter` (type: `string`):

`author-posts` mode. An unknown value is SILENTLY IGNORED by Bluesky, so it is checked here. `posts_with_replies` (default), `posts_no_replies`, `posts_with_media`, `posts_and_author_threads`.

## `engagementType` (type: `string`):

`post-engagement` mode. `likes` / `reposts` return the accounts; `quotes` returns the quoting posts.

## `threadDepth` (type: `integer`):

`thread` mode. How many reply levels below the target post to fetch (0-20).

## `threadParentHeight` (type: `integer`):

`thread` mode. How many ancestor posts above the target to include (0-20).

## `maxItems` (type: `integer`):

Cap on rows per work unit (per account, query, post or feed) — followers, posts, likes, etc. `profiles` mode ignores it. Default 1000.

## `slimOutput` (type: `boolean`):

By default every PROFILE / POST row carries the verbatim AppView object in `raw`. Turn on to emit only the normalised fields.

## `maxConcurrency` (type: `integer`):

Parallel in-flight requests across work units.

## `minRequestInterval` (type: `number`):

Politeness pacing. The public AppView is generous (~10/s here by default).

## `proxyConfiguration` (type: `object`):

Optional. The public AppView has no anti-bot layer, so a proxy is OFF by default.

## Actor input object example

```json
{
  "mode": "profiles",
  "identifiers": [
    "bsky.app"
  ],
  "feedFilter": "posts_with_replies",
  "engagementType": "likes",
  "threadDepth": 6,
  "threadParentHeight": 0,
  "maxItems": 1000,
  "slimOutput": false,
  "maxConcurrency": 4,
  "minRequestInterval": 0.1,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `items` (type: `string`):

One row per scraped record. See the dataset's default view for field definitions.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "identifiers": [
        "bsky.app"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapyx/bluesky-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "identifiers": ["bsky.app"] }

# Run the Actor and wait for it to finish
run = client.actor("scrapyx/bluesky-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "identifiers": [
    "bsky.app"
  ]
}' |
apify call scrapyx/bluesky-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapyx/bluesky-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/EIevo30ptE3eEtbRW/builds/kck1wMnzSTa3R3SiX/openapi.json