From 28510a97b8bde9081df09ff0dc9561b89db217b5 Mon Sep 17 00:00:00 2001 From: "firecrawl-spring[bot]" <254786068+firecrawl-spring[bot]@users.noreply.github.com> Date: Tue, 12 May 2026 02:42:54 +0000 Subject: [PATCH] docs(scrape): mention profile parameter for persistent sessions Customers asked whether persistent session profiles work with /scrape the same way as /interact. They do, but the scrape feature page never mentioned it. Add a short section pointing at the existing Persistent Sessions docs. Co-Authored-By: micahstairs --- features/scrape.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/features/scrape.mdx b/features/scrape.mdx index 2161cc7d..b97eed06 100644 --- a/features/scrape.mdx +++ b/features/scrape.mdx @@ -334,6 +334,10 @@ It is important to almost always use the `wait` action before/after executing ot For workflows that require richer browser control after scraping, such as authenticated sessions, multi-step navigation, or a live view of the page, we recommend [Interact](/features/interact) over extending the actions array. +## Persistent browser profiles + +`/scrape` accepts the same `profile` parameter as the Browser and Interact endpoints. Passing `profile: { name: "" }` reuses a named browser profile across scrapes so cookies, `localStorage`, and other browser state are preserved between calls. See [Persistent Sessions](/features/browser#persistent-sessions) for the full profile lifecycle, including `saveChanges` semantics and the single-writer (`409`) constraint. + ## Location and Language Specify country and preferred languages to get relevant content based on your target location and language preferences.