HTTP status codes

the table below presents standard http status codes that our system might return code text explanation recovery 200 ok the request has succeeded n/a 400 bad request the request was not processed, due to something the server considers to be a client error typically due to malformed request syntax, invalid request message framing, or deceptive request routing 401 unauthorized the request was not successful because it lacks valid authentication credentials (api key) for the requested resource provide a valid api key 403 forbidden the api key doesn’t have permissions to perform the request regenerate or modify the api key 404 not found the server cannot find the requested resource common causes of 404 responses are mistyped urls or pages that are moved or deleted without redirection 408 request timeout the server has decided to close the connection because it did not receive a complete request from the client within the server's allotted timeout period check connection 409 conflict the request conflicts with another request (perhaps due to using the same idempotent key) resolve conflicts and retry 424 external dependency failed the request couldn’t be completed due to a failure in a dependency external to cross river fix root cause and retry 429 too many requests indicates the client has sent too many requests in a given amount of time slow down the rate of requests is commonly called 5xx server errors someting went wrong on cross river's end