Raw HTML Scraper API

Retrieve the HTML of a public web page and keep control of the parsing. Use the standard fetch mode for server-rendered pages, or enable JavaScript rendering for pages that need a browser. Raw HTML returns page markup, not pre-extracted product, property or accommodation fields.

Start for free Read the documentation1,000 free credits included

Data format: HTML
Starting credits: 1
Request: synchronous POST
Free credits: 1,000

Choose how to retrieve your HTML

One endpoint, with optional rendering and proxy settings. Choose the mode your target page needs.

Use case	Option	Returns
Standard fetch	`options.useChrome: false`	Page HTML without browser rendering
JavaScript rendering	`options.useChrome: true`	Browser-rendered HTML
Premium proxy	`options.premiumProxy: true`	HTML fetched through a premium proxy

Raw HTML returns markup, not a predefined data schema. Browser rendering is optional.

Connect Raw HTML to your workflow

This page is the Raw HTML API guide itself. There are no separate dedicated scraper pages to list: use the endpoint below and parse the HTML in your application.

Read the API documentation

Request options and integration examples

Try your target in the live test

Inspect a response before writing your parser

Start with 1,000 free creditsTest representative targets and inspect the returned data before scaling your requests.

Create an account

How a Raw HTML API call works

Raw HTML requests are synchronous: submit a public URL and read page markup from the same response.

STEP 1Send the public URL and enable browser rendering only when the target requires it. Authenticate with your username and API key.

curl --request POST 'https://api.scraping-bot.io/scrape/raw-html' \
  --user "YOUR_USERNAME:YOUR_API_KEY" \
  --header 'Content-Type: application/json' \
  --data '{
  "url": "https://example.com/",
  "options": {
    "useChrome": false,
    "premiumProxy": false
  }
}'

Replace example.com with your public target page. Set options.useChrome to true only when browser rendering is needed.

STEP 2Read the response as HTML text, then parse the fields your application needs with your own selector logic.

Response formatRaw page markup; your application defines the extracted fields

Request parameters

Parameter	Requirement	Purpose
`url`	Required	Full public page URL, including https://.
`options.useChrome`	Optional	Render JavaScript when the page needs a browser.
`options.premiumProxy`	Optional	Use a premium proxy for targets that require it.
`options.proxyCountry`	Optional	Country targeting with a premium proxy; availability depends on the target.
`options.waitFor`	Optional	Additional browser wait in milliseconds, capped at 10,000 by the route

See the documentation for the complete request and response examples.

Credits, refunds and limits

Scenario	Response	Credits
Successful request	HTML text	Consumed at the applicable plan and option rate
Handled scraping failure	Error; inspect the response before retrying	Refunded by the failure handler

Current plans start at 1 credit for standard HTML retrieval. Legacy plans calculate option costs differently. Browser rendering is optional; Raw HTML does not always mean rendered HTML.

Current-plan mode	Credits	Options
Standard request	1	No browser rendering or premium proxy
JavaScript rendering	5	options.useChrome: true
Premium proxy	10	options.premiumProxy: true
Rendering + premium proxy	25	Both options enabled

Request limits depend on your plan. Respect rate-limit responses, avoid uncontrolled retries and check target-specific proxy requirements. Additional targeting or special-domain rules can affect costs; confirm your configuration in the pricing plans and documentation.

Raw HTML or a structured scraper API?

Raw HTML API

Choose Raw HTML when you need page markup, custom fields or full control over your selectors.

HTML text rather than predefined JSON fields
You maintain the parser and handle target layout changes
Optional browser rendering and premium proxies

Structured APIs

Get parsed JSON fields with an endpoint tailored to your data type.

Retail for product fields
Real Estate for property listings
Booking for accommodation data

Questions about the Raw HTML API

Does Raw HTML extract structured fields for me?: No. It returns HTML. Use your own parser, or choose Retail, Real Estate or Booking when you need their structured fields.
Is JavaScript rendering always enabled?: No. The standard mode retrieves HTML without a browser. Set options.useChrome to true when the content depends on JavaScript.
Do I need to poll a responseId?: No. Read the HTML from the POST response. The responseId polling workflow belongs to the asynchronous Social Media endpoint.
Which data should I collect?: Use public pages and collect only the data needed for your use case. Public availability does not remove privacy, copyright or contractual obligations; assess those before using or republishing the results.

4.9

★★★★★

133 Google reviews

★★★★★

I've tested dozens of web scraping tools in my life, and they all had annoying limitations. With Scraping Bot, I don't have to worry about getting blocked or not having specialized technical knowledge! Highly recommend it :)

Orphée de Bouard

Other categories

Social Media E-commerce & Retail Real Estate Booking & Travel Search Engine

Start scraping raw html today

Try ScrapingBot with 1,000 free credits. No card required.

Create an account Talk to us