Skool Community and Pricing Data Scraping
Skool community, pricing and discovery pages are rendered by JavaScript and sit behind active bot detection.
A hosted scraping API handles the browser, proxy rotation and anti-bot layer so your client stays a thin HTTP call and your code focuses on parsing the fields you actually need.
What you can collect from public Skool pages
Public Skool pages expose a stable set of fields that most teams care about: community name, member count, pricing tier, course list, public reviews, event activity and discovery-page badges. Those fields are the ones the API is designed to return without you writing HTML selectors, and they cover the three jobs that dominate Skool scraping: product availability checks, public review tracking, and member engagement monitoring.
A useful rule of thumb is to decide which of those three jobs you are actually doing before you pick request options. Availability and pricing checks usually only need the rendered page. Review tracking benefits from structured extraction so you can compare communities over time. Engagement monitoring is the most sensitive because it depends on public post and event activity rather than anything behind a login.
Scope check before you build:
- Confirm the field you want is visible on the public page, not only after sign-in.
- Confirm the community page you plan to poll is publicly reachable.
- Confirm your retention policy matches the field sensitivity (member counts and pricing are low risk; named individuals are not).
- Confirm your polling cadence matches how often the page actually changes.
Request options and what each one costs in credits
The API accepts a Skool URL by GET or POST and returns rendered HTML. To get structured JSON back, add extract_rules with CSS or XPath selectors, or ai_extract_rules for natural-language extraction. Four request options cover the common Skool cases, and each one has a different credit cost:
- render_js turns on JavaScript rendering. Each successful request that enables JS rendering costs 5 API credits.
- Premium proxies cost 10 credits when JS rendering is off, or 25 credits when it is on.
- stealth_proxy is the heavier option for aggressive targets and costs 75 credits.
- country_code routes the request through a chosen geography; the platform supports 200+ countries and territories on premium proxies and 40+ on classic proxies.
A simple decision order keeps cost down: start with the plain request, add render_js if the page is JavaScript-driven, add premium proxies if you see IP-based blocking, and only move to stealth_proxy when the target is actively hostile. Screenshots and extraction rules are included on every plan, so the cost difference between options is the only variable you need to model.
Field map: what comes back and where it comes from
The following fields are the ones the API is designed to return for a Skool page. Treat this as a map of what to expect, not a guarantee that every page will populate every field.
- Community name and member count: the identity and size of the community, useful for discovery and comparison.
- Pricing tier: the public price band for the community, useful for competitor positioning.
- Course list: the courses a community advertises publicly, useful for content and offer research.
- Public reviews and star ratings: public testimonials and discovery-page social proof, useful for competitor-community research without touching student data.
- Event activity: public event signals, useful for community managers tracking growth, retention and event ROI.
- Discovery-page badges: public markers that appear on Skool discovery pages.
If a field you need is not on this list, it is likely behind a login or rendered only for signed-in members. The API is designed around public pages, and the legal guidance is to avoid post-login content.
Worked example: estimating a monthly credit budget
The credit costs above let you estimate a monthly budget before you commit. Suppose you want to poll 200 public Skool community pages once a day for a month, and each page needs JavaScript rendering plus premium proxies because the target blocks plain requests.
Each request costs 25 credits (premium proxy with JS rendering). 200 pages × 30 days = 6,000 requests, so the monthly total is 6,000 × 25 = 150,000 credits. That fits comfortably inside the Freelance plan's 250,000 credits and stays well under the Startup plan's 1,000,000. If you drop the premium proxy and only need JS rendering, the same workload costs 6,000 × 5 = 30,000 credits, which fits inside the Hobby plan's 75,000 credits.
Two practical notes: API credits are valid for one month and do not roll over, so size the plan to the month you actually need; and the credit cost per request depends on the options you enable, so a single plan can cover very different workloads depending on how aggressively you configure each request.
Legal and scope: what to keep out of your pipeline
Public-facing pages can usually be scraped, but the target site's terms of service should be reviewed before you deploy, and post-login content should be avoided. That means member-only posts, private course materials, and anything that requires a signed-in session are out of scope for this workflow.
The API itself does not collect or store personal data from scraped sites unless the user explicitly requests it, which keeps the platform side of the pipeline neutral. The responsibility for what you extract and how long you keep it stays with you. A short internal checklist helps: confirm the field is public, confirm the retention window, confirm the polling cadence, and confirm the community page is reachable without a login.
Getting started
The setup path is short: create an account to get an API key and 1,000 free credits, install the SDK for your stack (Python, Node, Go, PHP or Ruby), then POST or GET the Skool URL. The API renders the page, handles anti-bot, and returns rendered HTML or structured JSON depending on which extraction option you used.
If you prefer to skip the SDK, the documentation includes Python, Node.js, cURL and request-builder examples you can copy and adapt. The request builder is useful for testing a single Skool URL before you wire it into a pipeline.
| Plan | Price / month | API credits | Concurrent requests | Priority email support | Dedicated account manager | Team management |
|---|---|---|---|---|---|---|
| Hobby | $19 /mo | 75,000 | 25 | Not included | Not included | Not included |
| Freelance | $49 /mo | 250,000 | 50 | Not included | Not included | Not included |
| Startup (Recommended) | $99 /mo | 1,000,000 | 100 | Not included | Not included | Not included |
| Business | $249 /mo | 3,000,000 | 200 | Included | Included | Included |
| Business + | $599 /mo | 8,000,000 | 400 | Included | Included | Included |
| Enterprise 14 | $999 /mo | 14,000,000 | 500 | Included | Included | Included |
| Enterprise 24 | $1,599 /mo | 24,000,000 | 600 | Included | Included | Included |
| Enterprise 41 (Recommended) | $2,399 /mo | 41,000,000 | 700 | Included | Included | Included |
| Enterprise 69 | $3,599 /mo | 69,000,000 | 800 | Included | Included | Included |
| Enterprise 120 | $5,799 /mo | 120,000,000 | 900 | Included | Included | Included |
All prices are exclusive of VAT. API credits are valid for one month and do not roll over. Requests start at 1 credit each. JavaScript rendering is included on every plan and costs 5 credits per successful request. Rotating and premium proxies are included on every plan and cost 10 or 25 credits per successful request depending on whether JS rendering is enabled. Geotargeting, screenshots and extraction rules are included on every plan. Plan prices and inclusions are commercial terms that vary by provider and should be checked against current pricing before purchase.
| Option | Effect | Credit cost |
|---|---|---|
| render_js | JavaScript rendering | 5 credits per successful request |
| premium_proxy (JS off) | Premium proxy without JS rendering | 10 credits per successful request |
| premium_proxy (JS on) | Premium proxy with JS rendering | 25 credits per successful request |
| stealth_proxy | Heavier anti-bot bypass | 75 credits per successful request |
| country_code | Route through a chosen geography | Included with premium proxies (200+ countries and territories); 40+ on classic proxies |
Credit costs are the per-request figures supplied for this page. They apply to successful requests and depend on which options are enabled together.
Frequently asked questions
Do I need an account to scrape Skool?
No external Skool account is required. You sign up for one of the API keys (1,000 free credits, no card), send the target URL, and the API handles the rest.
Is scraping Skool legal?
Public-facing pages can usually be scraped, but you should review the target site's terms of service before deploying and avoid post-login content.
What data can I extract from Skool?
Whatever is visible on the public page. You can describe the fields you want with ai_extract_rules, or point at them directly with CSS selectors in extract_rules; either route returns structured JSON.
How do I start scraping Skool?
Sign up, grab your API key, and send a GET request with the target URL. The API renders the page, rotates proxies, and returns the data. You get 1,000 free credits to test.
Will I get blocked when scraping Skool?
Requests are routed through rotating residential proxies and driven by a real headless browser, so they resemble ordinary visitor traffic. If a target starts blocking aggressively, turn on stealth_proxy for that request.
How much does it cost to scrape Skool?
A free trial allowance and paid plan prices are commercial terms that depend on the provider, so treat the figures below as a reference framework rather than a current quote. A typical offer gives new accounts a starter credit balance with no card required, and paid plans begin at $19/month for higher volume and concurrency. The credit cost per request depends on options: 5 credits for JS rendering, 25 for premium_proxy with JS, and 75 for stealth_proxy. Check the provider's current pricing page before you commit.
Should I use extract_rules or ai_extract_rules for Skool?
Use extract_rules when you already know the CSS or XPath selectors for the fields you want, because the extraction is deterministic and cheap to re-run. Use ai_extract_rules when the page structure changes often or you want to describe the fields in natural language. Both return structured JSON; the trade-off is selector maintenance versus a natural-language spec.
What is the difference between premium_proxy and stealth_proxy?
premium_proxy routes the request through a higher-quality proxy pool and costs 10 or 25 credits per successful request depending on whether JS rendering is enabled. stealth_proxy is the heavier option for aggressive targets and costs 75 credits per successful request. Start with premium_proxy and only move to stealth_proxy when the target is actively blocking.