Response Codes

Scrapehero Cloud APIs will return the following HTTP Response Codes from API requests. You should inspect the response code that the API returns to determine whether your request has been successful or not.

The billable status codes are 200 and 404.

HTTP Response Code	Description
200 Success	Request processed successfully.
400 Bad Request	The request you specified is invalid. The details of the error are shown in the JSON body of the response. The most common cause of an HTTP 400 response is passing invalid parameters to the APIs, or combinations of parameter values that are not supported.
401 Unauthorized	The API Key supplied with your request is not valid.
404 Not Found	The request URL you specified is invalid. Check the request URL you are using (if you receive an HTTP 404 it's likely the path you're using is not correct). It could also be you are using an incorrect HTTP verb - i.e. making an HTTP POST where a GET is required.
429 Too Many Requests	If you are using a plan or accessing an API endpoint that has rate limits—meaning there is a cap on the number of requests you can make within a certain time frame—and you exceed that limit, the server will respond with an HTTP 429 status code. This status means "Too Many Requests" and indicates that you've hit the allowed threshold. To handle this properly and avoid hitting the rate limit, you can implement delays or backoff strategies in your code, such as waiting a certain amount of time before retrying the request. This helps ensure smoother interaction with the API and compliance with the rate limits.
500 Internal Server Error	There was a problem processing your request. You should retry your request after a delay and if you continue to experience the same result please contact our support team.