Billing Information
Last updated
Last updated
Web Unblocker counts both request and response traffic. Request traffic refers to data sent to the target URL, while response traffic refers to the data received from the target URL.
All responses from the target site with 2xx or 4xx status codes are counted as successful.
All other responses are counted as unsuccessful.
For more information about response codes, please refer to the Response Codes table.
If the response contains 2xx or 4xx status codes, and the result doesn’t contain expected information, we still count it as a successful result.
You will be billed for both request and response traffic of successfully extracted data.
Failed attempts to scrape due to our system errors (5xx status codes) won’t be included in your traffic usage calculation, and you won’t be billed for that.
If a request results in a failed attempt due to a fault or error on your side, you will still be billed.
Please find a few billing case examples below:
You make a request, and it takes three attempts for Web Unblocker to unblock the website. You will be billed only for the traffic consumed during the last attempt, which was successful, in this case, for 201 kB of consumed traffic.
You make a request to Web Unblocker, and the response is unsuccessful due to our error, e.g., we have reached our internal retry limit. In this case, you will not be billed for this request.
You make a request to Web Unblocker, and the response is unsuccessful due to an error on your side. You will be billed for the traffic consumed during the attempt, which was unsuccessful, in this case, for 51 kB of consumed traffic.
Please note that if JavaScript rendering is applied when scraping, total traffic for the job may be higher than the size of the HTML file alone due to the external calls the website is executing in order to load additional data.
