Hyperbrowser exposes endpoints for starting a crawl request and for getting it's status and results. By default, crawling is handled in an asynchronous manner of first starting the job and then checking it's 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
npminstall@hyperbrowser/sdk
or
yarnadd@hyperbrowser/sdk
pipinstallhyperbrowser
Usage
import { Hyperbrowser } from"@hyperbrowser/sdk";import { config } from"dotenv";config();constclient=newHyperbrowser({ apiKey:process.env.HYPERBROWSER_API_KEY,});constmain=async () => {// Handles both starting and waiting for crawl job responseconstcrawlResult=awaitclient.crawl.startAndWait({ url:"https://hyperbrowser.ai", });console.log("Crawl result:", crawlResult);};main();
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.
{"jobId":"962372c4-a140-400b-8c26-4ffe21d9fb9c"}
The Get Crawl Job GET /crawl/{jobId} will return the following data:
{"jobId":"962372c4-a140-400b-8c26-4ffe21d9fb9c","status":"completed","totalCrawledPages":2,"totalPageBatches":1,"currentPageBatch":1,"batchSize":20,"data": [ {"url":"https://example.com","status":"completed","metadata": {"title":"Example Page","description":"A sample webpage" },"markdown":"# Example Page\nThis is content...", }, ... ]}
The status of a crawl job can be one of pending, running, completed, failed . There can also be other optional fields like error with an error message if an error was encountered, and html and links in the data object depending on which formats are requested for the request.
Unlike the scrape endpoint, the crawl endpoint returns a list in the data field with the all the pages that were crawled in the current page batch. The SDKs also provide a function which will start the crawl job, wait until it's complete, and return all the crawled pages for the entire crawl.
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.
The crawl endpoint provides additional parameters you can provide to tailor the crawl to your needs. You can narrow down the pages crawled by setting a limit to the maximum number of pages visited, only including paths that match a certain pattern, excluding paths that match another pattern, etc.
import { Hyperbrowser } from"@hyperbrowser/sdk";import { config } from"dotenv";config();constclient=newHyperbrowser({ apiKey:process.env.HYPERBROWSER_API_KEY,});constmain=async () => {// Handles both starting and waiting for crawl job responseconstcrawlResult=awaitclient.crawl.startAndWait({ url:"https://hyperbrowser.ai", maxPages:5, includePatterns: ["/blogs/*"], });console.log("Crawl result:", crawlResult);};main();
You can also provide configurations for the session that will be used to execute the crawl job just as you would when creating a new session itself. These could include using a proxy or solving CAPTCHAs.
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.