Skip to content

docs(scrape): mention profile parameter for persistent sessions #939

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
firecrawl-spring wants to merge 1 commit into
base: main
Choose a base branch
from
+4 −0
Open

docs(scrape): mention profile parameter for persistent sessions #939

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions features/scrape.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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: "<your-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.
Expand Down