This page lists the HTTP status codes that the Bloxs APIs can return. Bloxs implements these status codes according to REST conventions. Use the suggested course of action to decide whether to retry, adjust or escalate a request.
Status code | Description | Suggested course of action |
|---|---|---|
400 | There is a functional error in the content of the request. See the Interpretation of a 400 response page for more detail on how to interpret this response. | Interpret the response, either automatically or manually, adjust the request accordingly and resend it. |
401 | The client is not authenticated, or cannot be authenticated. This is caused by missing or expired login credentials. See the Authorization documentation for detailed information about authentication and authorization. | Request a new authentication token, since the current token has most likely expired. The API key or secret may also have changed. |
403 | The client is not authorized for this specific action. | Request a new authentication token, since role or claim changes are not retrieved automatically. Contact the organization you are connecting to for a role adjustment. |
404 | The server cannot find the requested resource. | Check that the correct URL was used. Alternatively, the resource may have been deleted. |
405 | The server recognizes the request method, but the resource does not support it. For example, a GET request is sent to a resource that only supports POST. | Resend the request with the correct method. |
429 | The client has sent too many requests within a limited time period. Bloxs applies throttling in this case, and returns the excess requests with a 429 response. | Retry the request at a later time. |
500 | A server side error occurred within Bloxs. | Retry the request at a later time. Bloxs actively monitors errors and resolves issues as soon as possible. |
503 | The Bloxs server is temporarily unavailable, for example due to maintenance. | Retry the request at a later time. |