This code is returned due to one of the following reasons:

• User's role has no access permissions or functional scope.
• A required SKU subscription is missing.
• API operations that use POST, PUT, or DELETE methods are performed when the ZIA Admin Portal was in maintenance mode during a scheduled upgrade.

Contact Zscaler Support or your Zscaler Account team for assistance.

Bad Request

For example:

{
 "id": "resource.not.found", 
 "reason": "No resource exists with the given id/name :0", 
 "params": [
   "0" 
 ] 
}

Unauthorized

For example:

{
 id: "access.denied",
 reason: "Access denied"
}

Conflict

For example:

{
   "params":[
      "com.zscaler.zpn.model.PolicySet"
   ],
   "id":"api.concurrent.access.error",
   "reason":"Unable to modify the resource due to concurrent change requests. Try again"
}

Concurrent API calls using POST, PUT, and DELETE methods to the policy set controller might return error 409 - Conflict. Ensure that only one PUT request per policy rule is sent at a given time.

The API client exceeded the rate limit or quota.

The following example is the response body when an API call is rate limited:

{
  "exception": "invalid.toomanyrequests",
  "id": "invalid.toomanyrequests",
  "reason": "Exceeded the number of requests allowed"
}

The following example is the response header when an API call is rate limited:

{
  "content-type": "application/json",
  "date": "Wed, 6 Mar 2024 11:38 GMT",
  "retry-after": "13s"
} 

To learn more, see Understanding Rate Limiting.

Service Unavailable

The following example is a response body for error code 503:

{
 "id": "retryable.server.error",
 "reason": "An error occurred. Refer to the Retry-After header, and then try again."
}

The following is an example response header: {Retry-After: 10s}

Zscaler recommends an exponential backoff strategy before retrying. If a Retry-After header is available as part of the response headers, wait until the stipulated time mentioned in the Retry-After header before retrying.

This code is returned for one of the following reasons:

• The API key was disabled by your service provider.
• User's role has no access permissions or functional scope.
• API operations that use POST, PUT, or DELETE methods were performed when the Zscaler Cloud & Branch Connector Admin Portal was in maintenance mode during a scheduled upgrade.

Contact Zscaler Support or your Zscaler Account team for assistance.