DevDocs Documentation Sets Scraper
Pricing
from $7.69 / 1,000 results
DevDocs Documentation Sets Scraper
Scrapes documentation sets from DevDocs by name or keyword. Returns each docset as a flat row with name, slug, and version. Export to CSV, JSON, Excel, or XML.
Pricing
from $7.69 / 1,000 results
Rating
0.0
(0)
Developer
ParseForge
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
9 days ago
Last modified
Categories
Share
DevDocs Documentation Sets Scraper
Scrape documentation sets from DevDocs, the free API documentation browser. Get every docset name, slug, and version in one flat list, up to a million entries per run. No login, no API key. Export to CSV, JSON, Excel, or XML.
DevDocs aggregates hundreds of API documentation sets into one searchable interface, but there is no official API to list them all. This Actor reads the public docset index directly and returns each documentation set as a flat row, so you can inventory what is available, monitor new releases, or build your own documentation index. Filter by name or keyword, set a maximum count, and export the results in the format you need.
| Who uses it | What they scrape DevDocs for |
|---|---|
| Developer tool builders | Discover which documentation sets are available to integrate into their own products |
| Technical writers | Keep track of documentation versions across multiple projects |
| Data analysts | Build a catalog of documentation resources for internal knowledge bases |
| Open source maintainers | Monitor when new documentation sets are added to DevDocs |
What it does
This Actor collects documentation sets from DevDocs by name or keyword, and returns each one as a flat row with its name, slug, and version.
- 🔍 Keyword filter: return only docsets whose name or slug contains your search text, like python, react, or css.
- 📋 Full listing: leave the search field empty to get every documentation set DevDocs currently offers.
- 🔢 Result cap: set a maximum number of entries per run, from 1 up to 1,000,000.
- 📦 Flat output: each docset is one row with name, slug, and version, ready for CSV, JSON, Excel, or XML.
Results export to CSV, JSON, Excel, or XML, or straight from the API.
What you can do with DevDocs data
📚 Build a documentation inventory.
A developer tools company runs this Actor with no search filter to get a complete list of every documentation set on DevDocs, then uses the output to decide which APIs to support in their product.
🔎 Find specific docsets.
A technical writer searches for 'python' to see all Python-related documentation sets, including their slugs and versions, so they can link to the correct reference in their guides.
📈 Monitor new additions.
An open source maintainer schedules this Actor to run weekly and compares the results to spot when a new documentation set appears, so they can update their community resources.
🗂️ Feed a knowledge base.
A data analyst collects the full docset list and imports it into an internal wiki, giving their team a searchable catalog of available documentation without manual entry.
Why choose this scraper
| What you get | |
|---|---|
| No official API | DevDocs does not expose a public API for listing docsets, so this Actor reads the index directly |
| Up-to-date catalog | Every run returns the current list of documentation sets, including newly added ones |
| Simple filtering | Search by name or slug to narrow down to the docsets you care about |
| Scalable output | Collect up to a million entries in a single run, then export to your preferred format |
How it compares
No other Store actor targets DevDocs the same way, so the honest comparison is with the alternatives teams actually weigh.
| DevDocs Documentation Sets Scraper | Build it in-house | By hand | |
|---|---|---|---|
| Setup | Run it now, zero config | Days of engineering | None, but hours per pull |
| When DevDocs changes | Maintained for you | You fix it | You re-learn the page |
| Proxies, retries, anti-bot | Built in | Your problem | Browser only |
| Output | Fixed JSON schema, CSV/Excel export | Whatever you build | Copy-paste |
| Cost | Pay per result | Engineering time | Analyst hours |
Configure the run
Drive the Actor with a documentation name or keyword, and set a maximum number of entries to collect per run. The filter runs as each docset is read, so only matches reach your dataset. The Input tab lists every parameter.
A first run with the defaults:
A larger pull:
Pricing
Pay-per-result: $0.0085 per result collected. You pay only for the results written to your dataset.
| Results collected | Approximate cost |
|---|---|
| 100 results | $0.85 |
| 1,000 results | $8.50 |
| 10,000 results | $85.00 |
New Apify accounts start with $5 in free credit.
Free users
Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.
Run it
- Create a free Apify account with $5 in credit.
- Open the DevDocs Documentation Sets Scraper.
- Set your inputs and any filters, then click Start.
- Export the results as CSV, Excel, JSON, or XML from the Dataset tab.
Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.
Use with AI agents (MCP)
Give an AI agent live access to DevDocs through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:
Then prompt it in plain language to run the scraper and read back the results.
Troubleshooting
Why am I getting no results?
Make sure your search keyword is spelled correctly and is not too specific. The filter matches substrings, so try a shorter term. For example, 'py' will match 'Python' and 'PyTorch'. If you still get no results, the docset may not be available on DevDocs.
Why is my run taking a long time?
If you set a very high maximum entries value, the Actor may need to read the entire docset index. Reduce the maximum entries or add a search filter to speed up the run.
Can I get more than 1,000,000 entries?
No, the maximum entries per run is 1,000,000. If you need more, you can split your request into multiple runs with different search filters.
The output is missing a field I expected.
The Actor returns the fields that are available in the DevDocs docset index: name, slug, and version. If you need additional data, such as the documentation URL, you may need to use a different scraper or the DevDocs website directly.
FAQ
| Question | Answer |
|---|---|
| What is DevDocs? | DevDocs is a free, open source web application that combines documentation from many APIs and programming languages into a single searchable interface. It is widely used by developers to look up syntax, functions, and examples quickly. |
| Does this Actor require an API key or login? | No. This Actor reads the public docset index from DevDocs, so you do not need to register an application, authenticate, or worry about rate limits. |
| What data does each result contain? | Each result is a flat row with the documentation set's name, slug, and version. The exact fields are shown in the sample output from a real run. |
| Can I filter by documentation name? | Yes. Use the 'Documentation name or keyword' input to return only docsets whose name or slug contains your text. For example, entering 'react' will match React, React Native, and any other docset with 'react' in its name or slug. |
| How many entries can I collect? | You can set the maximum entries from 1 to 1,000,000 per run. If you leave the search field empty, the Actor will list every docset currently available, up to your specified limit. |
| What output formats are supported? | The Actor can export results to CSV, JSON, Excel, or XML. You can choose the format when you set up your run in Apify. |
| Is this Actor affiliated with DevDocs? | No. This Actor is an independent tool built by the Apify community. It is not endorsed by or affiliated with DevDocs or its maintainers. |
| Can I schedule this Actor to run automatically? | Yes. Apify supports scheduling for any Actor. You can set it to run daily, weekly, or on a custom cron schedule to keep your documentation list up to date. |
| What if I get no results? | Check your search keyword. The filter is case-insensitive and matches substrings, so 'css' will find 'CSS' and 'CSS Reference'. If you still get no results, the docset may not exist on DevDocs. |
| How do I get the full list of docsets? | Leave the 'Documentation name or keyword' field empty and set a high maximum entries value, such as 1000. The Actor will return every docset currently listed on DevDocs. |
Related actors
Browse the full ParseForge collection for more scrapers.
🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.
⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by DevDocs. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.
