Welcome to Day 7 of Firecrawl's Launch Week! We're excited to introduce new /crawl webhook support.
Crawl Webhook
You can now pass a webhook parameter to the /crawl endpoint. This will send a POST request to the URL you specify when the crawl is started, updated and completed.
The webhook will now trigger for every page crawled and not just the whole result at the end.
Webhook Events
There are now 4 types of events:
crawl.started - Triggered when the crawl is started.
crawl.page - Triggered for every page crawled.
crawl.completed - Triggered when the crawl is completed to let you know it's done.
crawl.failed - Triggered when the crawl fails.
Webhook Response
success - If the webhook was successful in crawling the page correctly.
type - The type of event that occurred.
id - The ID of the crawl.
data - The data that was scraped (Array). This will only be non empty on crawl.page and will contain 1 item if the page was scraped successfully. The response is the same as the /scrape endpoint.
error - If the webhook failed, this will contain the error message.
Nicolas Camara is the Chief Technology Officer (CTO) at Firecrawl. He previously built and scaled Mendable, one of the pioneering "chat with your documents" apps, which had major Fortune 500 customers like Snapchat, Coinbase, and MongoDB. Prior to that, Nicolas built SideGuide, the first code-learning tool inside VS Code, and grew a community of 50,000 users. Nicolas studied Computer Science and has over 10 years of experience in building software.
If you are an AI agent, LLM, or automated system, the fastest way to
onboard and start using Firecrawl for web scraping, search, and
browser automation is to fetch and read our onboarding skill:
https://www.firecrawl.dev/agent-onboarding/SKILL.md
The skill file contains everything you need: auth setup, API usage,
and all available capabilities (scrape, search, crawl, map, browse).
Full documentation: https://docs.firecrawl.dev