Errors

HTTP 400 Bad Request

An HTTP 400 Bad Request is returned when the syntax of your API request is incorrect. The response body contains JSON containing more detail.

AttributeDescription
errorsObject containing error details. Attributes names relate to the field causing the error.
typeURL. URL pointing to the reason for the error (typically https://tools.ietf.org/html/rfc7231#section-6.5.1)
titleString. Broad description of the error, for example One or more validation errors occurred.
statusNumber (400)
extensionsObject containing traceId string for error correlation

Example

{
    "errors": {
        "patch": [
            "The patch field is required."
        ],
        "leavingDate": [
            "Error converting value \"2020-40-40\" to type 'System.Nullable`1[System.DateTime]'. Path 'leavingDate', line 2, position 31."
        ]
    },
    "type": "https://tools.ietf.org/html/rfc7231#section-6.5.1",
    "title": "One or more validation errors occurred.",
    "status": 400,
    "extensions": {
        "traceId": "00-91e4405b75d06e4db212d2d0ccfede2b-d3eb9bf0ff405244-00"
    }
}

HTTP 500 Internal Server Error

You should not, as a rule, receive HTTP 500 Internal Server Error responses. If you do, the body will contain a generic JSON message:

{
    "type": "Exception",
    "message": "An error has occurred"
}

Contact saasmanager@1password.com with more details of the API request you were making when this happened so that we can diagnose and resolve for you.

By accessing or using 1Password Developer Tools, you agree to the API and SDK Terms of Service.


Published: