Status codes

Response status codes

When Hike receives a request to an API endpoint, a number of different HTTP status codes can be returned in the response depending on the original request.

200 OK	The request was successfully processed by Hike.
201 Created	The request has been fulfilled and a new resource has been created.
202 Accepted	The request has been fulfilled and an existing resource has been updated.
303 See Other	The response to the request can be found under a different URI in the Location header and can be retrieved using a GET method on that resource.
400 Bad Request	The request was not understood by the server, generally due to bad syntax or because the Content-Type header was not correctly set to application/json. This status is also returned when the request provides an invalid code parameter during the OAuth token exchange process.
401 Unauthorized	The necessary authentication credentials are not present in the request or are incorrect.
403 Forbidden	The server is refusing to respond to the request. This is generally because you have not requested the appropriate scope for this action.
404 Not Found	The requested resource was not found but could be available again in the future.
422 Unprocessable Entity	The request body was well-formed but contains semantical errors. The response body will provide more details in the errors parameter.
429 Too Many Requests	The request was not accepted because the application has exceeded the rate limit. See the API Call Limit documentation for a breakdown of Hike's rate-limiting mechanism.
500 Internal Server Error	An internal error occurred in Hike. Please email api@hikeup.com so that Hike staff can investigate.
501 Not Implemented	The requested endpoint is not available on that particular shop, e.g. requesting higher plan specific API on a shop running on a start-up plan. This response may also indicate that this endpoint is reserved for future use.
503 Service Unavailable	The server is currently unavailable. Check the status page for reported service outages.
504 Gateway Timeout	The request could not complete in time. Try breaking it down in multiple smaller requests.