DocumentationAPI DetailsScrape URLReal Browser

Using a Real Browser

By default, ScrAPI uses a fast HTTP client that does not execute JavaScript. For websites that rely on client-side rendering - such as single-page applications (SPAs), React/Vue/Angular sites, or pages with dynamically loaded content - you need a real browser to get the fully rendered HTML.

Set the useBrowser parameter to true to use a full headless browser that executes JavaScript and waits for the page to finish loading before returning the final rendered document.

When To Use This

  • JavaScript-rendered pages - SPAs, React, Vue, Angular, or any site that loads content dynamically via JavaScript.
  • Pages with lazy-loaded content - Content that only appears after the initial page load completes.
  • Sites requiring browser fingerprints - Some sites block non-browser HTTP clients by checking for browser-specific headers, cookies, or JavaScript execution.
  • Prerequisite for advanced features - Browser commands, captcha solving, screenshots, PDFs, and video recording all require a real browser.

Tip: If the page you need doesn’t require JavaScript and loads fine with a simple HTTP request, skip this option - it’s faster and costs fewer credits (1 credit vs. 5 credits).

Browser Behavior

When using a real browser:

  • JavaScript is fully executed and the DOM is rendered before content extraction.
  • Ads and web trackers are automatically blocked.
  • Popup dialogs are automatically cancelled. Set acceptDialogs to true if you need to accept them instead.
  • The browser includes anti-detection measures to mimic a real user session - realistic viewport, user agent, and browser fingerprint.

Example Request

GET https://api.scrapi.tech/v1/scrape?url=https://deventerprise.com&useBrowser=true

POST https://api.scrapi.tech/v1/scrape

{
  "url": "https://deventerprise.com",
  "useBrowser": true,
  "acceptDialogs": false
}

Related Features

  • Browser Commands - Click, type, scroll, and run JavaScript after the page loads.
  • Captcha Solving - Automatically solve CAPTCHAs detected in the browser.
  • Screenshots - Capture the final rendered page as a PNG image.
  • Sessions - Persist browser state (cookies, IP) across multiple requests.
  • Credit Usage - Browser rendering costs 5 credits per request.

Testing

Test this request in the Playground or view the OpenAPI specification.

Getting StartedBrowser Commands