# Browser request

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

> 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

```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 browser verification flows and JavaScript challenges within authorized workflows
* Renders dynamic content that a normal `GET` cannot produce
* Supports [browser actions](/docs/browser-actions) (e.g., clicking, scrolling, waiting)
* Works with 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"`](/docs/request-post) for browser-based POST requests
* Compatible with `browserActions`, [`autoparse`](/docs/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.