Legacy APIs
APIs that predate the modern Crawlbase platform but are still operational. Some are closed to new sign-ups; some are simply older shapes being gradually replaced. None are scheduled for shutdown.
What does "legacy" mean here?
These APIs are still fully operational for existing customers. Some are closed to new sign-ups (Scraper, Leads, Screenshots) and some are simply older products being gradually replaced by newer ones. None are being shut down. If you're already using them, nothing changes. If you're starting fresh, the modern alternatives are linked below.
Legacy APIs in this section
Scraper APIlegacy
Standalone JSON-extraction endpoint. Closed to new sign-ups Oct 2024. Modern path: Crawling API +
&scraper=.Leads APIlegacy
Email lead extraction by domain. Closed to new sign-ups Oct 2024.
Screenshots APIlegacy
Standalone screenshot endpoint. Closed to new sign-ups Nov 2024. Modern path: Crawling API + screenshot params, or
crawl_screenshot via MCP.Proxy Backconnect APIlegacy
Account API
Monitor monthly usage, credits, and per-domain success rates across products. Still actively supported.
User Agents APIfree
Random User-Agent strings optimized for web crawling. Free to use, rate-limited to 1 req/sec.
When to use legacy vs modern
| If you need… | Modern API | Why |
|---|---|---|
| Structured JSON from a known site | Crawling API with &scraper=name | Same scrapers, simpler endpoint, more parameters |
| A page screenshot | Crawling API + screenshot params, or MCP's crawl_screenshot | Combined with the same JS-rendering pipeline you already use |
| Rotating residential proxy | Smart AI Proxy | Better routing, AI ban avoidance, fewer config knobs |
| Account-level metadata | Account API | This is still the canonical endpoint — it lives in this section because it predates the modern split, not because it's deprecated |
| Random User-Agent strings | User Agents API | Same — free, supported, no replacement planned |