Mastodon

Collect public posts, trending conversations, hashtag timelines, accounts and hashtags from mastodon.social. Run one query or a list, download structured results, and continue from a saved post ID.

Features

Process	What you get
Get Trends	Public posts currently trending on mastodon.social
Get Statuses by Username	Public posts for an exact username or federated account address, excluding replies
Get Timelines by Tag	Public posts containing a hashtag
Search for Usernames	Matching accounts with profile details and available follower counts
Search for Hashtags	Matching hashtags and their available activity history

Post results include the source's available text, timestamps, links, engagement counts, media references, tags and mentions. Results reflect what mastodon.social knows; they are not an exhaustive archive of every Mastodon server.

Get started

Choose a process, enter one or more keywords, and select the maximum pages per query.

{
  "process": "gt",
  "keywords": ["@Mastodon@mastodon.social", "@Gargron@mastodon.social"],
  "maximum": 2,
  "pause": 1000
}

For hashtag timelines, choose gi and enter tags such as cats or photography. For trends, choose gr; no keyword is needed. Existing inputs using keyword and last_id also work.

Posts and hashtag timelines return up to 40 items per page; trends return up to 20. Account and hashtag searches return up to 11 matches per keyword. The source can return fewer items. Duplicate records across queries are returned once.

Continue from a post ID

Provide last_ids in the same order as keywords to retrieve posts newer than those IDs. Use an empty string or 1 where no starting ID is needed. IDs must be strings to preserve their full precision. RUN_SUMMARY records progress, continuation cursors and any unprocessed queries.

To continue older history, use the returned cursor as the starting ID and select cursorDirection: "older". Without a starting ID, posts are retrieved newest first.

Pricing

See the Pricing tab for the active rate and any scheduled changes. The pay-per-event rate is $0.75 per 1,000 unique results + $0.01 per start, including platform usage. Each unique returned post, account or hashtag is one result. Each valid pay-per-event run with at least one query input includes a shared minimum charge of 100 result units. The minimum also applies when fewer results are returned or no matches are found. Set a maximum run budget of at least $0.09.

If fewer than 100 results are available, clearly marked placeholder rows fill the difference; they contain no scraped data, so filter them out when exporting. Each separate run has its own minimum, including scheduled or API runs. Platform usage is included. Increase your maximum run budget when collecting more than the included minimum. Runs can also stop at time, request or transfer limits; check RUN_SUMMARY to continue an unfinished collection.

Availability and troubleshooting

No Mastodon account is needed for the public features above. Full-text post search requires authentication on mastodon.social and is not available anonymously. The legacy st process is accepted but reports this limitation when no public results are returned.

Direct requests are used by default. You can select an Apify proxy or provide custom proxies. If requests are blocked, the run reports "Try another proxy"; if no usable results were retrieved, it returns labeled placeholders. Missing accounts and empty searches are reported separately. Three consecutive source errors stop further requests.

Private or deleted posts are not available. Mastodon controls result availability and rate limits. For help, open an issue and include the run URL.

Unsuccessful lookups

Where listed in the Pricing tab, a handled lookup problem that prevents a run from returning any real results produces one clear error record and a single $0.02 unsuccessful-lookup fee, in addition to any listed start fee.