Contents x
    Error codes
    • 25 Sep 2024
    • 1 Minute to read
    • Print
    • Dark
      Light
    Contents

    Error codes

    • Updated on 25 Sep 2024
    • 1 Minute to read
    • Print
    • Dark
      Light
    Article summary

    The following list contains the full range of possible error codes which can be returned by the Bloxs API’s. The implementation is according to the rest standard.

    Status code

    Description

    Suggested course of action

    400

    There is a functional error in the content of the request. For more details on how to interpret the 400 response see 'Interpretation 400 response’.

    Interpret the response (automatically or manually), adjust the request accordingly and resend the request.

    401

    Client is not/cannot be authenticated. This is caused by missing or expired login credentials. For more details regarding authentication see ‘Authorization’.

    Request a new authentication token, the current token has most likely expired. The API key and/or Secret also may have changed.

    403

    Client is not authorized for this specific action.

    Step 1: Request a new authentication token, potential role / claim changes were not retrieved.

    Step 2: contact the tenant you are connecting too for the role adjustments

    404

    The server cannot find the requested resource.

    Check if the correct url has been used. Alternatively, it may have been deleted.

    405

    The request method is known by the server, but not supported by the resource that is addressed. For example, a GET is requested for a POST method.

    Retry with the correct method.

    429

    The client has send too many request in a limited time period. In this case Bloxs will apply throttling and the excess messages will be returned with a 429 response.

    Retry the request(s) at a later time.

    500

    Server side error (Bloxs).

    Retry the request(s) at a later time. Bloxs actively monitors errors and will fix the issue as soon as possible.

    503

    The Bloxs server is temporarily not available. For example due to maintenance.

    Retry the request(s) at a later time.

    What's Next