Render dynamic websites to static HTML.

Render dynamic content from web pages to static HTML with Headless Chrome in the cloud.

Just specify target geolocation for sending requests to route them for you via a worldwide proxy network.

Dataflow Kit Scraper

Headless Chrome as a service.

Actions

Generate "ready-to-run" code for your favourite language.


                    
 Copy the snippet and give it a go! 
Parameter Description
api_key API Key is used to authenticate with the API - You can find it in your Account Dashboard
URL Specify URL to download a web page.
Proxy Select country to locate proxy to pass requests through to target web sites.
Fetcher type If set to "Base", regular pages are downloaded "as is" using standard HTTP requests.
But for the most cases choose "Chrome" fetcher type to render Javascript-driven web pages.
Read more...
Wait Delay Wait Delay parameter is used to specify a custom delay (in seconds).
This may be useful if certain elements of the web site need to be rendered after initial page load.
Actions Actions can be used to automate manual workflows while rendering web pages. They simulate real-world human interaction with pages.

Why Use DFK JS Rendering Service.

Base Fetcher

"Base Fetcher" is suitable for processing server-side rendered pages where the HTML in the HTTP response contains all content.

Crawling a URL with "Base fetcher" takes fewer resources and works faster than rendering HTML with "Chrome fetcher."

Requesting static HTML pages is always cheaper ...

But...

Chrome Fetcher

JavaScript Frameworks like Angular, React, Vue.js used widely for building modern web applications. They consist of HTML + JS code. HTML initially does not contain all the actual content. It loads dynamically after rendering JavaScript code.

So scraping such pages 'as is' is useless for most cases.

The headless Chrome browser is used by "Chrome fetcher" for rendering dynamic content and returning it as a static HTML. It renders websites in the same way as a real browser would do it.

V/S

Automation of manual workflows.

Of course, we don't intend only to render JavaScript driven web pages but to perform tasks with them.

Doing actions helps you to be closer to the desired data.

Actions are performed by scraper upon visiting a Web page, and it simulates real-world human interaction with the page.

You can use DFK API for executing simple actions after rendering a web page:

"Input" action

Specify Input CSS Selector and Input Text to perform search queries, or fill forms.

"Click" action

Click on an element with the specified CSS Selector.

"Wait" action

Wait for the specific DOM elements you want to manipulate.

"Scroll" action

Automatically scroll a page down to load more content, simulating user interaction with infinite scrolled pages.

Let machines do the grunt work and let humans do what they do best.

Proxy and Geo-Targetting.

Dataflow kit Proxies pool is useful to get around content download restrictions from specific websites.

Choose the one from 100+ supported global locations to send your web scraping API requests.

Or select "country-any" to use random geo-targets.

Dataflow kit API.

Render JavaScript web pages right from your application.

Just send an API request specifying the desired web page and parameters.

Easily integrate DFK API with your applications using your favorite framework or language.

Cloud file storage.

Dataflow Kit storage is designed according to the best industry practices. We use S3 compatible storage, giving you high availability and scalability.

Store from a few records to a few hundred million, with the same low latency and high reliability.

And besides, you can easily upload your data to the following cloud storages:

Google Drive,
Dropbox,
Microsoft Onedrive

Challenges with Rendering JS Pages?
We will help you to solve your problem.

Contact us