HomeGuidesAPI ReferenceChangelog
Log In

Response Codes

Client error responses are served with 400 series HTTP status codes and server error responses are served with 500 series HTTP status codes. Usually a JSON response will be attached, but some will respond with different kinds of body. In these circumstances where a response structure cannot be parsed, consider the HTTP code's core meaning to take precedence. For instance, you may occasionally see a HTTP 404 along with a HTML response. In this case, it's safe to assume that the content cannot be found (HTTP 404 means "Not Found").

HTTP Status Codes and Messages

CodeTextDescriptionTroubleshooting tips
200OKThe request was successful!
304Not ModifiedThere was no new data to return.
400Bad RequestThe request was invalid or cannot be otherwise served. An accompanying error message will explain further.Double check the format of your JSON request body.
401UnauthorizedThere was a problem authenticating your request. This could be due to missing or incorrect authentication credentials. This may also be returned in other undefined circumstances.Check that you are using the correct authentication method and that your credentials are correct.
403ForbiddenThe request is understood, but it has been refused or access is not allowed. An accompanying error message will explain why.Check that your account has the necessary permission to perform the operation.
404Not FoundThe URL requested is invalid or the resource requested, such as an account or provider, does not exist.Check that you are using valid parameters and the correct URL for the endpoint you're using.
406Not AcceptableReturned when an invalid format is specified in the request. Generally, this occurs where your client fails to properly include the headers to accept the response type.Check that you are correctly passing expected query parameters, including expected headers, in your request.
409ConflictReturned when the resource cannot be modified in the requested way as it would conflict with another resource.Usually this occurs when trying to name a resource with a name that is already in use, or when trying to delete a resource which is linked via other resources.
410GoneThis resource is gone. Used to indicate that an API endpoint has been turned off.
422Unprocessable EntityReturned when the data is unable to be processed.Check that the data you are sending in your request is valid. For example, this data could be the JSON body of your request or an image.
429Too Many RequestsReturned when a request cannot be served due to the App's rate limit having been exhausted for the resource. See Rate Limiting.Check the number of requests per timeframe allowed with the endpoint you're using. Wait for the timeframe to reset. Space out your requests to ensure you don't hit rate limits.
500Internal Server ErrorSomething is broken. This is usually a temporary error, for example in a high load situation or if an endpoint is temporarily having issues.Check the Urjanet Status Page or simply wait and try again later.
502Bad GatewayUrjanet API is down, or being upgradedCheck the Urjanet Status Page or simply wait and try again later.
503Service UnavailableThe Urjanet servers are up, but overloaded with requests. Try again later.Check the Urjanet Status Page or simply wait and try again later.
504Gateway TimeoutThe Urjanet servers are up, but the request couldn't be serviced due to some failure within the internal stack. Try again later.Check the Urjanet Status Page or simply wait and try again later.

When an error occurs during a request, detailed information about the error is returned in the response body to aid in diagnosing the problem.