Indie Hackers Posts Scraper avatar

Indie Hackers Posts Scraper

Pricing

from $2.40 / 1,000 indie hackers posts scrapers

Go to Apify Store
Indie Hackers Posts Scraper

Indie Hackers Posts Scraper

Collect public Indie Hackers posts from the rendered homepage. Return titles, URLs, upvotes/comments, and URL fields when available. Run with maxResults and keywordFilter; no login needed. Pricing: $0.0024/result + $0.00005/Actor Start on Free.

Pricing

from $2.40 / 1,000 indie hackers posts scrapers

Rating

0.0

(0)

Developer

Vitalii Bondarev

Vitalii Bondarev

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

11 days ago

Last modified

Features

Limited permissions

Share

Scrape public Indie Hackers homepage posts, extracting titles, canonical URLs, and available author, engagement, slug, section, and post ID fields. On the Free plan you pay $0.0024 per result ($2.40 per 1,000 results), plus $0.00005 per start event; the default 2048 MB run is charged 2 start events ($0.0001).

  • Collect one post per dataset item.
  • Filter posts by case-insensitive text in the post URL for targeted post research.
  • Extract upvote and comment counts from homepage cards for engagement analysis.
  • Use the public homepage feed without an Indie Hackers login.

What you get

The Actor renders the Indie Hackers homepage in a browser. Each saved dataset item represents one parsed post.

FieldTypeDescription
titlestringPost title shown in the public Indie Hackers feed; a saved item requires a non-empty title.
urlstringCanonical public URL of the post; a saved item requires a valid post URL.
postIdstringPost identifier parsed from the URL; omitted when no post ID is present in the URL.
slugstringPost slug parsed from the URL; omitted when no slug can be parsed.
sectionstringFeed section included in the post URL; omitted when the URL has no section path.
authorstringAuthor name shown with the post; omitted when no author value is available.
upvotesintegerUpvote count displayed on the post card; omitted when no count is available.
commentsintegerComment count displayed on the post card; omitted when no count is available.

Fields with no value are omitted from the item. The comments field is a count; the Actor does not return discussion comments or post-body text.

Sample output

{
"title": "I launched my first Mac app today: a text expander with plain text snippets",
"url": "https://www.indiehackers.com/post/i-launched-my-first-mac-app-today-a-text-expander-with-plain-text-snippets-7ee42de7dd",
"slug": "i-launched-my-first-mac-app-today-a-text-expander-with-plain-text-snippets",
"postId": "7ee42de7dd",
"author": "jeyk333",
"upvotes": 3,
"comments": 18
}

Pricing

This Actor uses pay-per-event billing.

EventUnitFree-plan price
apify-default-dataset-itemOne scraped result with all fields (a result)$0.0024 per event
apify-actor-startOnce per GB of run memory, with a minimum of one event$0.00005 per event

The default run memory is 2048 MB, so a default run is charged 2 start events, $0.0001 in total on the Free plan. If you change the run memory, the number of start events changes with it.

Examples for a default 2048 MB run on the Free plan (results, then 2 start events at $0.00005 each):

  • Free: 100 x $0.0024 = $0.24, plus 2 x $0.00005 = $0.0001, total $0.2401
  • Free: 1,000 x $0.0024 = $2.40, plus 2 x $0.00005 = $0.0001, total $2.4001
  • Free: 10,000 x $0.0024 = $24.00, plus 2 x $0.00005 = $0.0001, total $24.0001

The Apify Free plan's $5 monthly platform usage credit covers 2,083 results at this per-result price.

You pay only for the events listed in the table above. This Actor does not use the Pay per event + usage option, so the platform usage of your runs (compute, proxy traffic and storage) is not billed to you separately.

How to use

  1. Open the Indie Hackers Posts Scraper in Apify and run it from your Apify account. No Indie Hackers login is required.
  2. Set the input fields described in Input parameters; no field is required.
  3. Start the Actor and wait for the run to finish.
  4. Review the dataset items and use the returned title, URL, author, counts, and URL-derived fields.
  5. To repeat the run, use Apify Schedules. Each run is billed on its own, and the Actor does not remove posts it already returned in an earlier run, so repeated runs can bill the same homepage posts again.

Example input:

{
"maxResults": 10,
"proxyConfiguration": {
"useApifyProxy": true,
"apifyProxyGroups": ["RESIDENTIAL"]
}
}

Export the dataset from the run results as JSON or CSV, or read it through the Apify dataset API.

Input parameters

ParameterWhat it doesDefault
maxResultsInteger maximum number of post records to save. The schema accepts values from 1 to 1000. The returned number can be lower when fewer posts are visible or parseable in the feed.50
keywordFilterKeeps posts whose URL contains this text. Matching is case-insensitive. Leave it empty to include all selected visible posts.Empty string
proxyConfigurationOptional Apify proxy settings. Omit the field or set useApifyProxy to false to use a direct connection.Apify RESIDENTIAL

No input field is required.

Limits and edge cases

ConditionWhat you seeWhat to do
Fewer posts are visible in the homepage feed than maxResultsThe dataset contains fewer records than the requested maximum.Treat the returned count as the number of posts available and parseable in that feed view.
keywordFilter does not occur in a post URLThat post is excluded from the dataset.Clear the filter or use text that occurs in the target post URLs.
A post has no value for a fieldThe field is not in that itemRead fields by name and allow for a missing key.
maxResults is zero or negative when supplied directlyThe Actor logs that no records were requested and returns without saving records.Use a positive value; the input schema accepts 1 through 1000.
The rendered homepage contains no parseable public post recordsThe run fails with an error stating that no parseable public post records were found.Check that the public homepage can be rendered and try the run again.
The configured browser runtime is unavailableThe run fails because Indie Hackers requires rendering.Check the run configuration and use an available browser runtime.
Indie Hackers markup or available posts changeThe set of parsed records or available fields can vary over time.Review the returned fields and account for optional values in downstream processing.
The Actor receives a direct connection configurationThe homepage is requested without an Apify proxy.Use the default proxy configuration to route requests through Apify Proxy.
A run is aborted, times out or fails after some records were savedRecords are added to the dataset as they are pushed. Records already pushed remain; later records are not added.Read the dataset after the run ends.

FAQ

How much does it cost to scrape Indie Hackers?

On the Free plan, $0.0024 per result ($2.40 per 1,000 results) plus $0.00005 per start event, charged once per GB of run memory (2 events, $0.0001, on the default 2048 MB run); see Pricing for the event names and billing details.

Why did my run return no records?

A URL keyword filter can exclude every visible post. A run can also fail when the rendered homepage contains no parseable public post records. Try clearing keywordFilter and check that the homepage can be rendered.

Why is the Actor not working?

This Actor requires a browser to render the Indie Hackers homepage. A browser-runtime error prevents collection, and changes to the Indie Hackers page can affect which posts are parsed. Check the run log, verify the browser runtime, and review the returned fields after a successful run.

Does the Actor collect discussion comments or post text?

No. comments is a count only, and the Actor returns no discussion comments or post-body text; see What you get.

The Actor reads public homepage content and requires no Indie Hackers login. Source terms and applicable law depend on your use case, so review them before using the collected data; this Actor does not provide a legal guarantee.