# Vanilla JS Scraper (`mstephen190/vanilla-js-scraper`) Actor Scrape the web using familiar JavaScript methods! Crawls websites using raw HTTP requests, parses the HTML with the JSDOM package, and extracts data from the pages using Node.js code. Supports both recursive crawling and lists of URLs. This actor is a non jQuery alternative to CheerioScraper. - **URL**: https://apify.com/mstephen190/vanilla-js-scraper.md - **Developed by:** [Matthias Stephens](https://apify.com/mstephen190) (community) - **Categories:** Automation, Developer tools, Open source - **Features:** Full permissions - **Stats:** 529 total users, 1 monthly users, 100.0% runs succeeded, 5 bookmarks - **User rating**: No ratings yet ## Pricing Pay per usage This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## Vanilla JS Scraper Vanilla JS Scraper is a ready-made solution for crawling websites using plain HTTP requests with support for familiar JavaScript syntax. It runs on top of [Apify CheerioCrawler](https://sdk.apify.com/docs/api/cheerio-crawler) and utilizes the [JSDOM](https://github.com/jsdom/jsdom) package to retrieve the HTML pages, parse them, and extract any data from them. Fast. Vanilla JS Scraper is ideal for scraping web pages that do not rely on client-side JavaScript to serve their content, and can be up to 20 times faster than using a full-browser solution such as Puppeteer. If you're unfamiliar with web scraping or web development in general, you might prefer to start with the [**Web scraping tutorial**](https://apify.com/docs/scraping/web-scraper-tutorial) from the Apify documentation. ### Table of Contents - [Usage](#usage) - [Content types](#content-types) - [Limitations](#limitations) - [Input configuration](#input-configuration) - [Start URLs](#start-urls) - [Link selector](#link-selector) - [Pseudo-URLs](#pseudo-urls) - [Page function](#page-function) - **[`window: Object`](#window-object)** - **[`document: Object`](#document-object)** - **[`body: String | Buffer`](#body-string-buffer)** - **[`crawler: Object`](#crawler-object)** - **[`userData: Object`](#userdata-object)** - **[`customData: Object`](#customdata-object)** - **[`enqueueRequest(request, [options]): AsyncFunction`](#enqueuerequest-request-options-asyncfunction)** - **[`kvStore: Object`](#kvstore-object)** - **[`json: Object`](#json-object)** - **[`request: Object`](#request-object)** - **[`response: Object`](#response-object)** - [Proxy configuration](#proxy-configuration) - [Results](#results) - [Additional resources](#additional-resources) - [Upgrading](#upgrading) ### Usage To get started with Vanilla JS Scraper, you only need two things. First, tell the scraper which web pages it should load. Second, tell it how to extract data from each page. The scraper starts by loading the pages specified in the [**Start URLs**](#start-urls) field. You can make the scraper follow page links on the fly by setting a [**Link selector**](#link-selector) and/or [**Pseudo URLs**](#pseudo-urls) to tell the scraper which links it should add to the crawling queue. This is useful for the recursive crawling of entire websites, e.g. to find all products in an online store. To tell the scraper how to extract data from web pages, you need to provide a [**Page function**](#page-function). This is JavaScript code that is executed for every web page loaded. Since the scraper does not use the full web browser, writing the **Page function** is equivalent to writing server-side Node.js code. In summary, Vanilla JS Scraper works as follows: 1. Adds each [Start URL](#start-urls) to the crawling queue. 2. Fetches the first URL from the queue and constructs a DOM from the fetched HTML string. 3. Executes the [**Page function**](#page-function) on the loaded page and saves its results. 4. Optionally, finds all links from the page using the [**Link selector**](#link-selector). If a link matches any of the [**Pseudo URLs**](#pseudo-urls) and has not yet been visited, adds it to the queue. 5. If there are more items in the queue, repeats step 2, otherwise finishes. ### Content Types By default, Vanilla JS Scraper only processes web pages with the `text/html` and `application/xhtml+xml` MIME content types (as reported by the `Content-Type` HTTP header), and skips pages with other content types. If you want the crawler to process other content types, use the **Additional MIME types** (`additionalMimeTypes`) input option. Note that while the default `Accept` HTTP header will allow any content type to be received, HTML and XML are preferred over JSON and other types. Thus, if you're allowing additional MIME types and you're still receiving invalid responses, be sure to override the `Accept` HTTP header setting in the requests from the scraper, either in [**Start URLs**](#start-urls), [**Pseudo URLs**](#pseudo-urls) or in the **Pre-Navigation Hooks**. The web pages with various content types are parsed differently and thus the `context` parameter of the [**Page function**](#page-function) will have different values: | **Content types** | [`context.body`](#body-string-buffer) | [`context.document`](#document-object) | [`context.json`](#json-object) | | --------------------------------------------------------- | ------------------------------------- | -------------------------------------- | ------------------------------ | | `text/html`, `application/xhtml+xml` or `application/xml` | `String` | `Object` | `null` | | `application/json` | `String` | `Object` | `Object` | | Other | `Buffer` | `Object` | `null` | ### Limitations The actor does not employ a full-featured web browser such as Chromium or Firefox, so it will not be sufficient for web pages that render their content dynamically using client-side JavaScript. To scrape such sites, you might prefer to use **[Web Scraper](https://apify.com/apify/web-scraper)** (`apify/web-scraper`), which loads pages in a full browser and renders dynamic content. Since Vanilla JS Scraper's **Page function** is executed in the context of the server, it only supports server-side code running in Node.js. If you need to combine client-side and server-side libraries in Chromium using the [Puppeteer](https://github.com/GoogleChrome/puppeteer/) library, you might prefer to use **[PuppeteerScraper](https://apify.com/apify/puppeteer-scraper)** (`apify/puppeteer-scraper`). For even more flexibility and control, you might develop a new actor from scratch in Node.js using the [Apify SDK](https://sdk.apify.com). In the **[Page function](#page-function)**, **Pre-Navigation Hooks**, and **Post-Navigation Hooks**, you can only use NPM modules that are already installed in this actor. If you require other modules for your scraping, you'll need to develop a completely new actor. You can use the [`CheerioCrawler`](https://sdk.apify.com/docs/api/cheerio-crawler) class from Apify SDK to get most of the functionality of Vanilla JS Scraper out of the box. ### Input configuration As input, the Vanilla JS Scraper actor accepts a number of configurations. These can be entered either manually in the user interface in [Apify Console](https://console.apify.com), or programmatically in a JSON object using the [Apify API](https://apify.com/docs/api/v2#/reference/actors/run-collection/run-actor). For a complete list of input fields and their types, please visit the [Input](https://apify.com/apify/vanilla-js-scraper?section=input-schema) tab. #### Start URLs The **Start URLs** (`startUrls`) field represents the initial list of pages that the scraper will visit. You can either enter the URLs manually one by one, upload them in a CSV file, or [link URLs from a Google Sheet](https://help.apify.com/en/articles/2906022-scraping-a-list-of-urls-from-google-spreadsheet) document.Each URL must start with either a `http://` or `https://` protocol prefix. The scraper supports adding new URLs to scrape on the fly, either using the [**Link selector**](#link-selector) and [**Pseudo-URLs**](#pseudo-urls) options or by calling `context.enqueueRequest()` inside the [**Page function**](#page-function). Optionally, each URL can be associated with custom user data - a JSON object that can be referenced from your JavaScript code in the [**Page function**](#page-function) under `context.request.userData`. This is useful for determining which start URL is currently loaded, in order to perform some page-specific actions. For example, when crawling an online store, you might want to perform different actions on a page listing the products vs. a product detail page. For details, see the [**Web scraping tutorial**](https://apify.com/docs/scraping/tutorial/introduction#the-start-url) in the Apify documentation. #### Link selector The **Link selector** (`linkSelector`) field contains a CSS selector that is used to find links to other web pages, i.e. `` elements with the `href` attribute. On every page loaded, the scraper looks for all links matching the **Link selector**. It checks that the target URL matches one of the [**Pseudo-URLs**](#pseudo-urls), and if so then adds the URL to the request queue, to be loaded by the scraper later. By default, new scrapers are created with the following selector that matches all links: ``` a[href] ``` If the **Link selector** is empty, page links are ignored, and the scraper only loads pages that were specified in the [**Start URLs**](#start-urls) input or that were manually added to the request queue by calling `context.enqueueRequest()` in the [**Page function**](#page-function). #### Pseudo-URLs The **Pseudo-URLs** (`pseudoUrls`) field specifies what kind of URLs found by [**Link selector**](#link-selector) should be added to the request queue. A pseudo-URL is simply a URL with special directives enclosed in `[]` brackets. Currently, the only supported directive is `[regexp]`, which defines a JavaScript-style regular expression to match against the URL. For example, the pseudo-URL `http://www.example.com/pages/[(\w|-)*]` will match all of the following URLs: - `http://www.example.com/pages/` - `http://www.example.com/pages/my-awesome-page` - `http://www.example.com/pages/something` If either `[` or `]` is part of the normal query string, it must be encoded as `[\x5B]` or `[\x5D]`, respectively. For example, the following pseudo-URL: ``` http://www.example.com/search?do[\x5B]load[\x5D]=1 ``` will match the URL: ``` http://www.example.com/search?do[load]=1 ``` Optionally, each pseudo-URL can be associated with user data that can be referenced from your [**Page function**](#page-function) using `context.request.userData` to determine what kind of page is currently loaded in the browser. Note that you don't have to use the **Pseudo-URLs** setting at all because you can completely control which pages the scraper will access by calling `context.enqueueRequest()` from your **[Page function](#page-function)**. #### Page function The **Page function** (`pageFunction`) field contains a single JavaScript function that enables the user to extract data from the web page, access its DOM, add new URLs to the request queue, and otherwise control Vanilla JS Scraper's operation. Example: ```javascript async function pageFunction(context) { const { document, request, response, kvStore } = context; // Use "document" and "window" almost just as you would in browser const pageTitle = document.querySelector('title').textContent; const items = document.querySelectorAll('div.item'); const itemArray = Array.from(items).map((item) => { return { title: item.querySelector('span.name').textContent, id: item.getAttribute('data-id'), }; }); const url = window.location; const responseHeaders = response.headers; // Use the kvStore API to add and retrieve values from // the key-value store await kvStore.set('new-headers', responseHeaders); // Return an object with the data extracted from the page. // It will be stored to the resulting dataset. return { pageTitle, itemArray, url, }; } ``` The code runs in [Node.js 16](https://nodejs.org/), and the function accepts a single argument, the `context` object, whose properties are listed below. The return value of the pageFunction must be an object representing the data extracted from the web page. The return value must be stringify-able to JSON, i.e. it can only contain basic types and no circular references. If you prefer not to extract any data from the page and skip it in the clean results, simply return an empty object: `{}`. The **Page function** supports the JavaScript ES6 syntax and is asynchronous, which means you can use the `await` keyword to wait for background operations to finish. To learn more about `async` functions, visit the [Mozilla documentation](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/async_function). Additionally, it is not recommended to delete the function declaration from the pageFunction's editor. **Properties of the `context` object:** - ##### **`window: Object`** This is not a fully-fledged window object, but supports many of the methods you already know, such as: ```JavaScript window.contentType window.location ``` - ##### **`document: Object`** This object is the starting point for traversing the DOM and extracting data from it. It supports the same methods you are likely already familiar with. > Note: You **CANNOT** manipulate the DOM with this document object. It simply will not work. Example: ```html ``` ```javascript document.querySelector('.movies > #fun-movie').textContent; //=> Fun Movie document.querySelector('ul .sad-movie').className; //=> sad-movie document.querySelector('li[class=horror-movie]').innerHTML; //=> Horror Movie ``` - ##### **`body: String|Buffer`** The body from the target web page. If the web page is in HTML or XML format, the `body` will be a string that contains the HTML or XML content. In other cases, the `body` with be a [Buffer](https://nodejs.org/api/buffer.html). If you need to process the `body` as a string, you can use the information from `contentType` property to convert the binary data into a string. Example: ```javascript const stringBody = context.body.toString(context.contentType.encoding); ``` - ##### **`crawler: Object`** A reference to the `CheerioCrawler` object, see [Apify SDK docs](https://sdk.apify.com/docs/api/cheerio-crawler) for more information. - ##### **`customData: Object`** Contains the object provided in the **Custom data** (`customData`) input field, which is useful for passing dynamic parameters to your scraper using API. - ##### **`userData: Object`** Contains the object provided in the **userData** (`userData`) when the request was added to the request queue either with **Start-URLs** or `context.enqueueRequest()` - ##### **`enqueueRequest(request, [options]): AsyncFunction`** Adds a new URL to the request queue, if it wasn't already there. The `request` parameter is an object containing details of the request, with properties such as `url`, `userData`, `headers` etc. For the full list of the supported properties, see the [`Request`](https://sdk.apify.com/docs/api/request) object's constructor in the Apify SDK documentation. Example: ```javascript await context.enqueueRequest({ url: 'https://www.example.com', userData: { hello: 'world' } }); await context.enqueueRequest('https://www.example2.com'); ``` > Note: If you only need to provide a URL, you don't need to place it inside of an object. - ##### **`kvStore: Object`** Represents an in-memory store that can be used to share data across page function invocations, e.g. state variables, API responses, or other data. Gives you access to the key-value store. The name of this store can be configured in **Advanced options**. Example: ```JavaScript let movies = await context.kvStore.get('cached-movies'); if (!movies) { movies = await fetch('http://example.com/movies.json'); await context.kvStore.set('cached-movies', movies); } console.dir(movies); ``` The kvStore object supports two methods: `get` and `set`. - ##### **`json: Object`** The parsed object from a JSON string if the response contains the content type `application/json`. - ##### **`request: Object`** An object containing information about the currently loaded web page, such as the URL, number of retries, a unique key, etc. Its properties are equivalent to the [`Request`](https://sdk.apify.com/docs/api/request) object in the Apify SDK. - ##### **`response: Object`** An object containing information about the HTTP response from the web server. Currently, it only contains the `status` and `headers` properties. For example: ```javascript { // HTTP status code status: 200, // HTTP headers headers: { 'content-type': 'text/html; charset=utf-8', 'date': 'Wed, 06 Nov 2019 16:01:53 GMT', 'cache-control': 'no-cache', 'content-encoding': 'gzip', } } ``` ### Proxy configuration The **Proxy configuration** (`proxyConfiguration`) option enables you to set proxies that will be used by the scraper in order to prevent its detection by target web pages. You can use both the [Apify Proxy](https://apify.com/proxy) and custom HTTP or SOCKS5 proxy servers. The following table lists the available options of the proxy configuration setting:
None The scraper will not use any proxies. All web pages will be loaded directly from IP addresses of Apify servers running on Amazon Web Services.
Apify Proxy (automatic) The scraper will load all web pages using the Apify Proxy in automatic mode. In this mode, the proxy uses all proxy groups that are available to the user. For each new web page it automatically selects the proxy that hasn't been used in the longest time for the specific hostname in order to reduce the chance of detection by the web page. You can view the list of available proxy groups on the Proxy page in Apify Console.
Apify Proxy (selected groups) The scraper will load all web pages using the Apify Proxy with specific groups of target proxy servers.
Custom proxies

The scraper will use a custom list of proxy servers. The proxies must be specified in the scheme://user:password@host:port format. Multiple proxies should be separated by a space or new line. The URL scheme can be either http or socks5. User and password might be omitted, but the port must always be present.

Example: 

http://bob:password@proxy1.example.com:8000
            http://bob:password@proxy2.example.com:8000
The proxy configuration can be set programmatically when calling the actor using the API by setting the `proxyConfiguration` field. It accepts a JSON object with the following structure: ```javascript { // Indicates whether to use the Apify Proxy or not. "useApifyProxy": Boolean, // Array of Apify Proxy groups, only used if "useApifyProxy" is true. // If missing or null, the Apify Proxy will use automatic mode. "apifyProxyGroups": String[], // Array of custom proxy URLs, in "scheme://user:password@host:port" format. // If missing or null, custom proxies are not used. "proxyUrls": String[], } ``` ### Results The scraping results returned by [**Page function**](#page-function) are stored in the default dataset associated with the actor run, from where you can export them to formats such as JSON, XML, CSV or Excel. For each object returned by the [**Page function**](#page-function), Vanilla JS Scraper pushes one record into the dataset and extends it with URL of the web page where the results come from. For example, if your page function returned the following object: ```JavaScript { message: 'Hello world!'; } ``` The full object stored in the dataset would look like this: ```JSON { "page": "https://www.example.com", "message": "Hello world!" } ``` If you are to return an object with a key of `page`, your data will overwrite the default metadata value. To download the results, call the [Get dataset items](https://apify.com/docs/api/v2#/reference/datasets/item-collection) API endpoint: ``` https://api.apify.com/v2/datasets/[DATASET_ID]/items?format=json ``` where `[DATASET_ID]` is the ID of the actor's run dataset, in which you can find the Run object returned when starting the actor. Alternatively, you'll find the download links for the results in Apify Console. To get the results in other formats, set the `format` query parameter to `xml`, `xlsx`, `csv`, `html`, etc. For more information, see [Datasets](https://apify.com/docs/storage#dataset) in documentation or the [Get dataset items](https://apify.com/docs/api/v2#/reference/datasets/item-collection) endpoint in Apify API reference. ### Additional resources Congratulations, you've learned how Vanilla JS Scraper works! You might also want to see these other resources: - [Web scraping tutorial](https://apify.com/docs/scraping) - An introduction to web scraping with Apify. - **Cheerio Scraper** ([apify/cheerio-scraper](https://apify.com/apify/cheerio-scraper)) - Apify's basic tool for web crawling and scraping. It uses a full Chrome browser to render dynamic content. - **Web Scraper** ([apify/web-scraper](https://apify.com/apify/web-scraper)) - A higher level tool for scraping dynamic websites within the context of the browser - **Puppeteer Scraper** ([apify/puppeteer-scraper](https://apify.com/apify/puppeteer-scraper)) - An actor similar to Web Scraper, which provides lower-level control of the underlying [Puppeteer](https://github.com/GoogleChrome/puppeteer) library and the ability to use server-side libraries. - [Actors documentation](https://apify.com/docs/actor) - Documentation for the Apify Actors cloud computing platform. - [Apify SDK](https://sdk.apify.com) - Learn how to build a new web scraping actor from scratch using the world's most popular web crawling and scraping library for Node.js. # Actor input Schema ## `requests` (type: `array`): A static list of URLs to scrape.

For details, see the Start URLs section in the README. ## `pseudoUrls` (type: `array`): Specifies what kind of URLs found by the Link selector should be added to the request queue. A pseudo-URL is a URL with regular expressions enclosed in \[] brackets, e.g. http://www.example.com/\[.\*].

If Pseudo-URLs are omitted, the actor enqueues all links matched by the Link selector.

For details, see Pseudo-URLs in README. ## `linkSelector` (type: `string`): A CSS selector stating which links on the page (\ elements with href attribute) shall be followed and added to the request queue. To filter the links added to the queue, use the Pseudo-URLs field.

If the Link selector is empty, the page links are ignored.

For details, see the Link selector in README. ## `pageFunction` (type: `string`): A JavaScript function that is executed for every page loaded server-side in Node.js 12. Use it to scrape data from the page, perform actions or add new URLs to the request queue.

For details, see Page function in README. ## `preNavigationHooks` (type: `string`): Async functions that are sequentially evaluated before the navigation. Good for setting additional cookies or browser properties before navigation. The function accepts two parameters, `crawlingContext` and `requestAsBrowserOptions`, which are passed to the `requestAsBrowser()` function the crawler calls to navigate. ## `postNavigationHooks` (type: `string`): Async functions that are sequentially evaluated after the navigation. Good for checking if the navigation was successful. The function accepts `crawlingContext` as the only parameter. ## `proxy` (type: `object`): Specifies proxy servers that will be used by the scraper in order to hide its origin.

For details, see Proxy configuration in README. ## `debug` (type: `boolean`): Include debug messages in the log? ## `maxConcurrency` (type: `integer`): Specifies the maximum number of pages that can be processed by the scraper in parallel. The scraper automatically increases and decreases concurrency based on available system resources. This option enables you to set an upper limit, for example to reduce the load on a target web server. ## `maxRequestRetries` (type: `integer`): The maximum number of times the scraper will retry to load each web page on error, in case of a page load error or an exception thrown by the Page function.

If set to 0, the page will be considered failed right after the first error. ## `pageLoadTimeoutSecs` (type: `integer`): The maximum amount of time the scraper will wait for a web page to load, in seconds. If the web page does not load in this timeframe, it is considered to have failed and will be retried (subject to Max page retries), similarly as with other page load errors. ## `pageFunctionTimeoutSecs` (type: `integer`): The maximum amount of time the scraper will wait for the Page function to execute, in seconds. It is always a good idea to set this limit, to ensure that unexpected behavior in page function will not get the scraper stuck. ## `ignoreSslErrors` (type: `boolean`): If enabled, the scraper will ignore SSL/TLS certificate errors. Use at your own risk. ## `additionalMimeTypes` (type: `array`): A JSON array specifying additional MIME content types of web pages to support. By default, Cheerio Scraper supports the text/html and application/xhtml+xml content types, and skips all other resources. For details, see Content types in README. ## `datasetName` (type: `string`): Name or ID of the dataset that will be used for storing results. If left empty, the default dataset of the run will be used. ## `keyValueStoreName` (type: `string`): Name or ID of the key-value store that will be used for storing records. If left empty, the default key-value store of the run will be used. ## `customData` (type: `object`): A custom JSON object that is passed to the Page function as context.customData. This setting is useful when invoking the scraper via API, in order to pass some arbitrary parameters to your code. ## Actor input object example ```json { "requests": [ { "url": "https://apify.com" } ], "pseudoUrls": [ { "purl": "https://apify.com[(/[\\w-]+)?]" } ], "linkSelector": "a[href]", "pageFunction": "async function pageFunction(context) {\n const { window, document, crawler, enqueueRequest, request, response, userData, json, body, kvStore, customData } = context;\n\n const title = document.querySelector('title').textContent\n\n const responseHeaders = response.headers\n\n return {\n title,\n responseHeaders\n };\n}", "preNavigationHooks": "// We need to return array of (possibly async) functions here.\n// The functions accept two arguments: the \"crawlingContext\" object\n// and \"requestAsBrowserOptions\" which are passed to the `requestAsBrowser()`\n// function the crawler calls to navigate..\n[\n async (crawlingContext, requestAsBrowserOptions) => {\n // ...\n }\n]", "postNavigationHooks": "// We need to return array of (possibly async) functions here.\n// The functions accept a single argument: the \"crawlingContext\" object.\n[\n async (crawlingContext) => {\n // ...\n },\n]", "proxy": { "useApifyProxy": true }, "debug": false, "maxConcurrency": 50, "maxRequestRetries": 3, "pageLoadTimeoutSecs": 60, "pageFunctionTimeoutSecs": 60, "ignoreSslErrors": false, "additionalMimeTypes": [], "customData": {} } ``` # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "requests": [ { "url": "https://apify.com" } ], "pseudoUrls": [ { "purl": "https://apify.com[(/[\\w-]+)?]" } ], "linkSelector": "a[href]", "pageFunction": async function pageFunction(context) { const { window, document, crawler, enqueueRequest, request, response, userData, json, body, kvStore, customData } = context; const title = document.querySelector('title').textContent const responseHeaders = response.headers return { title, responseHeaders }; }, "preNavigationHooks": `// We need to return array of (possibly async) functions here. // The functions accept two arguments: the "crawlingContext" object // and "requestAsBrowserOptions" which are passed to the `requestAsBrowser()` // function the crawler calls to navigate.. [ async (crawlingContext, requestAsBrowserOptions) => { // ... } ]`, "postNavigationHooks": `// We need to return array of (possibly async) functions here. // The functions accept a single argument: the "crawlingContext" object. [ async (crawlingContext) => { // ... }, ]`, "proxy": { "useApifyProxy": true }, "additionalMimeTypes": [], "customData": {} }; // Run the Actor and wait for it to finish const run = await client.actor("mstephen190/vanilla-js-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "requests": [{ "url": "https://apify.com" }], "pseudoUrls": [{ "purl": "https://apify.com[(/[\\w-]+)?]" }], "linkSelector": "a[href]", "pageFunction": """async function pageFunction(context) { const { window, document, crawler, enqueueRequest, request, response, userData, json, body, kvStore, customData } = context; const title = document.querySelector('title').textContent const responseHeaders = response.headers return { title, responseHeaders }; }""", "preNavigationHooks": """// We need to return array of (possibly async) functions here. // The functions accept two arguments: the \"crawlingContext\" object // and \"requestAsBrowserOptions\" which are passed to the `requestAsBrowser()` // function the crawler calls to navigate.. [ async (crawlingContext, requestAsBrowserOptions) => { // ... } ]""", "postNavigationHooks": """// We need to return array of (possibly async) functions here. // The functions accept a single argument: the \"crawlingContext\" object. [ async (crawlingContext) => { // ... }, ]""", "proxy": { "useApifyProxy": True }, "additionalMimeTypes": [], "customData": {}, } # Run the Actor and wait for it to finish run = client.actor("mstephen190/vanilla-js-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "requests": [ { "url": "https://apify.com" } ], "pseudoUrls": [ { "purl": "https://apify.com[(/[\\\\w-]+)?]" } ], "linkSelector": "a[href]", "pageFunction": "async function pageFunction(context) {\\n const { window, document, crawler, enqueueRequest, request, response, userData, json, body, kvStore, customData } = context;\\n\\n const title = document.querySelector('\''title'\'').textContent\\n\\n const responseHeaders = response.headers\\n\\n return {\\n title,\\n responseHeaders\\n };\\n}", "preNavigationHooks": "// We need to return array of (possibly async) functions here.\\n// The functions accept two arguments: the \\"crawlingContext\\" object\\n// and \\"requestAsBrowserOptions\\" which are passed to the `requestAsBrowser()`\\n// function the crawler calls to navigate..\\n[\\n async (crawlingContext, requestAsBrowserOptions) => {\\n // ...\\n }\\n]", "postNavigationHooks": "// We need to return array of (possibly async) functions here.\\n// The functions accept a single argument: the \\"crawlingContext\\" object.\\n[\\n async (crawlingContext) => {\\n // ...\\n },\\n]", "proxy": { "useApifyProxy": true }, "additionalMimeTypes": [], "customData": {} }' | apify call mstephen190/vanilla-js-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,mstephen190/vanilla-js-scraper" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/URJ7uUMQ8DDCMiUfW/builds/KNr2xqkLyGdERqbgE/openapi.json