# Browser request

Source: https://docs.scrappey.com/docs/browser-request

> Execute a fully rendered browser session to handle anti-bot mechanisms and retrieve dynamic or JavaScript-heavy content.

## 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

```bash
curl -X POST "https://publisher.scrappey.com/api/v1?key=YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "cmd": "request.get",
    "url": "https://example.com"
  }'
```

## Notes

**Cost:** 1 credit per successful request.

**Pros**

* Handles bot protections like Cloudflare, CAPTCHA, and JS challenges
* Retrieves content that normal `GET` cannot access
* Supports browser actions (e.g., clicking, scrolling, waiting)
* Enables scraping from single-page applications (SPAs)

**Cons**

* Slower execution (avg ~30 seconds)
* Higher cost than simple `GET` requests
* 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**

* Scraping JavaScript-heavy websites
* Interacting with form submissions or dynamic elements
* Accessing sites when standard scraping is blocked

This is the most powerful and flexible way to extract data through Scrappey, ideal for advanced scraping workflows.