503 backendError Server returned an error.
Error Responses
Standard error responses
If a Core Reporting API request is successful, the API returns a 200 status code. If an error occurs with a request, How to remove Avast email signature from my email the API returns an HTTP status code, status, and reason in the response based on the type of error. Additionally, the body of the response contains a detailed description of what caused the error. Here's an example of an error response:
"error": {
"errors": [
"domain": "global",
"reason": "invaliParameter",
"message": "Invalid value '-1' for max-results. Value must be within the range: [1, 1000]",
"locationType": "parameter",
"location": "max-results"
"code": 00,
"message": "Invalid value '-1' for max-results. Value must be within the range: [1, 1000]"
Note: The description could change at any time so applications should not depend on the actual description text.
Error table
Code Reason Description Recommended Action
00 invalidParameter Indicates that a request parameter has an invalid value. The locationType and location fields in the error response provide information as to which value was invalid. Do not retry without fixing the problem. You need to provide a valid value for the parameter specified in the error response.
00 badRequest Indicates that the query was invalid. E.g., parent ID was missing or the combination of dimensions or metrics requested was not valid. Do not retry without fixing the problem. You need to make changes to the API query in order for it to work.
01 invalidCredentials Indicates that the auth token is invalid or has expired. Do not retry without fixing the problem. You need to get a new auth token.
03 insufficientPermissions Indicates that the user does not have sufficient permissions for the entity specified in the query. Do not retry without fixing the problem. You need to get sufficient permissions to perform the operation on the specified entity.
03 dailyLimitExceeded Indicates that user has exceeded the daily quota (either per project or per view (profile)). Do not retry without fixing the problem. You have used up your daily quota. See API Limits and Quotas.
03 userRateLimitExceeded Indicates that the Queries per 100 seconds per user limit has been exceeded. The default value set in Google API Console is 100 queries per 100 seconds per user. You can increase this limit in the Google API Console to a maximum of 1,000. Retry using exponential back-off. You need to slow down the rate at which you are sending the requests.
03 rateLimitExceeded Indicates that the project queries per 100 seconds rate limits have been exceeded. Retry using exponential back-off. You need to slow down the rate at which you are sending the requests.
03 quotaExceeded Indicates that the 10 concurrent requests per view (profile) in the Core Reporting API has been reached. Retry using exponential back-off. You need to wait for at least one in-progress request for this view (profile) to complete.
500 internalServerError Unexpected internal server error occurred. Do not retry this query more than once.
Handling 500 or 503 responses
A 500 or 503 error might result during heavy load or for larger more complex requests. For larger requests consider requesting data for a shorter time period. Also consider implementing exponential backoff. The frequency of these errors can be dependent on the view (profile) and the amount of reporting data associated with that view; A query that causes a 500 or 503 error for one view (profile) will not necessarily cause an error for the same query with a different view (profile).