Error Messages Returned by Integration Monitoring API for Strategic Sourcing
When there is an issue with the Integration monitoring API, a JSON response containing one of the following HTTP response codes is returned to explain what the issue was.
|
Other error messages might be displayed as a result of JSON serialization errors or certificate parsing and validations. These can appear as error code 500 (for request processing errors) or error code 401 (for authentication failure).
Error Examples:
{
"error": {
"code":400,
"message": "The API requires either the ITK display name or the Internal Event Name."
}
}
{
"error": {
"code":400,
"message": "The ITK event display name provided is invalid."
}
}
{
"error": {
"code":400,
"message": "The integration event name provided is invalid."
}
}
{
"error": {
"code":400,
"message": "The realm name provided is invalid."
}
}
{
"error": {
"code":401,
"message": "Shared Secret and Client Certificate are both null"
}
}
{
"error": {
"code":401,
"message": "Authentication failure: Invalid Integration Password or Authentication mode is of type Certificate."
}
}
{
"error": {
"code":401,
"message": "Authentication failure: Invalid Digital Certificate or Authentication mode is of type Shared Secret"
}
}
{
"error": {
"code":403,
"message": "This API is not enabled for your site."
}
}
{
"error": {
"code":405,
"message": "POST not allowed."
}
}
{
"error": {
"code":500,
"message": "OAuth server is down. Please try again later."
}
}