How much does Lemmy Scraper cost?

$0.0015 per post — $1.5 per 1,000. Billing is pay-per-result on your own Apify account: no subscription, and a run that returns nothing costs nothing.

What do I need to provide to run Lemmy Scraper?

Nothing is mandatory — every field has a working default. The settings you will usually change are Lemmy instance, Mode, Query (community name or search term), Sort, Max posts.

Do I need to code to use Lemmy Scraper?

No. It is a ready-to-run cloud tool: open it on Apify, fill in the form, click Run, and download the results. Everything runs on Apify's servers, so there is nothing to install or host.

Lemmy Scraper

Q: What data does Lemmy Scraper return?

A structured dataset with 14 fields per record, including author, authorActor, body, comments, community, communityTitle, downvotes, id, nsfw, postUrl, published, score. Export it as JSON, CSV or Excel, or send it straight to your app, a database or an AI agent.

Scrape public Lemmy posts from any instance by feed, community, or keyword. Get title, author, score, comments and more as JSON. No login needed.

5 from 1 review on Apify 64 runs on Apify $0.0015 per post ($1.5 / 1,000)

Run this in the cloudRun on Apify →

Social Media Scrapers

How it works

1
Open it on Apify
Hit Run on Apify — it opens the tool in the cloud, no install.
2
Set the inputs
Adjust instance, mode, query (sensible defaults are pre-filled).
3
Click Run
The tool runs on Apify’s cloud and collects the data for you.
4
Export the results
Download as JSON, CSV or Excel, or pipe straight into your app, Google Sheets, or an AI agent.

Pricing

$0.0015 per post = $1.5 per 1,000

You are charged for	When	Price
Post returned	Charged per post returned.	$0.0015

Pay-per-event pricing: you are billed per result, not per subscription — a run that returns nothing costs nothing beyond the start fee. Billing is handled by Apify on your own account. These are the live Apify store prices, in effect since 2026-06-13, and they are what you are actually charged.

Inputs

Field	What it does	Type
`instance`	The Lemmy instance host to scrape (bare domain, no https://). Examples: lemmy.world, lemmy.ml, beehaw.org, sh.itjust.works.	string
`mode`	What to scrape: "feed" = the instance front-page feed; "community" = a single community (put its name in Query); "search" = search posts by keyword (put the term in Query).	string
`query`	For mode "community": the community name, e.g. "technology" or "technology@lemmy.world". For mode "search": the keywords to search for, e.g. "linux". Ignored in mode "feed".	string
`sort`	How to sort posts. Hot/Active rank by recent engagement; New is chronological; the Top* options rank by score within a time window.	string
`maxItems`	Maximum number of posts to return. The actor paginates (50 per request) until it reaches this many or runs out of posts.	integer
`notionConnector`	Optional. Write each post as a page into your Notion when the run finishes. Authorize a Notion connector once in Settings → API & Integrations → MCP connectors, then pick it here. Leave empty to skip (default) — results are always saved to the dataset regardless.	string
`notionParentId`	Optional. The Notion data source ID of the database to write into (only used if a Notion connector is set). Leave empty to create the pages privately in your workspace instead.	string

What you get

A structured dataset — each result includes fields like:

authorauthorActorbodycommentscommunitycommunityTitledownvotesidnsfwpostUrlpublishedscorethumbnailtitle

Export every run as JSON, CSV or Excel, or send it to your app, a database, Google Sheets, or an AI agent.

2 ready-to-run use cases

Scrape lemmy.world Front Page: Hot Posts + Scores

The hottest lemmy.world front-page posts as structured data: title, link, author, score, and comment count. Sort by Hot, New, or Top, no login needed.

Lemmy Keyword Search: Find Posts on Any Topic

Track a brand or topic on Lemmy by pulling every post that mentions your keyword across lemmy.world, sorted newest first, with author and score.

Related tools in Social Media Scrapers

Other ready-to-run tools in the same category — all pay-per-use on the Apify cloud.

Social Media Scrapers

Reddit Text Cleaner — TTS-Ready Narration

Turn raw Reddit posts into TTS-ready narration. Strips markdown, links and edit stamps, expands AITA/MIL/TIFU, splits into sentences. No AI, instant.

2 use cases

Social Media Scrapers

TikTok Comments Scraper

TikTok comments scraper at $0.25 per 1,000 with no run-start fee. Text, likes, reply counts, authors and timestamps including replies. No login or key.

Ready to run — no setup

Social Media Scrapers

TikTok Hashtag Scraper

Scrape any TikTok hashtag for videos, views, likes, comments, shares and author data. No login or API key. $0.25 per 1,000 videos.

Ready to run — no setup

Social Media Scrapers

TikTok Sound Scraper

Scrape every TikTok video using a sound: views, likes, comments, shares, author and music data. $0.25 per 1,000 videos, flat at every volume.

Ready to run — no setup

Social Media Scrapers

TikTok Followers & Following Scraper

Extract any TikTok account's public followers or following list with bios, avatars, regions, verified badges and counts.

Ready to run — no setup

Social Media Scrapers

Instagram Comments Scraper

Scrape Instagram post and reel comments at $0.40 per 1,000, flat at every volume, plus a $0.001 run start. Text, likes, replies, author, verified badge.

5 use cases

See all Social Media Scrapers →

Where this tool sits

Categories: Social Media Scrapers
Platforms: Lemmy

Lemmy Scraper

Scrape public posts from any Lemmy instance — the federated, Reddit-style link aggregator. Browse an instance's front-page feed, pull a single community, or search by keyword. No account, no API key, no login.

Uses the public Lemmy v3 REST API, so reads are fast and clean (structured JSON, not HTML scraping).

Modes

Feed — the instance front page (/api/v3/post/list). Just set instance and sort.
Community — one community's posts. Set mode: "community" and put the community name in query (e.g. technology, or cross-instance technology@lemmy.world).
Search — search posts by keyword. Set mode: "search" and put the term in query (e.g. linux).

What you get per post

id, title, url (the external link the post points to, if any), body (post text; markdown, with stray HTML stripped), author, authorActor (the creator's federated actor URL), community, communityTitle, score, comments, upvotes, downvotes, nsfw, thumbnail, published (ISO), and postUrl (the permalink on the instance, e.g. https://lemmy.world/post/123).

Fields that can be null

url / thumbnail — many posts are pure text discussions with no external link or image.
body — link posts often have no body text.
Any field Lemmy omits for a given post comes back null rather than being dropped.

Input

Field	Notes
`instance`	Lemmy instance host (bare domain). Default `lemmy.world`.
`mode`	`feed`, `community`, or `search`. Default `feed`.
`query`	Community name (community mode) or search term (search mode).
`sort`	`Hot`, `Active`, `New`, `TopDay`, `TopWeek`, `TopMonth`, `TopAll`. Default `Hot`.
`maxItems`	Max posts to return (paginated 50 at a time). Default 100.

Pricing

$1.50 per 1,000 posts ($0.0015 each), with no run-start fee. Flat rate — no volume tiers, no plan gates — and you are charged only for posts actually returned. A run that finds nothing costs nothing.

Output

One dataset row per post, deduped by post id. You are only charged for genuine post rows (ok: true). Rows we couldn't deliver are never charged:

invalid input — a single ok: false diagnostic row with errorCode: "BAD_INPUT" (bad instance, bad mode, or a missing community name / search term),
no posts for this feed/community/search (NO_RESULTS),
a missing community or non-Lemmy host (NOT_FOUND),
rate limits or network errors (RATE_LIMITED / NETWORK).

Proxy

The Lemmy v3 REST API is public and has no anti-bot, so no proxy is required and the default runs without one (saving proxy credits). Only enable Apify Proxy if an instance rate-limits your IP at very high volume.

Troubleshooting

NOT_FOUND in community mode? Check the community name. If it lives on another instance, use the cross-instance form name@otherinstance.tld, or set instance to that instance directly.
NO_RESULTS? The feed/community/search genuinely returned nothing on this instance — try a different sort, a broader search term, or a larger instance.
BAD_INPUT? community and search modes both require query. instance must be a bare Lemmy domain like lemmy.world.

Example

{ "instance": "lemmy.world", "mode": "community", "query": "technology", "sort": "Hot", "maxItems": 50 }

Notes

Lemmy is federated: a large instance like lemmy.world also relays content from communities hosted elsewhere. The postUrl permalink points to the instance you scraped; authorActor and the community's federated identity tell you where the content originates.