# Indie Hackers Startup Revenue & Interview Scraper (`vexaloom-labs/indie-hackers-startup-revenue-and-interview`) Actor

Browse Indie Hackers products by self-reported revenue, launch date or followers, list founder interviews and community groups, or resolve specific product, interview and group URLs.

- **URL**: https://apify.com/vexaloom-labs/indie-hackers-startup-revenue-and-interview.md
- **Developed by:** [vexaloom-labs](https://apify.com/vexaloom-labs) (community)
- **Categories:** Developer tools, Social media, Lead generation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.49 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Indie Hackers Startup Revenue & Interview Scraper

Indie Hackers is where bootstrapped founders publish their products alongside self-reported monthly revenue, follower counts, and founder interviews. This actor collects that product catalog, the founder interview index, and community groups, or resolves specific product/interview/group URLs directly.

### What this actor does

- Browses the product catalog, with a revenue-ranked order available and an optional keyword filter (see the `sortBy` FAQ entry for the other sort options' current behavior).
- Lists founder interviews with publish dates and the product/founder they belong to.
- Lists community groups with member counts and descriptions.
- Resolves a list of specific Indie Hackers product, interview, or group URLs into the matching record type.
- Fields a product, interview, or group hasn't filled in (for example no disclosed revenue, or no Twitter handle) are left out of that record.

### Output per product

| Field | Description |
| --- | --- |
| `name` | Product name. |
| `slug` | Product's Indie Hackers ID. |
| `tagline` | One-line product tagline. |
| `description` | Longer product description. |
| `websiteUrl` | Product's own website. |
| `indiehackersUrl` | Link to the product's page on Indie Hackers. |
| `logoUrl` | Product logo/avatar image URL. |
| `monthlyRevenue` | Self-reported monthly revenue, when the founder discloses one. |
| `memberCount` | Number of followers on Indie Hackers. |
| `launchDate` | Reported launch date. |
| `twitterHandle` / `facebookUrl` | Social links, when provided. |
| `commitment` | Founder's stated commitment level (e.g. full-time, side project). |
| `employees` | Reported team size bracket. |
| `founders` | Founder count bracket tags. |
| `funding` | Funding status tags, when disclosed. |
| `revenueModel` | Revenue model tags (e.g. subscription, one-time). |
| `verticals` | Industry/vertical tags. |
| `platforms` | Platform tags (e.g. web, mobile). |
| `founderUsername` / `founderName` / `founderAvatarUrl` | The listed founder's Indie Hackers username, display name, and avatar. |
| `scrapedAt` | ISO timestamp of when the record was captured. |

### Output per interview

| Field | Description |
| --- | --- |
| `title` | Interview title. |
| `slug` | Interview's Indie Hackers ID. |
| `interviewUrl` | Link to the interview on Indie Hackers. |
| `intervieweeSlug` / `intervieweeName` | Username and display name of the founder interviewed. |
| `productId` / `productUrl` | The product the interview is linked to, when one is set. |
| `publishedDate` / `createdDate` | When the interview was published and originally created. |
| `scrapedAt` | ISO timestamp of when the record was captured. |

### Output per group

| Field | Description |
| --- | --- |
| `name` | Group name. |
| `slug` | Group's Indie Hackers ID. |
| `description` | Group description. |
| `groupUrl` | Link to the group on Indie Hackers. |
| `iconUrl` | Group icon image URL. |
| `memberCount` | Number of members in the group. |
| `createdDate` | When the group was created. |
| `scrapedAt` | ISO timestamp of when the record was captured. |

### Input

| Field | Type | Default | Description |
| --- | --- | --- | --- |
| `mode` | String (select) | `products` | `products`, `interviews`, `groups`, or `byUrl`. |
| `sortBy` | String (select) | `revenue-desc` | Product sort order (mode=products): `revenue-desc` reliably ranks by revenue; `foundedDate-desc`, `memberCount-desc`, and `name-asc` currently return Indie Hackers' default catalog order rather than actually re-sorting (see FAQ). |
| `searchQuery` | String | – | Keyword filter for product name/tagline or group name/description. |
| `pageUrls` | Array of strings | – | Indie Hackers product, interview, or group URLs to resolve directly (mode=byUrl). |
| `maxItems` | Integer | 50 | Maximum number of items to return. |

#### Example: top products by revenue

```json
{
  "mode": "products",
  "sortBy": "revenue-desc",
  "maxItems": 100
}
```

#### Example: top-revenue products matching a keyword

```json
{
  "mode": "products",
  "searchQuery": "newsletter",
  "sortBy": "revenue-desc",
  "maxItems": 30
}
```

#### Example: resolve specific pages

```json
{
  "mode": "byUrl",
  "pageUrls": [
    "https://www.indiehackers.com/product/example-product",
    "https://www.indiehackers.com/group/example-group"
  ]
}
```

### Use cases

- **Market researchers** tracking which bootstrapped products report the highest monthly revenue in a vertical.
- **VC and acquisition scouts** sourcing self-funded startups with disclosed traction before they raise.
- **Content curators** pulling founder interviews for newsletters or roundups.
- **Competitive analysts** monitoring how competitors describe their revenue model, team size and funding status.
- **Community managers** mapping Indie Hackers groups by member count and topic.

### FAQ

**Does this need an Indie Hackers account?**
No. It reads the same public product, interview and group listings shown to any visitor.

**Why is `monthlyRevenue` missing from some products?**
Revenue figures on Indie Hackers are self-reported by founders; when a founder hasn't disclosed one, the field is left out rather than shown as zero.

**Does the interview record include the full interview text?**
No, it returns the interview's metadata (title, dates, interviewee, linked product) rather than the transcript body.

**What's the difference between `founders`, `employees`, and `commitment`?**
These come from separate tags the founder sets on their product: `founders` is the founder-count bracket, `employees` is the team-size bracket, and `commitment` is whether they work on it full-time or as a side project.

**Does `sortBy` actually change the order products come back in?**
Only `revenue-desc` is currently guaranteed — it pulls from Indie Hackers' own revenue-ranked index. `foundedDate-desc`, `memberCount-desc`, and `name-asc` are accepted but currently return results in the catalog's default order rather than re-sorting by date, member count, or name.

**Can I look up a specific product, interview or group I already know the URL for?**
Yes, use `mode: "byUrl"` with those URLs in `pageUrls`; the actor detects whether each URL is a product, interview, or group.

**Is this affiliated with Indie Hackers?**
No. This is an independent tool and is not affiliated with, endorsed by, or sponsored by Indie Hackers or Stripe.

# Actor input Schema

## `mode` (type: `string`):

What to fetch from Indie Hackers.

## `sortBy` (type: `string`):

Sort order for products (mode=products).

## `searchQuery` (type: `string`):

Keyword filter for product name/tagline or group name/description.

## `pageUrls` (type: `array`):

Indie Hackers page URLs to scrape (product or interview pages).

## `maxItems` (type: `integer`):

Maximum number of items to return.

## Actor input object example

```json
{
  "mode": "products",
  "sortBy": "revenue-desc",
  "maxItems": 50
}
```

# Actor output Schema

## `results` (type: `string`):

Dataset containing all scraped Indie Hackers items (products, interviews, or groups).

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "mode": "products",
    "sortBy": "revenue-desc",
    "maxItems": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("vexaloom-labs/indie-hackers-startup-revenue-and-interview").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "mode": "products",
    "sortBy": "revenue-desc",
    "maxItems": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("vexaloom-labs/indie-hackers-startup-revenue-and-interview").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "mode": "products",
  "sortBy": "revenue-desc",
  "maxItems": 50
}' |
apify call vexaloom-labs/indie-hackers-startup-revenue-and-interview --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/indie-hackers-startup-revenue-and-interview"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/I4vgGUChyzGHjWHXn/builds/DDJoCa2L7Scr379X3/openapi.json
