Create URL Document
Fetch a URL via Firecrawl and ingest the rendered content as a document. The fetch happens synchronously; expect a few seconds per page. Use the sitemap / crawl endpoints for multi-page imports.
Authentication
Enter your API key with the Bearer prefix, e.g. ‘Bearer sk_…’.
Path parameters
Knowledge base id (prefixed external id, kb_...).
Headers
Request
Folder to drop the document into. Prefixed wire identifier
(kfolder_<26 char Crockford base32>); null/omitted = root.
Response headers
Response
The document was accepted and is being fetched + embedded
asynchronously. The returned row is a placeholder with
status: fetching; poll the document until it reaches
ready or failed.
Prefixed wire identifier (kb_<26 char Crockford base32>) of
the knowledge base the document belongs to.
How the document entered the KB. file is the upload path,
text is inline pasted content, url is fetched via
Firecrawl. Sitemap and crawl imports also produce url rows.
Folder this document lives in. Null for root-level (unfiled) documents. Mutated via the move endpoint.
Document lifecycle. fetching is the pre-scrape state used
only by url-sourced rows; file and text docs skip straight
to embedding because their content is available
synchronously. Terminal states are ready and failed.
Source URL for url-sourced documents (and the sitemap / crawl imports that produce them). Empty string for file and text rows.