RapidAPI Scraper

Extract public RapidAPI Marketplace API search results, provider details, ranking metadata, and visible quality signals for API discovery workflows.

RapidAPI Scraper helps developers and data teams turn RapidAPI Marketplace searches into structured datasets.

Use it to monitor API categories, discover competing API providers, enrich internal API catalogs, and build lead lists from public marketplace data.

What does RapidAPI Scraper do?

RapidAPI Scraper searches the public RapidAPI Marketplace.

It opens RapidAPI search pages in a browser.

It captures the public marketplace data used to render search results.

It saves one dataset row per API product.

Each row includes the API title, provider, category, description, pricing type, URL, ranking metadata, and quality scores when RapidAPI exposes them.

You can run broad keyword searches such as weather, email validation, or translation.

You can also provide RapidAPI search URLs directly.

Who is it for?

Developer relations teams

Find API providers in a category and track how they position their products.

API product teams

Monitor competing APIs, pricing labels, category changes, and listing descriptions.

Data enrichment teams

Build a structured catalog of APIs for internal search, procurement, or vendor intelligence.

Lead generation teams

Find public provider profiles and marketplace URLs for API vendors in a target niche.

Researchers and analysts

Export RapidAPI Marketplace search results to CSV, JSON, Excel, or your own data warehouse.

Why use this actor?

RapidAPI pages are designed for browsing, not bulk analysis.

Manual copying is slow.

Search results change over time.

A repeatable scraper gives you a timestamped dataset you can compare across runs.

The actor captures both visible listing fields and metadata from RapidAPI's public search payload.

It also includes fallback DOM extraction if the payload format changes.

Data you can extract

Field	Description
title	API listing title
providerName	Provider or organization name
category	RapidAPI category
description	Public API listing description
pricing	Visible pricing model such as FREEMIUM
profileUrl	RapidAPI API profile URL
playgroundUrl	RapidAPI playground URL
popularityScore	RapidAPI score when visible
averageLatencyMs	Latency signal when visible
averageSuccessRate	Success-rate signal when visible
rank	Rank within the captured search results
totalResults	Total results reported for the search
searchTerm	Query that produced the row
scrapedAt	Timestamp for the row

How much does it cost to scrape RapidAPI Marketplace?

This actor uses pay-per-event pricing.

There is a small start charge per run.

There is a per-item charge for each API record saved.

The current scaffold pricing is:

• Start: $0.005 per run.
• Item: tiered per saved API record, starting at $0.001 on BRONZE.

Final production pricing is validated from measured Apify run costs before publication.

Keep maxItems small for first tests.

Input options

searchTerms

List of RapidAPI Marketplace queries.

Example:

["weather", "email validation", "translation"]

startUrls

RapidAPI search URLs or API profile/playground URLs.

Example:

[{ "url": "https://rapidapi.com/search?term=weather&sortBy=ByRelevance" }]

maxItems

Maximum API records to save across all inputs.

Use a low number for smoke tests.

Use a larger number for category monitoring.

maxScrolls

Number of scroll passes per search page.

More scrolls may reveal more lazy-loaded results.

includeApiDetails

Open each API detail/playground page and save a short visible text snippet.

This is slower and uses more compute.

Example input: search intent

{
  "searchTerms": ["weather"],
  "maxItems": 25,
  "maxScrolls": 2,
  "includeApiDetails": false
}

Example input: competitive monitoring

{
  "searchTerms": ["email validation", "phone validation", "address validation"],
  "maxItems": 75,
  "maxScrolls": 2,
  "includeApiDetails": false
}

Example input: source-specific URL

{
  "startUrls": [
    { "url": "https://rapidapi.com/search?term=translation&sortBy=ByRelevance" }
  ],
  "searchTerms": [],
  "maxItems": 30,
  "maxScrolls": 1
}

Example output

{
  "title": "Open Weather",
  "providerName": "Quantum APIs",
  "category": "Weather",
  "pricing": "FREEMIUM",
  "profileUrl": "https://rapidapi.com/worldapi/api/open-weather13",
  "description": "Get real-time weather data for any location worldwide!",
  "popularityScore": 9.9,
  "averageLatencyMs": 356,
  "averageSuccessRate": 100,
  "searchTerm": "weather",
  "rank": 2,
  "totalResults": 491,
  "scrapedAt": "2026-06-20T20:36:18.354Z"
}

How to run

1. Open the actor on Apify.

2. Enter one or more RapidAPI search terms.

3. Set maxItems to the maximum number of API listings you need.

4. Leave includeApiDetails off for faster search exports.

5. Start the run.

6. Download the dataset as JSON, CSV, Excel, XML, or RSS.

Tips for best results

Use specific keywords.

Search email validation instead of only email.

Run multiple adjacent keywords for a complete category view.

Keep scheduled monitoring runs consistent so rank changes are comparable.

Use includeApiDetails only when you need page snippets.

Integrations

Send the dataset to Google Sheets for API lead review.

Export CSV into Airtable for provider tracking.

Load JSON into a warehouse for competitive intelligence dashboards.

Use webhooks to trigger alerts when a scheduled run finishes.

Combine with your CRM enrichment workflow to track API vendors.

API usage with Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/rapidapi-scraper').call({
  searchTerms: ['weather'],
  maxItems: 25,
});
console.log(run.defaultDatasetId);

API usage with Python

from apify_client import ApifyClient
import os

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('automation-lab/rapidapi-scraper').call(run_input={
    'searchTerms': ['weather'],
    'maxItems': 25,
})
print(run['defaultDatasetId'])

API usage with cURL

curl -X POST "https://api.apify.com/v2/acts/automation-lab~rapidapi-scraper/runs?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"searchTerms":["weather"],"maxItems":25}'

MCP usage

Use the actor through Apify MCP when you want an AI assistant to collect RapidAPI marketplace data directly from Claude Desktop or another MCP client.

MCP URL:

https://mcp.apify.com/?tools=automation-lab/rapidapi-scraper

Add the Apify MCP server from the command line:

$claude mcp add apify "https://mcp.apify.com/?tools=automation-lab/rapidapi-scraper"

Or add this MCP server configuration manually:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com/?tools=automation-lab/rapidapi-scraper"
    }
  }
}

Example prompts:

• "Find the top RapidAPI APIs for email validation and summarize providers."
• "Scrape RapidAPI weather APIs and return a CSV-ready table."
• "Monitor translation APIs on RapidAPI and highlight pricing labels."

Legality and responsible use

This actor extracts public marketplace information.

Do not use it to collect private account data.

Do not bypass authentication or access controls.

Respect RapidAPI terms and applicable laws.

Run at polite volumes.

Limitations

RapidAPI uses Cloudflare and client-side rendering.

The actor uses a browser to access public search pages reliably.

Very large result collection may require multiple search terms or future pagination improvements.

Some fields are optional because RapidAPI may not expose every score for every API.

Search ranking can change between runs.

Troubleshooting

I got fewer items than expected

Increase maxScrolls or add more specific search terms.

RapidAPI may only render a bounded first set for some searches.

The run is slower with detail pages

Disable includeApiDetails unless you need detail snippets.

Opening each profile page costs extra browser time.

Some fields are missing

RapidAPI does not expose every score, tag, or provider field for every listing.

Optional fields are omitted when unavailable.

Related scrapers

Use related Automation Labs actors when your workflow moves beyond API marketplace data:

• https://apify.com/automation-lab/website-contact-finder
• https://apify.com/automation-lab/bulk-url-status-checker

Future developer-tools actors should cross-link to RapidAPI Scraper for API marketplace discovery.

FAQ

Can I scrape any RapidAPI category?

Yes. Use search terms that match the category or workflow you care about.

Does this require a RapidAPI login?

No. The actor targets public marketplace pages.

Can I schedule monitoring?

Yes. Schedule the actor with the same input and compare datasets over time.

Can I collect provider contact details?

This actor only saves public marketplace provider names and URLs. Use a separate contact enrichment workflow if needed.

Is browser mode necessary?

Yes for this target. RapidAPI search records are hydrated through browser requests, so Playwright is more reliable than plain HTML parsing.