Spotted something off?Report on Discord
guides
Browser request
Execute a fully rendered browser request to render dynamic or JavaScript-heavy content with session reliability for authorized workflows.
Updated May 28, 2025
Execute a fully rendered browser session to render dynamic or JavaScript-heavy content with session reliability for authorized workflows.
Command
"cmd": "request.get"
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
cmd |
string | Yes | Must be "request.get" for browser GET requests. |
url |
string | Yes | The URL to request. |
Example
bash6 lines
Want to run this request directly in your browser?to try it live with your own API key.
Notes
Cost: 1 credit per successful request.
Pros
- Handles browser verification flows and JavaScript challenges within authorized workflows
- Renders dynamic content that a normal
GETcannot produce - Supports browser actions (e.g., clicking, scrolling, waiting)
- Works with single-page applications (SPAs)
Cons
- Slower execution (avg ~30 seconds)
- Higher cost than simple
GETrequests - More resource-intensive
- Relies on proxy usage and higher infrastructure demand
Also Works With
"cmd": "request.post"for browser-based POST requests- Compatible with
browserActions,autoparse, proxies, and custom headers
Use Cases
- Rendering JavaScript-heavy websites that require a full browser
- Interacting with form submissions or dynamic elements
- Dynamic websites that require JavaScript rendering or browser verification flows
This is the most flexible way to render content through Scrappey, ideal for authorized browser workflows. Respect third-party terms, robots.txt where applicable, rate limits, and applicable law.