Bluesky Followers & Following Scraper

Export public Bluesky followers or following accounts as individual profile records. Bluesky Followers & Following Scraper accepts complete handles, profile links or account identifiers and returns handles, names, biographies, avatar links and available profile metadata.

Keep the source account and direction on every row for audience research, community mapping and comparisons across selected profiles. Choose one direction per run and set a page budget for each input.

At a glance	Details
📥 Input	Add complete Bluesky handles, @handles, DIDs, or canonical https://bsky.app/profile/handle URLs. Choose followers or following in Mode.
📤 Output	One unique related profile
📄 Pagination	Up to 30 source items per requested page
🔐 Login required	No
⚡ Processing	Up to 5 HTTP requests concurrently; up to 5 attempts for temporary failures
💾 Delivery	One Apify dataset view with individual result rows, flattened object columns and complete nested JSON

What the Bluesky followers scraper collects 👥

The Actor collects the public follower or following list for each supplied account. Each result combines one returned account with the source profile and selected direction, preserving the relationship for later analysis.

Data can include:

• Account DID, handle, display name and canonical profile link
• Biography, avatar, banner and pronouns when the list response exposes them
• Creation and indexing dates, profile counts and verification states when present
• Source profile DID, handle and URL
• Selected followers or following mode on each success row

Mode	Input	Result	Best for
followers	A profile	Accounts following the source	Audience analysis
following	A profile	Accounts the source follows	Community and interest mapping

How to collect followers and following from Bluesky 🚀

1. Enter one or more supported inputs.
2. Choose a mode if available and set the page count for each input.
3. Start the Actor.
4. Open the Profiles dataset view and review individual result rows.
5. Export the dataset or retrieve it from your application.

{
  "inputList": [
    "bsky.app"
  ],
  "mode": "followers",
  "pagesPerProfile": 1
}

pagesPerProfile counts relationship-list pages separately for each source account. Each page requests up to 30 accounts. Choose followers or following for the entire run; use two runs when you need both directions.

Bluesky followers and following output fields 📦

Field	Type	Meaning
input	string	Original submitted input, retained on success and failure.
status	string	success or failed.
did	string or null	Stable Bluesky account identifier.
handle	string or null	Current complete account handle.
display_name	string or null	Display name returned by the source.
profile_url	string or null	Canonical account profile URL.
description	string or null	Public biography or collection description, according to row type.
avatar_url	string or null	Profile or feed avatar URL.
banner_url	string or null	Profile banner URL when exposed.
pronouns	string or null	Profile pronouns when exposed.
created_at	string or null	Creation or publication time returned by the source.
indexed_at	string or null	Time the source indexed the record.
followers_count	integer or null	Profile follower count when present in this response.
following_count	integer or null	Profile following count when present in this response.
posts_count	integer or null	Profile post count when present in this response.
verified_status	string or null	Source verification state, when supplied.
trusted_verifier_status	string or null	Source trusted-verifier state, when supplied.
labels	array or null	Source label values.
mode	string or null	Selected collection mode.
source_profile_did	string or null	Identifier of the requested source profile.
source_profile_handle	string or null	Resolved handle of the requested source profile.
source_profile_url	string or null	Canonical URL of the requested source profile.

The successful examples below use normalized public response data. Values are snapshots rather than promises of current content or counts; every top-level output key is included.

Complete representative successful result:

{
  "input": "bsky.app",
  "status": "success",
  "mode": "followers",
  "source_profile_did": "did:plc:z72i7hdynmk6r22z27h6tvur",
  "source_profile_handle": "bsky.app",
  "source_profile_url": "https://bsky.app/profile/did:plc:z72i7hdynmk6r22z27h6tvur",
  "did": "did:plc:sdo6kumfbnroeho6zllkzc2z",
  "handle": "handle.invalid",
  "profile_url": "https://bsky.app/profile/did:plc:sdo6kumfbnroeho6zllkzc2z",
  "labels": [],
  "verified_status": null,
  "trusted_verifier_status": null,
  "display_name": "Dev Test Account",
  "description": null,
  "avatar_url": "https://cdn.bsky.app/img/avatar/plain/did:plc:sdo6kumfbnroeho6zllkzc2z/bafkreidlettqkts2ru3b7wscewep5mbkxjfppdrqbhyfgcqgbrk2zdfrvi",
  "banner_url": null,
  "pronouns": null,
  "created_at": "2025-12-22T12:18:03.125Z",
  "indexed_at": "2025-12-22T12:18:03.125Z",
  "followers_count": null,
  "following_count": null,
  "posts_count": null
}

Complete failed dataset item:

{
  "input": "   ",
  "status": "failed",
  "did": null,
  "handle": null,
  "display_name": null,
  "profile_url": null,
  "description": null,
  "avatar_url": null,
  "banner_url": null,
  "pronouns": null,
  "created_at": null,
  "indexed_at": null,
  "followers_count": null,
  "following_count": null,
  "posts_count": null,
  "verified_status": null,
  "trusted_verifier_status": null,
  "labels": null,
  "mode": null,
  "source_profile_did": null,
  "source_profile_handle": null,
  "source_profile_url": null
}

Each failed row preserves input, uses status: failed, and sets every other top-level field to null. The reason is written to the run log. Successful rows may contain null optional fields or empty arrays when the source does not supply a value. The dataset is not split into separate tables for media, authors, modes or failures.

Input and pagination settings ⚙️

Parameter	Type	Required	Default	Rules
inputList	array of strings	Yes	None	Add complete Bluesky handles, @handles, DIDs, or canonical https://bsky.app/profile/handle URLs. Choose followers or following in Mode.
mode	string	No	followers	Choose the source results to collect. Each mode uses the same single dataset view. Allowed: followers, following.
pagesPerProfile	integer	No	1	Number of result pages to attempt per input. Each page requests up to 30 items; actual public rows can be fewer. Bootstrap requests do not count as pages. Stops when the cursor ends or repeats. Minimum 1.

Accept complete handles such as bsky.app and @pfrazee.com, supported did:plc: or did:web: identifiers, or canonical HTTPS profile URLs. A post URL, bare local username or search phrase is not an account input.

For supported website URLs, use the exact https://bsky.app host and canonical path without a query string or fragment. URLs from other hosts and unsupported record types are rejected. Handles are normalized; duplicate normalized inputs in the same mode are processed once. Different source inputs retain their own results, while repeated record identifiers within one input’s pagination are removed.

The first result request counts as page 1; resolving a handle or validating source metadata does not consume a result page. Pagination stops at the requested page count, a missing cursor or a repeated cursor. A short, empty or fully filtered page can still continue when it includes a usable next cursor. No exact result total is guaranteed.

Bluesky followers and following use cases 🎯

Audience overlap research

Collect follower rows for selected public accounts and compare returned DIDs in your own analysis. Preserve source-profile fields when calculating overlap.

Community mapping

Collect following lists to create directed source-to-account edges. Combine successive exports when studying how selected account networks change.

Profile discovery and qualification

Review handles, biographies and profile URLs in a spreadsheet before deciding which accounts deserve closer research. The Actor does not send messages or follow accounts.

Pricing and saved-result behavior 💰

See the Actor’s Pricing tab for the active charging model and current rate. Store settings are separate from this local implementation, so this README does not state an unverified fixed price or runtime.

Under dataset-item pricing:

• Every unique record saved as success is one result for that source input. Nested author, media or profile fields do not become separate rows.
• An invalid or unavailable input, an exhausted temporary failure, or an input with no publicly available results within its page budget can save one failed row.
• Automatic retry attempts do not create extra dataset rows by themselves.
• A normal empty continuation after earlier successes creates no extra result row.
• More requested pages can produce more saved rows. Check the active listing for how saved failed rows are billed; they are not assumed to be free.

The final total depends on source availability, duplicate removal and the chosen page budget. Start with a small run and check its actual usage before selecting a larger budget.

Bluesky followers and following API 🔌

Replace $ACTOR_ID with the identifier from this Actor’s API tab and $APIFY_TOKEN with your Apify token.

curl -X POST "https://api.apify.com/v2/acts/$ACTOR_ID/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"inputList":["bsky.app"],"mode":"followers","pagesPerProfile":1}'

Retrieve the default dataset through the Apify API or download JSON, CSV, Excel, XML and other formats available in the Console. Schedules, completion webhooks and Apify integrations can connect results to Google Sheets, Make, Zapier, n8n, cloud storage or your own backend. These are platform connection options, not integrations preconfigured by this Actor.

Reliability, retries, and public-data limits ⚠️

The Actor uses pure HTTP collection with up to five requests concurrently. It does not launch a browser. Invalid syntax and confirmed missing, removed or inaccessible targets stop without unnecessary retries. Temporary network and proxy failures, timeouts, blocks, malformed responses, throttling and server errors are retried up to five total attempts.

Earlier successful pages remain saved if a later page fails. If no publicly available rows are found before the source ends or the selected page budget is reached, one failed row records that input; this does not mean the underlying account or collection necessarily does not exist. A later empty page after successes is normal exhaustion. A later request that exhausts retries can append a failed row while preserving earlier results.

Bluesky controls public availability and returned fields. Objects restricted from unauthenticated viewing are excluded; a restricted target produces a failed row. Deleted, suspended, unavailable or otherwise restricted records may be missing. Optional counts are not inferred from an incomplete sample, and media links may change or expire.

The Actor returns profile fields already exposed by the relationship list; it does not request a separate detailed profile for every returned account. Optional counts, banners or pronouns can therefore remain null. A collected follow relationship does not indicate a real-world endorsement.

Three consecutive result pages were verified for every paginated mode in HTTP runs of the packaged Actor on September 11, 2026. These checks demonstrate working continuation on the tested sources and do not guarantee future source availability.

One invalid string inside an otherwise valid input list does not stop other inputs. A configuration that fails the input schema logs an input warning and exits without starting requests: for example, a list containing a number instead of a string, an unsupported mode or an invalid page-count type. Infrastructure failures such as startup errors, unavailable dataset storage or an unrecoverable result-save error can still stop the whole run. Result-save failures are not retried as fresh scraping requests.

Frequently asked questions ❓

Can one run collect both directions?

Each run has one mode. Run once with followers and once with following if you need both lists.

Are profile follower counts always included?

No. Returned list profiles may omit counts or other optional detail fields. The Actor does not make a separate enrichment request for each account.

Is the same person removed across different source profiles?

Deduplication applies within each input’s pagination. An account found for two different source profiles remains a separate relationship for each source.

Does it require Bluesky login or cookies?

No Bluesky login, password, session cookie or account token is accepted or required. The Actor uses HTTP requests used by the public website and respects restrictions on unauthenticated access.

What happens to invalid or unavailable inputs?

Invalid individual inputs are saved as failed rows without an HTTP request. Confirmed missing, removed or restricted targets also become failed rows without unnecessary retries. Temporary failures are retried up to five total attempts. Other inputs and already saved pages remain available.

Can I export results or automate collection?

Yes. Use the Apify dataset to download JSON, CSV, Excel, XML or other supported formats, or retrieve records through its API. Apify schedules and webhooks can connect repeated runs to your own workflow.

Support, responsible use, and related actors 🛟

For a reproducible problem, open an issue in the Actor’s Issues tab. Include the run ID, approximate time, mode if relevant, page count, safe public input, expected result and actual result. Do not share access tokens, proxy credentials or other secrets.

Use public data responsibly and follow applicable privacy, copyright, contractual and platform requirements before storing, combining or redistributing collected information.