We give an HTTP status code with every HTTP response we send from the backup management APIs. These status codes are intended to comply with the IETF specification. Here’s a non-exhaustive list of the frequently used status codes in our REST APIs and what we mean by them.

Status code	Status	Meaning
`200 OK`	Success	Everything was fine and worked.
`201 CREATED`	Success	Indicates that the request has succeeded and a new resource has been created as a result.
`202 ACCEPTED`	Success	Indicates that the request has been received but not completed yet. We have already added your request to our batch and will process it.
`400 BAD REQUEST`	Bad Request	The request does not have the required fields, or the fields are invalid in some way.
`401 UNAUTHORIZED`	Unauthorized	The current user is not authorized to execute this request. For more details, see Authorization.
`403 FORBIDDEN`	Forbidden	An action cannot be performed on the requested resource because the user does not have the access to that particular resource.
`404 NOT FOUND`	Not Found	The request has parameters that do not exist in the system. Verify the data that you are sending in your request.
`409 CONFLICT`	Conflict	The request could not be completed due to a conflict with the current state of the resource. A similar request/resource already exists in the system, and hence this prevents the user from creating duplicate requests.
`422 UNPROCESSABLE ENTITY`	Unprocessable Entity	The server understands the content type and syntax of the request entity, but is unable to process the request because of some invalid data passed in the request.
`429 TOO MANY REQUESTS`	Too Many Requests	There is a violation of the rate limit that we have set for our APIs. For more details, see Rate limiting.
`500 INTERNAL SERVER ERRORT`	Internal Server Error	Something went wrong and we don't know what. If the issue persists, reach out to the support team with the relevant details.
`503 UNAVAILABLE`	Service Unavailable	Something is down that should be up. Our load balancers might return this if we're down. We also return this if something we're relying on to handle the request isn't answering.
`504 GATEWAY TIMEOUT`	Gateway Timeout	We couldn't handle the GET request within our time limit. This might be due to some intermittent issue in the backend. Reach out to the support if the issue persists.

Error codes

You may encounter the following error codes when using these APIs:

Create backup policy

HTTP status code - 409 CONFLICT

1
2
"errorCode": "127",
"errorMessage": "Backup Policy already exists with orgId: {} cloudId: {} product: {PRODUCT}"

HTTP status code - 422 UNPROCESSABLE ENTITY

1
2
"errorCode": "103",
"errorMessage": "{PRODUCT} is not present in cloud site {}"

Get status of backup

HTTP status code - 400 BAD REQUEST

1
2
"errorCode": "108",
"errorMessage": "The backupId : {} is invalid or does not belong to operation Backup"

Create restore

HTTP status code - 409 CONFLICT

1
2
"errorCode": "137",
"errorMessage": "A restore request for this product already exists"

Get restore status

HTTP status code - 400 BAD REQUEST

1
2
"errorCode": "120",
"errorMessage": "The restoreId : {} is invalid or does not belong to operation Restore"

Create storage

HTTP status code - 409 CONFLICT

1
2
"errorCode": "128",
"errorMessage": "Conflicting Storage name = {}"

HTTP status code - 400 BAD REQUEST

1
2
"errorCode": "130",
"errorMessage": "Incorrect principalTag = {} or roleIdentifier = {}"

HTTP status code - 400 BAD REQUEST

1
2
"errorCode": "133",
"errorMessage": "Storage region = {} is not eligible for the org:{} and cloud: {}"

HTTP status code - 400 BAD REQUEST

1
2
"errorCode": "142",
"errorMessage": "Validation failed for storage creation for bucketName = {} and basePath = {} and region = {}"