Bubble Plugin Marketplace Data as Structured Output
Bubble's plugin marketplace is a moving catalog of installs, ratings, categories and pricing tiers.
This page describes an API workflow for pulling those public plugin pages at scale and receiving parsed fields instead of raw HTML. The request path is one HTTP call: you supply a Bubble plugin URL and your API key; the service rotates proxies, spoofs browser fingerprints and renders JavaScript before returning a response ready to parse.
What a Bubble plugin page returns
Each plugin page can yield plugin name, developer, install count, rating, review count, category, pricing tier and the full description. That field set supports three common jobs: watching competitor plugins, catching new marketplace launches, and aggregating the catalog for recommendation feeds.
A practical field map for the eight outputs:
- plugin name — the listing title
- developer — the publisher named on the listing
- install count — the marketplace install figure
- rating — the displayed score
- review count — the number of reviews behind the score
- category — the marketplace category
- pricing tier — the listing's price band
- description — the full listing text
If a field is missing on a given page, treat it as absent rather than zero; an absent install count is not the same as no installs.
Choosing the right request control
The source names several controls. Match the control to the problem rather than enabling everything:
- render_js=true — use when the page needs a real headless browser and post-render HTML. This is the JavaScript answer.
- stealth_proxy — use when CAPTCHA or anti-bot friction is the blocker.
- country_code — use when content varies by geography and you need a residential IP in that country.
- extract_rules — use when you can map CSS selectors to field names and want parsed JSON.
- ai_extract_rules — use when a natural-language spec is easier than selectors; the response still comes back as parsed JSON.
A useful rule of thumb: start with the plain request, add render_js only if the fields are missing from the initial HTML, and add stealth_proxy only if you see blocking rather than empty fields. Those are different failures and need different controls.
Worked example: one plugin page to one record
Suppose you point the API at a single Bubble plugin listing. With render_js=true the page runs in a headless browser and you receive post-render HTML. With extract_rules you map selectors to the eight field names above; with ai_extract_rules you describe the same fields in plain language. Either way the response is parsed JSON, so your downstream step is a field-by-field validation pass rather than an HTML parsing pass.
A minimal validation checklist before you store the record:
- Confirm the plugin name and developer are non-empty.
- Confirm install count and review count are numeric, not strings with separators.
- Confirm rating falls inside the expected scale.
- Confirm category and pricing tier match your allowed vocabularies.
- Flag any record where description is empty, since that often signals a render failure rather than a genuinely blank listing.
Rate limits vs concurrency limits
These are not the same thing. The API applies concurrency limits per plan — the number of requests that can be sent at the same time — rather than a per-target rate limit. If the target site throttles aggressive patterns, spacing out requests or using multiple sessions is the remedy. Raising your plan raises concurrency; it does not remove a target's own throttling.
Concurrency figures by plan are listed in the pricing table below. Treat them as the captured reference values and confirm current terms before committing to a plan.
Languages and SDKs
SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works too. The dashboard request builder lets you paste a URL, set parameters and copy a generated snippet in Python, Node, Go, PHP, Ruby or cURL — so you can start without writing the request by hand. Pick whichever your stack already uses; there is no requirement to switch languages for this task.
Plan and credit reference
The pricing table below preserves the captured plan rows, credit allowances, concurrency figures and feature availability. Two credit rules matter when estimating cost: API credits are valid for one month and do not roll over, and requests start at one credit each. JavaScript rendering costs five API credits per successful request; premium proxies cost ten or twenty-five credits depending on whether JS rendering is enabled. Geotargeting reaches 200+ countries and territories (40+ on classic proxies).
Because these are captured reference values, check the current pricing page before purchase. All prices in the captured table are exclusive of VAT.
Compliance and data handling
The service states that it does not collect or store personal data from scraped sites unless the user explicitly requests it. For a Bubble plugin catalog, the fields described here are marketplace listing attributes rather than personal data, but your own retention and purpose limitation still apply. Keep the scope to public plugin pages and avoid pulling developer personal details you do not need.
| Plan | Price /mo | API credits | Concurrent requests | Priority support | Account manager | Team management |
|---|---|---|---|---|---|---|
| Hobby | $19 | 75,000 | 25 | Not included | Not included | Not included |
| Freelance | $49 | 250,000 | 50 | Not included | Not included | Not included |
| Startup (Recommended) | $99 | 1,000,000 | 100 | Not included | Not included | Not included |
| Business | $249 | 3,000,000 | 200 | Included | Included | Included |
| Business + | $599 | 8,000,000 | 400 | Included | Included | Included |
| Enterprise 14 | $999 | 14,000,000 | 500 | Included | Included | Included |
| Enterprise 24 | $1,599 | 24,000,000 | 600 | Included | Included | Included |
| Enterprise 41 (Recommended) | $2,399 | 41,000,000 | 700 | Included | Included | Included |
| Enterprise 69 | $3,599 | 69,000,000 | 800 | Included | Included | Included |
| Enterprise 120 | $5,799 | 120,000,000 | 900 | Included | Included | Included |
Captured reference values. All prices exclusive of VAT. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots and extraction rules are included on every plan in the captured table. Check current pricing before purchase.
Frequently asked questions
Can I scrape Bubble plugins without writing code?
Yes. The dashboard request builder lets you paste a URL, set parameters and copy a generated snippet in Python, Node, Go, PHP, Ruby or cURL.
How do I handle JavaScript when scraping Bubble plugins?
Pass render_js=true. The page runs in a real headless browser, JavaScript executes server-side, and you receive the post-render HTML.
Can I scrape Bubble plugins from a specific country?
Yes. Pass country_code to route through a residential IP in that country, which helps when content varies by geography.
What's the rate limit for scraping Bubble plugins?
The API has concurrency limits per plan rather than per-target rate limits. If the target throttles aggressive patterns, space out requests or use multiple sessions.
How do I get structured JSON from Bubble plugins?
Two routes produce parsed JSON. With extract_rules you supply CSS selectors paired to your chosen field names. With ai_extract_rules you describe the fields in plain language instead of selectors. Either way, the response arrives already parsed, so no separate HTML-to-JSON step is needed.
Which programming languages can I use to scrape Bubble plugins?
Any. SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works too. Use whatever your stack already uses.