Firecrawl APIfirecrawl.dev ↗
Fetch all integration cards from the Firecrawl integrations directory in one call. Returns names, descriptions, category sections, and target URLs for every listed integration.
What is the Firecrawl API?
The Firecrawl Integrations API exposes one endpoint — list_integrations — that returns all integration cards publicly listed on firecrawl.dev/integrations in a single response. Each call yields a structured array of entries with 6 fields per card including name, category, description, target_url, and section-level aggregates like categories counts. This covers the full directory in one shot with no pagination required.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/153b62ba-fdbd-4373-98d8-58cb80173b4f/list_integrations' \ -H 'X-API-Key: $PARSE_API_KEY'
Returns all integration cards shown on the public Firecrawl integrations page in a single call (one page load, no pagination). Grain is one card per category section: an integration listed under several categories (e.g. a card that appears in both Featured and MCP) is returned once per category, never merged. Each item carries the section heading as category, the card's display name, its description text, the card's target link resolved to an absolute URL, and the source page URL. categories summarises the sections found with their card counts; unreadable lists any section or card whose heading or name could not be read (empty when everything parsed). target_url is the link the card points at, which may be a Firecrawl page or external docs page; no relationship beyond the displayed link is implied.
No input parameters required.
{
"type": "object",
"fields": {
"items": "array of integration entries, one per card per category section",
"total": "number of items returned",
"categories": "array of {category, count} for each section found on the page, in page order",
"source_url": "page URL the entries were read from",
"unreadable": "array of {section_id, reason, href?} for sections/cards whose category heading or name could not be read; empty when all parsed",
"items[].name": "card display name",
"items[].category": "heading of the section the card sits in",
"items[].source_url": "page URL the card was read from",
"items[].target_url": "absolute URL the card links to",
"items[].description": "card description text, null if the card has none"
},
"sample": {
"data": {
"items": [
{
"name": "ChatGPT",
"category": "Featured",
"source_url": "https://www.firecrawl.dev/integrations",
"target_url": "https://www.firecrawl.dev/integrations/chatgpt",
"description": "Install the official Firecrawl plugin for ChatGPT."
},
{
"name": "Zencoder",
"category": "MCP",
"source_url": "https://www.firecrawl.dev/integrations",
"target_url": "https://docs.firecrawl.dev/mcp-server",
"description": "Add web scraping to Zencoder."
}
],
"total": 54,
"categories": [
{
"count": 7,
"category": "Featured"
},
{
"count": 7,
"category": "AI Development"
},
{
"count": 35,
"category": "MCP"
}
],
"source_url": "https://www.firecrawl.dev/integrations",
"unreadable": []
},
"status": "success"
}
}About the Firecrawl API
What the API Returns
The list_integrations endpoint returns every integration card displayed on the Firecrawl public integrations directory. The top-level response includes items (one object per card per category section), total (the count of those items), categories (an ordered array of {category, count} pairs matching the sections as they appear on the page), and source_url confirming the page the data was read from.
Per-Card Fields
Each entry in items carries name (the card's display title), category (the section heading under which the card appears), description (the card's body text, or null if none is present), target_url (the absolute URL the card links to), and source_url (always the integrations directory URL). Because a single integration can appear under more than one section — for example, a card listed under both "Featured" and "MCP" — it will have a distinct entry in items for each section, which is why total can exceed the number of unique integration names.
Coverage and Error Handling
The categories array is returned in page order, so the sequence of sections is preserved. Any card or section heading that cannot be parsed is reported in the unreadable array with a section_id, a human-readable reason, and an optional href. When all cards parse cleanly, unreadable is an empty array. There are no filter inputs; the single call always returns the full directory snapshot.
Official API Note
Firecrawl does offer its own official developer API (documented at firecrawl.dev/docs) for web crawling and scraping tasks. The Parse API described here targets specifically the integrations directory page and is distinct from Firecrawl's own API product.
The Firecrawl API is a managed, monitored endpoint for firecrawl.dev — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when firecrawl.dev changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official firecrawl.dev API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Audit which tools and frameworks are officially listed as Firecrawl integrations by category section.
- Monitor the integrations directory over time to detect newly added or removed cards using the
totalanditemsfields. - Extract
target_urlvalues for all integration cards to build a link graph of Firecrawl's ecosystem partners. - Compare
categoriescounts across sections to understand how integrations are distributed (e.g., Featured vs. MCP vs. other sections). - Populate an internal knowledge base or dashboard with up-to-date integration names and descriptions.
- Identify integrations that lack descriptions by filtering
itemswheredescriptionisnull.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Firecrawl have an official developer API?+
Why does `total` sometimes exceed the number of distinct integration names?+
items is one entry per card per category section. An integration that appears under multiple sections — such as both 'Featured' and 'MCP' — generates a separate entry for each section, so total reflects card appearances, not unique integrations.Does the API support filtering by category or returning only a specific section?+
list_integrations endpoint takes no inputs and always returns the full directory. The categories array in the response lets you group or filter client-side by section. You can fork the API on Parse and revise it to add a category filter parameter if you need server-side filtering.Does the API return historical snapshots or changelog data about integrations?+
What does the `unreadable` field indicate?+
section_id, a reason string, and an optional href. When all entries on the page are readable, unreadable is an empty array.