Publishers and tools
Scrapy.io organizes the catalog as:
Publisher → Tool → Version / interface
Public identity
The stable public identity of a tool is:
{publisher} + {slug}
Examples:
| Publisher | Slug | Meaning |
|---|---|---|
datadoping | instagram-profile-scraper | Data Doping’s Instagram profile tool |
datadoping | linkedin-company-scraper | Same publisher, different tool |
Use these strings in Platform URLs:
GET /v1/tools/{publisher}/{slug}
and when creating schedules:
{
"publisher": "datadoping",
"slug": "instagram-profile-scraper"
}
You do not need internal database UUIDs for everyday Platform usage.
Execution URLs
Each tool detail includes execution hints for the publisher host:
{
"execution": {
"apiUrl": "https://datadoping.p.scrapy.infralyon.com/instagram-profile-scraper/v1/api",
"scraperUrl": "https://datadoping.p.scrapy.infralyon.com/instagram-profile-scraper/v1/scraper"
}
}
| Path | Mode |
|---|---|
/v1/api | Sync — one request, one JSON result |
/v1/scraper | Async — start a batch run, then poll |
These hosts are separate from api.scrapy.infralyon.com. See Sync vs async.
Discovering tools
# Search
curl "https://api.scrapy.infralyon.com/v1/tools?q=google+maps&limit=20" \
-H "Authorization: Bearer $SCRAPY_API_KEY"
# Detail + schemas
curl "https://api.scrapy.infralyon.com/v1/tools/datadoping/instagram-profile-scraper" \
-H "Authorization: Bearer $SCRAPY_API_KEY"
Tool detail may include:
inputSchema— fields expected by the tooldatasetSchema— how outputs are structured / viewedpricePerResult— billing unit for successful rowsfeatures— e.g.API,Scrapercategories— marketplace categories
Only active / published tools appear. Unpublished tools return 404.
Versions
Publisher execution URLs currently use a path version such as v1:
/{slug}/v1/api
/{slug}/v1/scraper
Breaking input/output contract changes use a new version segment (for example v2), not a change to the Platform /v1 namespace. Platform /v1 is the Platform API version prefix, not a per-tool contract version.