ScrapingBee Reviews

Comments: Pros I found this proxy service more effective compared to previous ones that were being used. It is fast and effiecient Cons sometimes too many internal server errors

Comments: Pros Easy to use. It is a full-featured all in one proxy solution where it can handle captchas, proxy rotation, JS rendering, geolocation and so on. Cons The only thing that bothers me is their pricing system for premium site like Amazon, Google etc. One of their competitor ScraperAPI have the same pricing plan for all sites. So charging extra for scraping data from permium sites like Amazon or Google is really what I don't like at all.

Comments: Pros It takes about 10 minutes to get up and running making requests and they make it super easy to get started with lots of examples. That said, pretty much all that matters is that it works. And it works really well. We tried a number of other things to keep our crawlers working but none works as well or as universally as scraping bee. The separation of premium vs regular proxies means we are able to optimize costs by only using regular proxies for sites that don't require premium ones. Cons None.

Comments: I had a scraping project that used many of the features in ScrapingBee. I wanted to scrape about 600k .json documents from a public API. I also wanted screenshots of those pages, and to extract various data from the corresponding HTML pages. ScrapingBee offered good options for all the cases. Finally, I wanted to get the Instagram follower counts for about 200k Instagram accounts. Instagram is super aggressive about blocking, but by using premium proxies, and resetting the session on each call, I was successful here too. That site I was scraping does block you after several thousand pages from a single IP, so I needed to use a proxy service. I never got blocked once I was using Scraping bee. Pros It has a well-documented, fairly easy-to-use API that covers a whole range of scraping situations. (I talk more about that below). You can choose Javascript rendering or not, residential or data-center proxies, screenshots, etc. I was never blocked once during my scraping. They are a small, responsive startup. I did run into a reproducible bug with their data extraction API, but they clearly made it a priority and had a new release fixing the problem the very next day. (Since they're in France, time zones worked out well and that was really first thing the next morning for me.) Cons It would have been nice to be able to get a screenshot and the data on the page at the same time. At present, you can only get one or the other, so I had to run it twice.

Pros: It has a well-documented, fairly easy-to-use API that covers a whole range of scraping situations. (I talk more about that below). You can choose Javascript rendering or not, residential or data-center proxies, screenshots, etc. I was never blocked once during my scraping. They are a small, responsive startup. I did run into a reproducible bug with their data extraction API, but they clearly made it a priority and had a new release fixing the problem the very next day. (Since they're in France, time zones worked out well and that was really first thing the next morning for me.) Cons: It would have been nice to be able to get a screenshot and the data on the page at the same time. At present, you can only get one or the other, so I had to run it twice. I had a scraping project that used many of the features in ScrapingBee. I wanted to scrape about 600k .json documents from a public API. I also wanted screenshots of those pages, and to extract various data from the corresponding HTML pages. ScrapingBee offered good options for all the cases. Finally, I wanted to get the Instagram follower counts for about 200k Instagram accounts. Instagram is super aggressive about blocking, but by using premium proxies, and resetting the session on each call, I was successful here too. That site I was scraping does block you after several thousand pages from a single IP, so I needed to use a proxy service. I never got blocked once I was using Scraping bee.

Pros: Easy to use. It is a full-featured all in one proxy solution where it can handle captchas, proxy rotation, JS rendering, geolocation and so on. Cons: The only thing that bothers me is their pricing system for premium site like Amazon, Google etc. One of their competitor ScraperAPI have the same pricing plan for all sites. So charging extra for scraping data from permium sites like Amazon or Google is really what I don't like at all.

Pros: It takes about 10 minutes to get up and running making requests and they make it super easy to get started with lots of examples. That said, pretty much all that matters is that it works. And it works really well. We tried a number of other things to keep our crawlers working but none works as well or as universally as scraping bee. The separation of premium vs regular proxies means we are able to optimize costs by only using regular proxies for sites that don't require premium ones. Cons: None.

Pros: I found this proxy service more effective compared to previous ones that were being used. It is fast and effiecient Cons: sometimes too many internal server errors

Pros: It has a well-documented, fairly easy-to-use API that covers a whole range of scraping situations. (I talk more about that below). You can choose Javascript rendering or not, residential or data-center proxies, screenshots, etc. I was never blocked once during my scraping. They are a small, responsive startup. I did run into a reproducible bug with their data extraction API, but they clearly made it a priority and had a new release fixing the problem the very next day. (Since they're in France, time zones worked out well and that was really first thing the next morning for me.) Cons: It would have been nice to be able to get a screenshot and the data on the page at the same time. At present, you can only get one or the other, so I had to run it twice.