Migrate from another API (/v2)

If your code already calls a scraping API through its client library, the /v2 paths let you switch with a base URL and key change. Then move to the /v1 endpoints at your own pace.

Get an API key Read the migration guide

What the /v2 paths are

The /v2 paths accept the request and response shapes of the Firecrawl v2 API, so its official Node and Python clients can point at https://api.superscraper.dev with a SuperScraper key. Each /v2 request runs as one of our own /v1 operations, with the same key, rate limit, credits and prices, and is charged once. Coverage is partial. Options we cannot honor are refused with a 400 or named in a warning, and we never swap them silently.

Routes on the migration door

Supported options per route, tested client versions, error shapes and the routes that are not on the door are in the migration guide.

Migration routes and the /v1 operation each one runs as
/v2 route	Runs as
POST /v2/scrape	POST /v1/scrape
POST /v2/search	POST /v1/search
POST /v2/map	POST /v1/map
POST /v2/crawl	POST /v1/crawl
GET /v2/crawl/:id	GET /v1/crawl/:id
DELETE /v2/crawl/:id	DELETE /v1/crawl/:id
POST /v2/batch/scrape	POST /v1/batch (async)
GET /v2/batch/scrape/:id	GET /v1/jobs/:id
POST /v2/parse	POST /v1/parse

Moving to /v1

The migration door lets an existing integration switch quickly. New work should call the /v1 endpoints directly. They expose every option we support and return the full response, including metadata.completeness and metadata.extractionMethod on /v1/scrape, which the door leaves out.

All /v1 endpoints

curl -X POST https://api.superscraper.dev/v1/scrape \
  -H "Authorization: Bearer $SUPERSCRAPER_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://example.com"}'

Switch the base URL, keep your client

Get a key, point your client at the /v2 paths, then move calls to /v1 when you are ready.

Get an API key Read the migration guide

Trademark notice: Firecrawl is a trademark of its owner. SuperScraper is not affiliated with, sponsored by or endorsed by that owner. The name is used on this page only to identify the API the /v2 paths are compatible with.