Lemmy Posts Scraper avatar

Lemmy Posts Scraper

Pricing

from $2.99 / 1,000 results

Go to Apify Store
Lemmy Posts Scraper

Lemmy Posts Scraper

Collect public Lemmy posts from any instance by sort or community. Gather post titles, timestamps, creators, scores, and comment counts into clean datasets.

Pricing

from $2.99 / 1,000 results

Rating

0.0

(0)

Developer

B2B Lead Generation

B2B Lead Generation

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Categories

Security

Limited permissions

Share

Lemmy Posts Scraper cover

Collect public posts from Lemmy communities and instances. Choose an instance, select a sorting method, optionally filter by community, and retrieve structured post information for research, monitoring, and analysis. Export results in JSON, CSV, Excel, or other supported Apify dataset formats.

What It Does

This actor retrieves public post listings from Lemmy instances. It collects post titles, ActivityPub identifiers, publication dates, community names, creator information, scores, and comment counts.

The actor uses cursor-based pagination with limit and page_cursor, removes duplicate posts using their IDs, and stops when the configured maxItems limit is reached.

Key Features

  • Collect public posts from different Lemmy instances.
  • Retrieve posts using multiple sorting options.
  • Filter results by community name.
  • Collect post metadata and engagement information.
  • Automatically paginate through available results.
  • Remove duplicate posts using post IDs.
  • Configure request delays and timeout settings.
  • Export results in multiple formats.

Input Example

{
"instance": "lemmy.world",
"sort": "Hot",
"maxItems": 50,
"requestDelayMs": 1000
}

Input Parameters

FieldTypeDefaultDescription
instancestringlemmy.worldLemmy instance hostname without a scheme
sortstringHotSorting method, such as Hot, New, or TopDay
communityNamestringEmptyOptional community name filter
maxItemsinteger100Maximum successful records per run; hard maximum is 1,000
requestDelayMsinteger1000Delay between requests in milliseconds
userAgentstringActorResearch/1.0User-Agent header used for requests
timeoutSecsinteger300Overall actor run timeout in seconds
requestTimeoutSecsinteger30Timeout for an individual request in seconds
proxyConfigurationobjectProxy offOptional proxy configuration

Output Example

{
"postId": 53019480,
"name": "Chronic rule",
"ap_id": "https://lemmy.world/post/53019480",
"published": "2026-10-12T04:45:48.054379Z",
"community": "onehundredninetysix",
"creator": "ickplant",
"score": 17,
"comments": 1,
"scrapedAt": "2026-10-12T05:30:00+00:00"
}

Output Fields

FieldDescription
postIdUnique Lemmy post identifier
namePost title
ap_idActivityPub identifier for the post
publishedPost publication timestamp
communityCommunity where the post was published
creatorUsername of the post creator
scorePost score
commentsNumber of comments
scrapedAtTimestamp when the record was collected

The dataset overview highlights post ID, title, ActivityPub ID, publication date, community, creator, score, and comment count.

Use Cases

  • Feed Monitoring: Track Hot, New, or other sorted posts from a Lemmy instance.
  • Community Research: Collect posts from specific communities for analysis.
  • Engagement Analysis: Examine post scores and comment counts.
  • Content Research: Explore publicly available discussions and trending topics.
  • Data Export: Build structured Lemmy post datasets for spreadsheets and downstream tools.
  • Sort Comparisons: Compare Hot, New, and TopDay results to explore different post collections.

Limits and Responsible Collection

  • Keep request frequency around one request per second.
  • Increase requestDelayMs if the instance returns HTTP 429 responses.
  • Respect individual instance policies and applicable rate limits.
  • Consider copyright and privacy requirements before reusing user-generated content.

Frequently Asked Questions

What does this actor collect?

It collects public Lemmy post metadata, including titles, post IDs, publication dates, communities, creators, scores, and comment counts.

Can I collect posts from different Lemmy instances?

Yes. Set the instance input to the hostname of the Lemmy instance you want to collect from, such as lemmy.world.

Can I filter posts by community?

Yes. Provide a community name using communityName to collect posts from a specific community.

Which sorting options are supported?

The actor supports Lemmy sorting methods such as Hot, New, and TopDay.

How many posts can one run collect?

The maximum is 1,000 successful records per run. Use maxItems to configure a smaller collection limit.

How does pagination work?

The actor retrieves posts in batches using limit and page_cursor, removes duplicate post IDs, and continues until the item limit is reached or no more results are available.

What happens when a page request fails?

The actor continues processing and stores an error record instead of stopping the entire run.

What export formats are supported?

You can export results as JSON, CSV, Excel, and other formats supported by Apify datasets.

Can I schedule recurring collections?

Yes. Configure an Apify schedule to automatically collect updated Lemmy posts at your preferred interval.

Trademark Notice

Lemmy and related names, logos, and trademarks belong to their respective owners. They are referenced only to identify the source of the collected post information. This actor is not affiliated with or endorsed by the Lemmy project or any individual Lemmy instance.

Disclaimer

This actor is an independent data collection tool. Post availability, content, and engagement information depend on the selected Lemmy instance. Users are responsible for verifying collected information and complying with applicable laws, instance policies, privacy requirements, and content licensing conditions.

This actor collects publicly accessible post information without bypassing login screens, paywalls, or technical security measures. How collected information can be used depends on applicable laws and the source instance's policies.

  • Personal Data: Public posts may contain usernames or other information that identifies individuals. Handle collected data responsibly and comply with applicable privacy laws, including GDPR or CCPA where relevant.
  • Copyright and Licensing: Posts may contain copyrighted user-generated content. Avoid unauthorized reproduction or redistribution and respect applicable content licences.
  • Platform Terms and Rate Limits: Collect responsibly, respect instance policies, and avoid excessive requests.
  • Disclaimer: This information is general guidance, not legal advice. Consult a qualified legal professional if you are unsure about your intended use.

Is web scraping legal?