# Browser instructions (Beta)
When using Custom Browser Instructions, you can define your own specific browser instructions that are executed when rendering JavaScript.
{% hint style="success" %}
Generate **Browser instructions automatically** in the [**Web Scraper API Playground**](https://dashboard.oxylabs.io/?route=/api-playground) on the Oxylabs dashboard. Set up browser actions, test them, and export the generated instructions in JSON format.
{% endhint %}
### How to use it?
To use browser instructions, provide a set of `browser_instructions` when creating a job.
Let’s say you want to search for the term `pizza boxes` in a website.
An example job parameters would look as follows:
{% code overflow="wrap" %}
```bash
curl -k -x https://unblock.oxylabs.io:60000 \
-U 'USERNAME:PASSWORD' \
'https://www.ebay.com' \
-H 'x-oxylabs-render: html' \
-H "x-oxylabs-browser-instructions: [{\"type\":\"input\",\"value\":\"pizza boxes\",\"selector\":{\"type\":\"xpath\",\"value\":\"\/\/input[@class='gh-tb ui-autocomplete-input']\"}},{\"type\":\"click\",\"selector\":{\"type\":\"xpath\",\"value\":\"\/\/input[@type='submit']\"}},{\"type\":\"wait\",\"wait_time_s\":5}]"
```
{% endcode %}
**Step 1.** You must provide the `x-oxylabs-render: html` parameter.
**Step 2.** Browser instructions should be described in the `x-oxylabs-browser_instructions` field.
{% hint style="info" %}
The browser instructions provided as the header value must be JSON-escaped and contain no extra spaces.
{% endhint %}
The sample browser instructions above specifies that the aim is to enter a search term `pizza boxes` into a search field, click `search` button and wait for 5 seconds for content to load.
The scraped result should look as follows:
```html
Content after executing the instructions
```
Scraped HTML should look like this:
#### Fetching browser resources
We provide a standalone browser instruction for fetching browser resources.
The function is defined here:
Using `fetch_resource` will result in job returning the first occurrence of a Fetch/XHR resource that matches the format provided instead of the HTML that is being targeted.
Let’s say we want to target a GraphQL resource that is fetched when visiting a product page organically in the browser. We will provide job information as such:
{% code overflow="wrap" %}
```bash
curl -k -x https://unblock.oxylabs.io:60000 \
-U 'USERNAME:PASSWORD' \
'https://www.example.com/product-page/123' \
-H 'x-oxylabs-render: html' \
-H "x-oxylabs-browser-instructions: [{\"type\": \"fetch_resource\",\"filter\": \"\/graphql\/product-info\/123\"}]"
```
{% endcode %}
These instructions will result in a result as such:
```html
{"product_id": 123, "description": "", "price": 456}
```
### List of supported browser instructions
{% content-ref url="/pages/SGu8RZu47Z7fs4aiPCvr" %}
[List of instructions](/scraping-solutions/web-scraper-api/features/js-rendering-and-browser-control/browser-instructions/list-of-instructions.md)
{% endcontent-ref %}
### Status codes
See our response codes outlined [**here**](/advanced-proxy-solutions/web-unblocker/response-codes.md).
Status codes in regards to instructions validation are documented [**here**](/scraping-solutions/web-scraper-api/features/js-rendering-and-browser-control/browser-instructions/list-of-instructions.md#instructions-validation).
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://developers.oxylabs.io/advanced-proxy-solutions/web-unblocker/custom-browser-instructions/browser-instructions-beta.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.