...
| 200 | Success | ||||||||||||||||||||||||||
| 201 | Created successfully The object or connection was successfully created. | ||||||||||||||||||||||||||
| 204 | Operation successful but no content returned The requested operation was carried out successfully but didn't return any data. | ||||||||||||||||||||||||||
| 303 | Already exists An attempt was made to create an object or connection which already exists. Along with the status code, a "location" URL pointing to a GET method for the existing object may be returned. | ||||||||||||||||||||||||||
| 400 | Invalid data Even though the request was in the right format, the data within the request do not meet the validation rules. | ||||||||||||||||||||||||||
| Bad signature The request authentication signature is invalid. The response header will contain a sub-code with more information about the specific error:
| ||||||||||||||||||||||||||
| Authentication failed Credentials for a specific account were invalid. In case Data Isolation is enabled, the following sub codes may be returned in the response header:
In case Denial of Service is enabled, the following sub codes may be returned in the response header:
| ||||||||||||||||||||||||||
| 404 | Object not found The requested object wasn't found. Any endpoint that uses dpKey may return the following sub code in the response header:
Any endpoint that uses extKey/extType may return the following sub code in the response header:
| ||||||||||||||||||||||||||
| 409 | Duplicate request A duplicate request is currently being processed. | ||||||||||||||||||||||||||
| 412 | Operation not allowed Even though the app was correctly authenticated, the requested operation is not permitted due to restrictions on the app. | ||||||||||||||||||||||||||
| 500 | Server error | ||||||||||||||||||||||||||
| 501 | Malformed request The data supplied in the request body is not in the expected format. |