Status Codes

SecureCloud uses conventional HTTP response codes to indicate the success or failure of an API request. In general:

Codes in the 2xx range indicate success.
Codes in the 4xx range indicate an error caused by the request (e.g., a required parameter was omitted or the token lacks permission). Most 4xx responses include an error message that briefly explains the problem.
Codes in the 5xx range indicate an error on SecureCloud's servers (these are rare).

Some endpoints additionally use SecureCloud-specific codes (440, 443, 447, 520). Please handle them explicitly in your integration. The reference page of each endpoint lists the codes it can return.

Success codes

HTTP status code	Description
200 - OK	SecureCloud successfully processed the request.
201 - Created	A resource was created, e.g. a group, a group member or an invitation.
204 - No Content	The request succeeded and the response has no body, e.g. when deleting an invitation.

Error codes

HTTP status code	Description
400 - Bad Request	The request was unacceptable, often due to a missing or invalid parameter.
401 - Unauthorized	No valid token provided or wrong format of the authorization header.
403 - Forbidden	The provided token doesn't have permissions to perform the request.
404 - Not Found	The requested resource doesn't exist.
423 - Locked	The file is locked by another user and cannot be deleted. Before version 13.0, this case returned `403`.
429 - Too Many Requests	Too many requests hit the API too quickly. We recommend an exponential backoff of your requests.
440 - Password Required	The library is encrypted and the `password` parameter is missing.
443 - Quota Exceeded	The storage quota is exceeded.
447 - Too Many Files	The number of files in the library exceeds the limit. Before version 13.0, this case returned `442`.
500, 502, 503, 504 - Server Errors	Something went wrong on SecureCloud's end.
520 - Operation Failed	The server could not complete the operation, e.g. a library or folder could not be created.