| 200 | Success |
| 201 | Created successfully The request to create some sort of object was completed with success and the new object was created |
| 204 | Operation successful but no content returned The requested operation was carried out successfully but didn’t return any data |
| 303 | Already exists The object that was attempted created already exists in the database. Along with the status code is usually the location to a GET method to retrieve the object that already exists |
| 400 | Invalid data Even though the request was in the right format, the data within the request doesn’t meet the validation rules |
| 401 | Bad signature The signature for authenticating the app making the request is invalid. Response body will hold sub-code with more information about the specific error:
When requested in our test environment, the latter will include information about correct hash and correct string to build token. |
| 403 | Authentication failed Credentials for a specific account was invalid |
| 404 | Object not found The requested object wasn’t found |
| 412 | Operation not allowed Even though the app was correctly authenticated, it is not permitted to carry out the requested operation due to the restrictions applied for the particular app |
| 500 | Server error |
| 501 | Malformed request The data supplied in the request body is not in the expected format |
Manage space
Manage content
Integrations