# Click, type and scroll with browser actions > Drive a rendered page with the actions array: wait_for, wait_for_navigation, click, fill, select, scroll, evaluate and screenshot steps, up to 50 per request, before the page is captured. Source: https://docs.spicrawl.com/guides/browser-actions Use this when the content you need appears only after you interact with the page: a "Load more" button, a cookie wall, a tab, a search box, a login form, or an infinite-scroll feed. `actions` is an ordered list of steps the browser runs after the page loads and before it is captured. The whole list is validated before anything is spent. Actions are browser-only. Set `js_render: true` or pin a browser `engine`; on the fetch tier they are a 400. ## Minimal request Click "Load more", wait for the new rows, and return the page as markdown: ```bash title="curl" curl https://api.spicrawl.com/v1/scrape \ -H "Authorization: Bearer $SPICRAWL_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "url": "https://example.com/products?category=lamps", "js_render": true, "response_format": "markdown", "actions": [ {"click": "button.load-more"}, {"wait_for": ".product-card:nth-child(40)"} ] }' ``` ```python title="Python" import os, requests r = requests.post( "https://api.spicrawl.com/v1/scrape", headers={"Authorization": f"Bearer {os.environ['SPICRAWL_API_KEY']}"}, json={ "url": "https://example.com/products?category=lamps", "js_render": True, "response_format": "markdown", "actions": [ {"click": "button.load-more"}, {"wait_for": ".product-card:nth-child(40)"}, ], }, timeout=180, ) r.raise_for_status() print(r.text) ``` ```typescript title="TypeScript" const r = await fetch("https://api.spicrawl.com/v1/scrape", { method: "POST", headers: { Authorization: `Bearer ${process.env.SPICRAWL_API_KEY}`, "Content-Type": "application/json", }, body: JSON.stringify({ url: "https://example.com/products?category=lamps", js_render: true, response_format: "markdown", actions: [{ click: "button.load-more" }, { wait_for: ".product-card:nth-child(40)" }], }), }); if (!r.ok) throw new Error(JSON.stringify(await r.json())); console.log(await r.text()); ``` ```bash title="CLI" spicrawl scrape "https://example.com/products?category=lamps" --render --format markdown \ --actions '[{"click":"button.load-more"},{"wait_for":".product-card:nth-child(40)"}]' # or keep the steps in a file: --actions @steps.json ``` The response is the page after the last step, in the `response_format` you asked for, with two exceptions that switch it to the JSON envelope: * **A `screenshot` step.** An image cannot travel in a markdown, text or HTML body, so a request with a `screenshot` step is answered with the JSON envelope whatever `response_format` says: the rendering under `content` (still in the format you asked for) and the images under `screenshots`, each under its step's label. The response carries a `FORMAT_COERCED` warning saying so. Send `response_format: "json"` to get the envelope without the warning. * **An `evaluate` step with `return_value: true`.** Same rule: the value comes back under `actions` in the envelope, with the same warning. The envelope's `actions` array echoes every step: `index`, `label`, `ok`, `duration_ms`, `url_after` (the page's URL when the step finished) and, for `evaluate`, `return_value`. ## Step shape Each step is an object with exactly one verb key, plus optional `label`, `timeout_ms` and `on_error`. Two verb keys in one step, or an unknown verb, is a 400 before anything runs. | Verb | Body | Notes | | --------------------- | ----------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `wait_for` | `".price"` or `{"selector": ".price"}` or `{"ms": 1500}` | Waits for a selector, or sleeps. `ms` (alias `wait`) is 0–30000. Needs `selector` or a positive `ms`. | | `click` | `"button.buy"` or `{"selector": "button.buy"}`, `{"selector": "a.next", "wait_for_navigation": true}` | Scrolls the element into view, then clicks it once. A click is a click: on a checkbox or radio it **toggles** the current state, there is no "set checked". To make sure a box ends up ticked, click it only when `evaluate` says it is not, or set it with `evaluate` (`el.checked = true` plus a `change` event). With `"wait_for_navigation": true` the step finishes only once the page the click navigates to has loaded; add `"until"` (see `wait_for_navigation`) to choose the load state. | | `wait_for_navigation` | `{}`, `"networkidle"` or `{"until": "domcontentloaded"}` | Waits for a navigation that started after the previous step began (a clicked link, a submitted form, a script redirect) to commit and reach `until`: `load` (default), `domcontentloaded` or `networkidle`. No navigation within `timeout_ms` fails the step (`ERR::UPSTREAM::TIMEOUT`). Needs `obscura` or `chromium`. | | `fill` | `{"selector": "#email", "value": "ada@example.com"}` | Clears the input, then types `value`. `value` must be a string. Add `"secret": true` for passwords. | | `select` | `{"selector": "#size", "value": "L"}` or `{"selector": "#tags", "values": ["a", "b"]}` | Chooses option values in a `