What I Learned Building Adapters for Product Hunt and Indie Hackers

Product Hunt and Indie Hackers are where makers gather. They are not the same crowd as Reddit or Stack Overflow. A complaint on Indie Hackers is not a customer frustrated with a product. It is a founder frustrated with the tools, platforms, or business realities of building software. The pain signals are different. They are more valuable if you are building for makers.

I built adapters for both platforms to understand this difference. Product Hunt has a GraphQL API that is trivially easy to use. Indie Hackers does not publish an API, but I reverse-engineered their Algolia search integration. Here is what I learned.

Product Hunt's public GraphQL API (no auth required)

Product Hunt exposes a GraphQL endpoint at https://api.producthunt.com/v2/api/graphql. No authentication required for public data.

A basic query for the day's top posts looks like this:

query {
  posts(first: 10, after: "") {
    nodes {
      id
      name
      tagline
      description
      createdAt
      commentsCount
      votesCount
      maker {
        name
      }
    }
  }
}

You get back the product name, tagline, description, creation date, comment count, vote count, and maker info. The API is generous. You can pull thousands of posts and their comments without hitting rate limits.

One gotcha: Product Hunt uses cursor-based pagination with an "after" parameter. You cannot skip to page 50. You have to start at page 1 and move forward. For large historical pulls, this is slow. But for recent data, it is fine.

What makes Product Hunt different from Hacker News

Both are communities of builders. But the vibe is different. Hacker News is more intellectual. Product Hunt is more commercial. When someone launches on Product Hunt, they are making a business decision. The comments often discuss pricing, market fit, and competitive positioning.

A thread on Hacker News about a new programming language might discuss the technical merits and language design. The same thread on Product Hunt would discuss whether people would pay for it and what market it is trying to address.

For pain point mining, this matters. A complaint on Product Hunt often includes a business angle. "This is frustrating because I am paying $200/month for this and it is missing feature X." That is more actionable than "this is frustrating." You know the person is a paying customer and willing to spend money on a solution.

Indie Hackers: reverse-engineering the search

Indie Hackers does not publish an API. The site has no official way to query posts or comments programmatically. So I did what you do when there is no API: I figured out what the website uses under the hood.

Indie Hackers uses Algolia for full-text search. Algolia is a search service that exposes a JavaScript client. When you search on the Indie Hackers website, the browser makes requests to Algolia's API directly. These requests are not authenticated. They are public.

I intercepted one of these requests and reverse-engineered the Algolia index structure. The posts index has fields for title, content, author, creation date, comment count, upvote count, and more. I wrote a query client that talks directly to Algolia, bypassing Indie Hackers' website entirely.

A search for posts containing "payment processing" looks like:

GET https://[algolia-app-id]-dsn.algolia.net/1/indexes/posts/query
{"params":"query=payment%20processing&hitsPerPage=100&page=0"}

Algolia returns JSON with up to 100 results per request. You can paginate through hundreds of posts.

Legal and ethical complexity

Using Indie Hackers' Algolia index is technically accessing their data through an undocumented interface. Indie Hackers does not explicitly forbid it, but they also do not document it. Is it okay?

My take: the data is public. It is posted by humans who decided to share it. Algolia is not protected by authentication. The queries are read-only. I am not impacting Indie Hackers' infrastructure. But I am also aware that Indie Hackers could shut me down by changing their search backend.

For ScopeScrape, I include the Indie Hackers adapter as optional. If the maintainers ask me to take it down, I will. Until then, it is useful and I am not hiding it.

Why founder pain points are different from user pain points

A user complaint is tactical. "This button does not work." A founder complaint is strategic. "This tool took 20 hours to set up and we still cannot integrate it with our existing stack."

Founder pain points are often about time, money, and integration. They are not just about product features. They are about operational overhead. This is valuable information if you are building tools for businesses or other builders.

Reddit might tell you users are frustrated with a feature. Product Hunt will tell you founders are frustrated because the feature does not integrate with their other tools, or the pricing makes it unaffordable at scale, or switching costs are too high.

On Indie Hackers, founders post about the business and operational challenges of building software. "How do I handle support as a solo founder?" "What payment processor should I use for an international marketplace?" These are not feature requests. They are operational pain points. And they are valuable if you are building infrastructure for makers.

Data quality and noise

Product Hunt is high-quality data. Posts are moderated. Comments are from real accounts. Spam is rare. The tradeoff is that you see only products that made it through Product Hunt's review process and were launched publicly.

Indie Hackers is more open. Anyone can post. The quality is more variable. But you see problems that people are struggling with in real-time, not just products they have finished building.

For ScopeScrape, I treat both as signals. Product Hunt data is high-confidence validation. Indie Hackers data is exploratory. The scoring weights reflect this difference.

What you cannot get from either platform

Neither platform exposes user-level data like individual email addresses, account details, or conversation history you do not have access to. Both are public data only.

Product Hunt explicitly forbids scraping for commercial purposes. Their terms say you cannot use the data to build competing products. Indie Hackers does not have explicit anti-scraping language (because they do not have published APIs), but the spirit is the same.

For ScopeScrape, I use both platforms for research only. I am not building a competing product. I am not selling the data. I am not using it to serve ads. If the intent changes, I would need to reconsider the ethics.

Why these platforms matter together

By themselves, Product Hunt tells you what is being launched and Indie Hackers tells you what founders are struggling with. Together, they tell you a story. If there is a lot of discussion about a problem on Indie Hackers, and then a product launching on Product Hunt to solve it, you know the pain is real and worth solving.

If a problem is discussed on Indie Hackers but no one launches a product to solve it on Product Hunt, it might be a fundamental problem (hard to solve) or a niche problem (not enough market). Either way, it is information.