Transition from Firecrawl to ScrapeGraph v2

​

Why switch?

​

Feature comparison at a glance

​

Authentication

​

SDK installation

​

Migration checklist

​

Quick cURL sanity check

curl -X POST https://v2-api.scrapegraphai.com/api/scrape \
  -H "SGAI-APIKEY: $SGAI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://example.com","formats":[{"type":"markdown"}]}'

{
  "id": "3b1c81d9-3f3b-42b0-9cf7-6926d9ebc7f5",
  "results": {
    "markdown": { "data": ["# Example Domain\n\n..."] }
  },
  "metadata": { "contentType": "text/html" }
}

​

Common gotchas

• Header name. It’s SGAI-APIKEY: sgai-..., not Authorization: Bearer .... Watch for proxies that normalize header casing — the API tolerates any case, but some HTTP libraries strip non-standard headers in redirects.
• schema field name in Python. JsonFormatConfig and extract use schema= (the field is internally aliased from schema_ to avoid shadowing the BaseModel.schema method — pass schema= from your code and it works).
• No actions array. If you relied on click/type/press actions, you’ll need to either split the flow into two scrapes (one to trigger a navigation that produces a stable URL, one to scrape the result) or contact support about the upcoming interactions API.
• Crawl is always async. There is no blocking sgai.crawl(...) — call crawl.start and poll, or pass a webhookUrl via a monitor instead.
• changeTracking is gone as a format. Use monitor.create — it gets you cron scheduling, persistent history, and webhook delivery in one resource.
• Response shape per format. Each requested format lives under results[<format>].data (always an array). For most formats the array has one element; for links and images it’s the full list.
• numResults caps at 20 for search. Firecrawl’s limit accepts higher values — split the query (e.g., by timeRange) if you need more.

​

Full SDK documentation

• Python SDK
• JavaScript SDK
• CLI (just-scrape)
• MCP Server
• API Reference