Firecrawl API
/v0/* endpoint removal
Deprecated, no dateSubscribe to Firecrawl APIShare
On May 15, 2026, Firecrawl API deprecated /v0/* endpoints without announcing a shutdown date. Affected paths include /v0/scrape, /v0/crawl, /v0/crawl/status/:jobId, DELETE /v0/crawl/cancel/:jobId, and /v0/search. Requests calling these endpoints will eventually fail.
Calls it hits
/v0/*
What to use instead of these calls
Move to the v2 endpoints: POST /v2/scrape, POST /v2/crawl, GET /v2/crawl/{id}, DELETE /v2/crawl/{id}, and POST /v2/search.
In Firecrawl API's words
Deprecated /v0/scrape, /v0/crawl, /v0/crawl/status/:jobId, DELETE /v0/crawl/cancel/:jobId, /v0/search, /v1/extract, /v1/extract/:jobId, /v2/extract, /v2/extract/:jobId, /v1/deep-research, /v1/deep-research/:jobId, /v1/llmstxt, and /v1/llmstxt/:jobId.
Facts
- API
- Firecrawl API
api.firecrawl.dev - Kind
- Endpoint removal
- Announced
- May 15, 2026
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Firecrawl API's own pages
Questions
When does this change take effect?
Firecrawl API deprecated /v0/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Firecrawl API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Firecrawl API 5
-
No date
/v1/deep-research*Endpoint removal Deprecated, no date -
No date
/v1/extract*Endpoint removal Deprecated, no date -
No date
/v1/llmstxt*Endpoint removal Deprecated, no date -
No date
/v2/extract*Endpoint removal Deprecated, no date -
No date
/v2/research/*Endpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.