Whop.com Scraper avatar

Whop.com Scraper

Pricing

from $1.00 / 1,000 results

Go to Apify Store
Whop.com Scraper

Whop.com Scraper

Scrape Whop.com community listings by search query, category, or URL. Extracts id, title, route, verified, member count, reviews, creator pitch, owner, images. HTTP-only, no proxy.

Pricing

from $1.00 / 1,000 results

Rating

5.0

(4)

Developer

Crawler Bros

Crawler Bros

Maintained by Community

Actor stats

4

Bookmarked

1

Total users

0

Monthly active users

3 days ago

Last modified

Share

Scrape public Whop.com community listings via search, category, or direct URL. HTTP-only — no cookies, no login, no proxy required.

What this actor extracts

Per community:

  • id, title, route, url
  • verified status
  • memberCount, reviewsCount, reviewsAverage
  • totalViews
  • creatorPitch (creator-written description)
  • createdAt
  • logoUrl, bannerUrl
  • owner (id, username, name, avatarUrl)
  • scrapedAt

Input

FieldTypeDescription
searchQueriesstring[]List of search keywords. Each query returns up to 20 results (Whop server cap).
startUrlsstring[]Whop URLs: search pages, category pages, or direct community pages.
categoryenumOptional category (trading, fitness, gaming, etc.). When set, is added as an extra search query.
maxItemsintegerMaximum records across all inputs (default 50, cap 500).

At least one of searchQueries, startUrls, or non-any category is required.

How it works

Whop.com runs on Next.js 14 App Router with React Server Components (RSC). Passing the rsc: 1 header to any page URL returns a text/x-component streaming response that contains server-rendered JSON for the page. We parse those line-by-line and collect community objects.

Limitations

  • 20 results per search query — Whop's search endpoint server-renders only the first page. To get more results, use multiple search queries covering related terms.
  • Discover homepage / category pages with no query return nothing server-side (they're client-side hydrated). The actor maps categories to search queries internally.
  • Custom domain communities (e.g. third-party storefronts) are not supported.

FAQ

Do I need cookies / login? No.

Do I need a proxy? No — the actor hardcodes Apify's RESIDENTIAL US proxy pool with per-request session rotation. Vercel rate-limits datacenter IPs so residential is mandatory and baked into the actor. No user configuration needed.

Why only 20 per query? Whop's frontend loads additional results via client-side XHR after hydration. A server-side scraper only gets the server-rendered batch.