Pull any public Mastodon account or post into structured JSON — profile details, toot text and media, boost and favourite counts, plus the instance the content lives on.
Mastodon is a federated microblogging platform made of thousands of independently run instances that share content over ActivityPub. The Mastodon Scraper API handles this fragmentation for you, resolving public accounts and posts on any instance and returning a unified record that includes the home server, so cross-instance data stays comparable.
Open-web researchers and trust-and-safety teams use it to observe how topics spread across the fediverse without standing up their own server. Only public toots and profiles are collected, with boost, favourite, and reply counts normalized into one schema regardless of which instance served them.
# POST a target — get validated JSON back
curl https://api.crawlzo.com/v4/scrape \
-H "Authorization: Bearer $CRAWLZO_KEY" \
-d '{
"url": "https://www.mastodon.com/",
"type": "profile",
"include": "recent_posts"
}'
// ← response
{
"status": "ok",
"data": {
"username": "...",
"followers": 1840221,
"posts": 412,
"verified": true,
"recent_posts": [
{ "id": "…", "likes": 21044, "comments": 882 }
]
}
}Mastodon data parsed into clean, validated JSON. Pull any group below on its own, or combine them in a single request.
Fediverse and ActivityPub research
Cross-instance topic monitoring
Community migration analysis
Public account and engagement tracking
Yes. Pass an account or post URL from any instance and we resolve it on that server, returning the originating instance alongside the content so federated data lands in a single consistent schema.
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.