Requests made to the Bid Manager API that can't be completed return an error message. Error messages should be parsed and appropriately handled to avoid future errors. Requests returning errors consume user quota, and error rates are considered when reviewing requests for additional quota.
An error response has the following format and includes an HTTP response code, an error message, and a Google RPC code status:
{ "error": { "code": integer, "message": string, "status": enum (google.rpc.Code) } }
Here's a list of common API errors along with the recommended action to take if they are returned:
Recommended Actions for error code and RPC | |
---|---|
400 INVALID_ARGUMENT
|
There's an issue with your request.
Review the message field in the error response, and modify your request
accordingly. If you are experiencing issues with finding an acceptable combination of filters, dimensions, and metrics, refer to our reporting best practices for recommendations. |
401 UNAUTHENTICATED
|
Your request couldn't be properly authenticated. Verify that you are including valid OAuth credentials in your request. For more information, see the Get Started guide. |
404 NOT_FOUND
|
The
Query
or
Report
you are attempting to run or retrieve cannot be found. Verify the
following:
|
429 RESOURCE_EXHAUSTED
|
You have exceeded either your
API request quota or
reporting quota.
Read the error message to determine what type of quota you are exceeding:
|
500 INTERNAL
|
The API experienced an internal error. Use the exponential backoff error handling strategy to wait and retry the request. If the error persists, contact support. |
504 DEADLINE_EXCEEDED
|
The API took too long to complete the request. Use the exponential backoff error handling strategy to wait and retry the request. If the error persists, contact support. |