The API will return a specific status code after every request depending on whether the request was successful, failed or some other error occurred.
To avoid timing out your request remember to set your timeout to 300 seconds.
In cases where a request fails after 300 seconds, you will not be charged for the unsuccessful request. You are only charged for successful requests. We are considering successful requests that have 200 status code & status: "ok" in the response JSON.

​
Status Codes

CodeDetails
200Successful response.
404Requested page does not exists.
500HasData server error. If you received 500 status code retry request, if the problem is not solved contact our support.
429You are sending requests too fast, and exceeding your concurrency limit.
403You have used app all your API credits.
401Invalid API key.

​
Handling Occasional Errors

In rare cases (1–2% of requests), especially on harder-to-scrape websites, a request might fail due to temporary issues or anti-bot systems.
  • Automatic Retry: Set up your code to retry failed requests. Most of the time, a retry will succeed.
  • Consistent Failures: If a request keeps failing, double-check your parameters and request structure.
  • Anti-Bot Detection: If you’re consistently getting blocked by an anti-bot system, open a support ticket—we’ll take a look and work on a bypass for you.
These situations are uncommon, but it’s a good idea to handle errors gracefully to ensure smooth data collection.