HTTP Error Codes

HTTP 400

The request cannot be processed due to something that is perceived to be a client error (for example, malformed request syntax, invalid request message framing, or deceptive request routing).

HTTP 401

Used exclusively to indicate that the client is not authenticated. This typically means that the Authorization header was missing or invalid.

HTTP 403

Used exclusively to indicate that the client is authenticated but does not have permission to access the requested resource.

HTTP 404

Used exclusively to indicate that the resource or collection does not exist in Juniper Connect.

Important Note: This is different to a resource that exists but is not visible to the current user. In this case, a 403 should be returned.

HTTP 422

Used exclusively to indicate the presence of data validation errors.

HTTP 500

A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.