Crawlbase’s Frequently Asked Questions

At the moment the only way to use Crawlbase is by integrating it to your product or service, therefore you will need to know development or know/pay someone which can help you.

Please note that we have some very easy to integrate libraries.

You can get the API keys or request tokens from the Crawlbase Account Documentation page.

https://crawlbase.com/dashboard/account/docs

By default a request is retried 110 times for a period of 48 hours from the first time it starts to be processed.

The 30 URLs-per-second limit applies to LinkedIn crawls. For other websites, we can evaluate and potentially increase the limit on a case-by-case basis. Please contact us to discuss your specific needs.

Yes, the Smart Proxy can be used for HTTPS websites, but the connection to the proxy must be done with http. So when connecting to the proxy use http://smartproxy.crawlbase.com and not https://smartproxy.crawlbase.com.

All HTTPS traffic that you send to any website using the Smart Proxy, will continue to be securely transfered and we won't be able to access it in any way.

We want to offer more than just a list or lists of proxies, therefore our API and Crawler products are built on top of thousands of residential and datacenter worldwide proxies combined with artificial intelligence plus our engineering team which helps delivering the best data results possible. If you are looking just for proxies and you don't want to get any of the other benefits, we recommend that you use the Smart Proxy

Yes, you can change your account email address. To do so, visit the Account page and look for the "Change email address" option. After updating your email address, you will receive a confirmation email at the new address. Please confirm the change by following the instructions in the email.

Yes you can use the free requests for javaScript or normal requests.

"Waiting" means that your requests are in your crawler queue waiting to be processed. "Concurrent crawlers" are the requests that are being crawled at the same time. Concurrent crawlers gets increased by our system if you have many pages to crawl, we also monitor crawlers and increase or decrease the concurrency depending on the pool. "Sets to be retried" are your requests that failed for any reason, they land in your crawler retry queue and are processed with a retry rate up until maximum 110 retries.

If your Crawler callback is down, you are notified by email, your crawlers get paused and your last failed request due to downtime at your endpoint, is set to be retried. Your crawlers get resumed when your endpoint becomes available automatically. Our monitoring system checks your endpoint every minute.