Skip to main content
The Crawl API allows you to crawl websites and get data from multiple pages in a single request. Starting from a URL, it can navigate through the site and extract content from linked pages.
For detailed usage, checkout the Crawl API Reference.
Hyperbrowser exposes endpoints for starting a crawl request and for getting its status and results. By default, crawling is handled in an asynchronous manner of first starting the job and then checking its status until it is completed. However, with our SDKs, we provide a simple function that handles the whole flow and returns the data once the job is completed.

Installation

Usage

Response

The Start Crawl Job POST /crawl endpoint will return a jobId in the response which can be used to get information about the job in subsequent requests.
The Get Crawl Job Status GET /crawl/{jobId}/status will return the following data:
The Get Crawl Job GET /crawl/{jobId} will return the following data:
The status of a crawl job can be one of pending, running, completed, failed. The results will be an array of scraped pages in the data field.
Each crawled page has it’s own status of completed or failed and can have it’s own error field, so be cautious of that.
To see the full schema, checkout the API Reference.

Crawl Options

You can configure various options for the crawl job:
  • maxPages: Maximum number of pages to crawl (default: 10, max: 100)
  • followLinks: Whether to follow links on the crawled pages (default: true)
  • ignoreSitemap: Whether to ignore the sitemap (default: false)

Session Configurations

You can also provide configurations for the session that will be used to execute the crawl job, such as using a proxy or solving CAPTCHAs. To see all the different available session parameters, checkout the API Reference or Session Parameters.
Using proxy and solving CAPTCHAs will slow down the crawl so use it only if necessary.

Scrape Configurations

You can also provide optional scrape options for the crawl job such as the formats to return, only returning the main content of the page, setting the maximum timeout for navigating to a page, etc.
Hyperbrowser’s CAPTCHA solving and proxy usage features require being on a PAID plan.
For a full reference on the crawl endpoint, checkout the API Reference.