Skip to content
Firecrawl Docsv2
Firecrawl Docs
Using the API

Introduction

Firecrawl API Reference (v2)

For AI agents: Use llms.txt for a full index of all documentation.

The Firecrawl API gives you programmatic access to web data. All endpoints share a common base URL, authentication scheme, and response format described on this page.

Features

Agentic Features

Base URL

All requests use the following base URL:

https://api.firecrawl.dev

Authentication

Every request requires an Authorization header with your API key:

Authorization: Bearer fc-YOUR-API-KEY

Include this header in all API calls. You can find your API key in the Firecrawl dashboard.

If you are an agent without an API key, start with Get credentials. If your platform supports WorkOS ID-JAG, use auth.md for registration instructions.

curl -X POST "https://api.firecrawl.dev/v2/scrape" \
  -H "Authorization: Bearer fc-YOUR-API-KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com"}'

Response codes

Firecrawl uses conventional HTTP status codes to indicate the outcome of your requests. Codes in the 2xx range indicate success, 4xx codes indicate client errors, and 5xx codes indicate server errors.

See Errors for the full reference, including the error string returned for each failure mode, retry guidance, and a copy-pasteable backoff snippet.

429 responses

When you exceed your plan’s rate or concurrency limits, the API returns a 429 status code. See Rate Limits for per-plan limits and Errors for retry guidance.

Was this page helpful?Suggest editsRaise issue