Page2API

Before designing this API, I was scraping the web from time to time, and 10 out of 10 - I was building my scrapers to get the data I need, and even knowing that there is plenty of APIs available, I couldn’t see myself using any of it.

Why?
Because It was much easier to write my own scrapers from scratch every time, rather than using something ready.

Reason - the way those APIs are built.

What is their main problem?
They are not intuitive and easy to use.

So, I’ve made the following commitment:
I must build a Web Scraping API that will satisfy the following requirements:

• Intuitive and powerful API (easy and fun to use)
• Asynchronous scraping (long-running scraping sessions)
• Scheduled scraping (automatic scraping on schedule)
• Javascript rendering (interact with js-rich pages)
• Custom browser scenarios (execute custom JS, handle pagination, and more)
• Fast and reliable proxies (never get blocked)