Stay organized with collections
Save and categorize content based on your preferences.
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:
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
400INVALID_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.
401UNAUTHENTICATED
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.
404NOT_FOUND
The
Query
or
Report
you are attempting to run or retrieve cannot be found. Verify the
following:
You have exceeded either your
API request quota or
reporting quota.
Read the error message to determine what type of quota you are exceeding:
API request quota: Examine your API usage using the
Google
Cloud Console, and modify your workflow to operate within the
existing quota limits. If your operations can't be completed within
your given daily quota,
request additional
quota.
[null,null,["Last updated 2025-08-28 UTC."],[[["\u003cp\u003eBid Manager API request errors impact user quota and can be avoided by properly handling error messages.\u003c/p\u003e\n"],["\u003cp\u003eError responses provide specific codes, messages, and statuses to help diagnose and resolve issues.\u003c/p\u003e\n"],["\u003cp\u003eCommon errors include invalid arguments, authentication failures, resource exhaustion, and internal server errors.\u003c/p\u003e\n"],["\u003cp\u003eRecommended actions for common errors involve reviewing the request, verifying credentials, and adjusting API usage.\u003c/p\u003e\n"],["\u003cp\u003ePersistent errors after implementing recommended actions necessitate contacting support for further assistance.\u003c/p\u003e\n"]]],[],null,["# Errors\n\nRequests made to the Bid Manager API that can't be completed return an error\nmessage. Error messages should be parsed and appropriately handled to avoid\nfuture errors. Requests returning errors consume user quota, and error rates\nare considered when reviewing requests for additional quota.\n\nAn error response has the following format and includes an HTTP response code,\nan error message, and a [Google RPC code](//cloud.google.com/apis/design/errors#handling_errors) status: \n\n```gdscript\n{\n \"error\": {\n \"code\": integer,\n \"message\": string,\n \"status\": enum (google.rpc.Code)\n }\n}\n```\n\nHere's a list of common API errors along with the recommended action to take if\nthey are returned:\n| **Note:** If the error persists even after taking the recommended action, [contact\n| support](/bid-manager/support/contact) to report the issue.\n\n| Recommended Actions for error code and RPC ||\n|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `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](/bid-manager/guides/general/best-practices) for recommendations. |\n| `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](/bid-manager/guides/get-started/overview). |\n| `404` `NOT_FOUND` | The [`Query`](/bid-manager/reference/rest/current/queries#Query) or [`Report`](/bid-manager/reference/rest/current/queries.reports#Report) you are attempting to run or retrieve cannot be found. Verify the following: - The resource ID is correct - The resource type is valid for the endpoint - The resource in question was [created by the accessing user](/bid-manager/guides/general/best-practices#build_new_reports_in_the_ui_first) |\n| `429` `RESOURCE_EXHAUSTED` | You have exceeded either your [API request quota](/bid-manager/quotas) or [reporting quota](/bid-manager/guides/general/best-practices#consider_reporting_quotas). Read the error message to determine what type of quota you are exceeding: - API request quota: Examine your API usage using the [Google Cloud Console](//console.developers.google.com/project/_/apiui/apiview/doubleclickbidmanager.googleapis.com/metrics), and modify your workflow to operate within the existing quota limits. If your operations can't be completed within your given daily quota, [request additional quota](/bid-manager/quotas#additional_quota). - Reporting quota: Review [existing reporting quota best practices](/bid-manager/guides/general/best-practices#consider_reporting_quotas) and reach out to [Display \\& Video 360 product support](//support.google.com/displayvideo/contact/nghelp_contact_form) if needed. |\n| `500` `INTERNAL` | The API experienced an internal error. Use the [exponential backoff error handling strategy](/bid-manager/guides/general/best-practices#exponential_backoff) to wait and retry the request. If the error persists, [contact support](/bid-manager/support/contact). |\n| `504` `DEADLINE_EXCEEDED` | The API took too long to complete the request. Use the [exponential backoff error handling strategy](/bid-manager/guides/general/best-practices#exponential_backoff) to wait and retry the request. If the error persists, [contact support](/bid-manager/support/contact). |"]]