Request Collections
Request
Response
Send a request to see the response here
HTTP Status Codes Guide
Common HTTP response status codes and their meanings:
100 Continue
The server has received the request headers and the client should proceed to send the request body.
200 OK
The request has succeeded. The information returned depends on the method used.
201 Created
The request has been fulfilled and resulted in a new resource being created.
301 Moved Permanently
The resource has been assigned a new permanent URI and any future references should use one of the returned URIs.
400 Bad Request
The request could not be understood by the server due to malformed syntax.
401 Unauthorized
The request requires user authentication.
403 Forbidden
The request refuses to authorize and requires permissions.
404 Not Found
The server has not found anything matching the Request-URI.
405 Method Not Allowed
The method specified in the request (e.g., POST or DELETE) is not allowed for the resource identified by the URI.
408 Request Timeout
The server timed out waiting for the client to send the complete request.
409 Conflict
The request could not be completed due to a conflict with the current state of the resource.
410 Gone
The requested resource is no longer available and will not be available again and indicates permanent removal.
413 Payload Too Large
The server cannot process the request because the requested entity is too large.
429 Too Many Requests
The user has sent too many requests in a given amount of time
500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
501 Not Implemented
The server does not support the functionality required to fulfill the request.
502 Bad Gateway
The server, while acting as a gateway or proxy, received an invalid response from an upstream server.
503 Service Unavailable
The server is currently unable to handle the request due to temporary overload or maintenance.
504 Gateway Timeout
The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server.
505 HTTP Version Not Supported
The server does not support the HTTP protocol version used in the request.