API Errors

KBPublisher uses conventional HTTP response codes to indicate success or failure of an API request. In general, codes in the 2xx range indicate success, codes in the 4xx range indicate an error that resulted from the provided information (e.g. a required parameter was missing, etc.), and codes in the 5xx range indicate an error on server, db error or API settings error.

HTTP Status Code Summary

• 200 OK - Everything worked as expected.
• 400 Bad Request - Often missing a required parameter, bad request.
• 401 Unauthorized - No valid API key provided,bad signature.
• 402 Request Failed - Parameters were valid but request failed.
• 404 Not Found - The requested item doesn't exist.
• 500, 502, 503, 504 Server errors - something went wrong on server.

Error Codes

In addition to descriptive error text, error messages contain machine-parseable codes. While the text for an error message may change, the codes will stay the same. The following table describes the codes which may appear when working with the API:

If you see an error response which is not listed in the above table, then fall back to the HTTP status code in order to determine the best way to address the error.

Error Messages

When the KBPublisher API returns error messages, it does so in your requested format. For example, an error from a JSON method might look like this:

{

    "errors":[

        {

            "errorCode": 25,

            "errorMessage": "Missing or invalid argument(s)",

            "errorInfo": "Required argument(s): timestamp"

         }

      ]

}

The corresponding XML response would be:

<?xml version="1.0" encoding="UTF-8"?>

<errors>

    <error>

        <errorCode>25</errorCode>

        <errorMessage>Missing or invalid argument(s)</errorMessage>

        <errorInfo>Required argument(s): timestamp</errorInfo>

    </error>

</errors> 

errorInfo field is an optional in error response.