Reference
Response Codes
1 min
response codes value serp will return the following http response codes from api requests you should inspect the response code that value serp returns to determine whether your request has been successful or not http response code description 200 success request processed successfully 402 payment required your value serp account has either run out of available credits (try enabling overage or upgrading your plan), or there is a payment problem 429 too many requests if you are on a plan with a rate limit, or making a call on an endpoint that is rate limited, and this limit is hit then an http 429 response is returned 401 unauthorized the api key supplied with your request is not valid 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 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 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 503 service unavailable we’ve implemented a system that returns a 503 status when a request type is down due to a parsing incident this helps avoid serving unstable or partial data if a parsing incident is active, the 503 response will include a message like { "message 'request type google web is temporarily unavailable you have not been charged for this request', retry after 3600 } additionally, customers can proactively opt out of receiving data during incidents by using the skip on incident request parameter this is especially useful for automated systems that prefer to fail gracefully rather than risk bad data