Pelcro uses conventional HTTP status codes to indicate the success or failure of an API request.
Generally, HTTP response status codes are separated into five categories. The first digit of the status code defines the category of response. There are five categories defined by the standard:
1xx informational response – the request was received, continuing process
2xx successful – the request was successfully received, understood, and accepted
3xx redirection – further action needs to be taken in order to complete the request
4xx client error – the request contains bad syntax or cannot be fulfilled
5xx server error – the server failed to fulfil an apparently valid request
Most commonly, you will likely see the following responses:
- HTTP Status Code 200 - OK: This is your ideal status code for your normal, everyday, properly functioning page.
- HTTP Status Code 301 - Permanent Redirect: A 301 redirect means that visitors and bots that land on that page will be passed to the new URL.
- HTTP Status Code 302 - Temporary Redirect: A 302 redirect is similar to a 301 in that visitors and bots are passed to the new page, but link equity may not be passed along.
- HTTP Status Code 404 - Not Found: This means the file or page that the browser is requesting wasn’t found by the server.
- HTTP Status Code 500 - Internal Server Error: Instead of the problem being with pages missing or not found, this status code indicates a problem with the server.
- HTTP Status Code 503 - Service Unavailable: This could be due to temporarily overloading the server or maintenance of the server.
For more information on HTTP response status codes, click here