Resolve any public Bluesky handle or post into structured JSON — profile bio and follower stats, post text, full thread context, reposts, likes, and reply counts.
Bluesky is a decentralized microblogging network built on the AT Protocol, where handles map to domains and posts thread together across the open firehose. The Bluesky Scraper API resolves public profiles and posts, reconstructs reply threads, and returns each record with stable URIs so you can join data over time.
Researchers tracking the migration of conversation away from legacy platforms use it to measure how communities form on the open social web. We capture public data only and normalize follower counts, engagement, and thread structure into the same schema we use for X and Threads.
# POST a target — get validated JSON back
curl https://api.crawlzo.com/v4/scrape \
-H "Authorization: Bearer $CRAWLZO_KEY" \
-d '{
"url": "https://www.bluesky.com/",
"type": "profile",
"include": "recent_posts"
}'
// ← response
{
"status": "ok",
"data": {
"username": "...",
"followers": 1840221,
"posts": 412,
"verified": true,
"recent_posts": [
{ "id": "…", "likes": 21044, "comments": 882 }
]
}
}Bluesky data parsed into clean, validated JSON. Pull any group below on its own, or combine them in a single request.
Decentralized social network research
Cross-platform conversation tracking
Creator growth and audience analysis
Thread and reply-graph mining
Pass either a handle or a post URI and we resolve it to the underlying public record, returning the stable DID and URI alongside the human-readable handle so your data stays joinable even if a handle changes.
Structured JSON straight from the API, or pushed to your stack natively — S3, BigQuery, Snowflake, Postgres, Kafka, or any HTTPS webhook. Call it from Python, Node, Go, Rust, or any HTTP client. The data lands where your pipeline already lives.
No. You pay for valid, schema-passing rows only. Retries, blocks, CAPTCHAs, and 5xxs are on us. If a run doesn't return data that conforms to the schema, it isn't billed.
Every request routes through the same engine behind our Web Unblocker API: compliant residential IPs, real browser fingerprints, TLS-level evasion, behaviour modelling, and built-in CAPTCHA solving. Hard targets become routine.
Yes. We respect robots policies, rate budgets, and ToS-aware allow/deny lists. We deliver and move on — no row-level retention beyond your replay window. GDPR DPA, PII redaction, and custom data residency available on request.