revenuegrowthguide.com APIwww.revenuegrowthguide.com ↗
Search and retrieve B2B growth experiments from Revenue Growth Guide. Access experiment details, FAQs, tags, time-to-implement, and related experiments via 2 endpoints.
curl -X GET 'https://api.parse.bot/scraper/10f2766e-8119-4c24-9b72-759666227915/search_experiments' \ -H 'X-API-Key: $PARSE_API_KEY'
Search experiments by category with optional text query filtering. Returns experiment listings with title, description, tags, and time-to-implement. Text query filters results by matching against title, description, and tags.
| Param | Type | Description |
|---|---|---|
| query | string | Text search query to filter experiments within the category. Matches against title, description, and tags (case-insensitive). Omitted returns all experiments in category. |
| category | string | Category to filter experiments. Accepts exactly one of: website, digital_ads, content, social_media, events, sponsorships, email, pr_influencers. |
{
"type": "object",
"fields": {
"query": "string",
"total": "integer",
"category": "string",
"experiments": "array of experiment summaries with number, slug, page_slug, title, tags, tti, description"
},
"sample": {
"query": "hero",
"total": 3,
"category": "website",
"experiments": [
{
"tti": "medium",
"slug": "homepage-hero-ab-test",
"tags": [
"CRO",
"hero",
"A/B test",
"Inbound",
"MOFU"
],
"title": "Homepage Hero A/B Test: Video, Copy, and CTA Variants",
"number": 1,
"page_slug": "homepage-hero-ab-test-video-copy-and-cta-variants",
"description": "Your homepage hero is the first thing every visitor sees..."
}
]
}
}About the revenuegrowthguide.com API
The Revenue Growth Guide API provides access to a library of B2B growth experiments across categories like website, digital ads, content, and social media through 2 endpoints. search_experiments returns filterable listings with titles, descriptions, tags, and time-to-implement values, while get_experiment_detail delivers full experiment records including FAQs, related experiments, and category metadata.
What the API Returns
The search_experiments endpoint accepts an optional category parameter — one of website, digital_ads, content, social_media, events, and others — and an optional query string that filters results by matching against experiment titles, descriptions, and tags. Each result in the experiments array includes a number, slug, page_slug, title, tags, tti (time-to-implement), and a short description. The response also surfaces the total count of matched experiments and echoes back the active category and query.
Experiment Detail Records
get_experiment_detail takes a page_slug from search results and returns the full experiment record. The response includes the experiment name, category, category_label, tags, tti, slug, number, and page_slug. It also returns a faq array of question-and-answer objects specific to that experiment, and a related array listing adjacent experiments with their own name, category, category_label, and page_slug values — useful for building recommendation flows or content graphs.
Filtering and Navigation
The two endpoints are designed to work together: use search_experiments to discover experiments by category or keyword, then pass the returned page_slug into get_experiment_detail to fetch the complete record. The query parameter in search performs case-insensitive matching across title, description, and tags, so you can narrow results to specific tactics like A/B testing, onboarding, or retargeting without knowing exact experiment names in advance.
- Build a B2B growth tactic browser filtered by channel category and keyword
- Populate a growth experiment recommendation engine using the
relatedarray from detail records - Generate experiment briefs by pulling
faqandttifields for a givenpage_slug - Tag and index experiments by
tagsarrays to power internal search or taxonomy tools - Track time-to-implement (
tti) across categories to prioritize quick-win experiments - Feed experiment metadata into a CMS or knowledge base for sales and marketing teams
- Map experiment coverage gaps by querying each category and counting
totalresults
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Revenue Growth Guide offer an official developer API?+
What does `search_experiments` return when no category or query is provided?+
search_experiments returns experiment listings from across the full library. The response includes each experiment's title, tags, tti, description, slug, and page_slug, along with a total count of matched records.Does the `get_experiment_detail` endpoint return the full experiment methodology or step-by-step instructions?+
name, category, tags, tti, faq question-and-answer pairs, and a related experiments array. Extended how-to methodology text beyond what appears in the faq field is not currently exposed as a distinct field. You can fork this API on Parse and revise it to add an endpoint that surfaces additional body content if the source page includes it.Can I retrieve a list of all available categories through the API?+
category values for search_experiments are fixed: website, digital_ads, content, social_media, events, seo, and similar slugs documented in the parameter spec. You can fork this API on Parse and revise it to add a categories endpoint that returns the full list dynamically.Does the API support pagination for `search_experiments` results?+
search_experiments response returns a total integer and an experiments array, but the endpoint does not currently expose pagination parameters such as page number or offset. If the library grows and you need paginated access, you can fork this API on Parse and revise it to add those parameters.