错误
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
向 Bid Manager API 发出无法完成的请求会返回错误
消息。应解析并适当处理错误消息,以避免
错误。返回错误的请求会消耗用户配额和错误率
在审核额外配额申请时将予以考虑。
错误响应采用以下格式,并且包含 HTTP 响应代码:
错误消息和 Google RPC 代码状态:
{
"error": {
"code": integer,
"message": string,
"status": enum (google.rpc.Code)
}
}
下面列出了常见的 API 错误以及针对以下情况建议采取的措施:
它们会返回:
针对错误代码和 RPC 的建议操作 |
400 INVALID_ARGUMENT
|
您的请求存在问题。
查看错误响应中的消息字段,并修改您的请求
如果您在查找
可接受的过滤器、维度和指标组合,请参阅我们的
最佳报告
了解建议做法。 |
401 UNAUTHENTICATED
|
无法正确处理您的请求
必须经过身份验证。验证您是否在其中添加了有效的 OAuth 凭据
你的请求有关详情,请参阅
开始使用
指南。 |
404 NOT_FOUND
|
通过
Query
或
Report
尝试运行或检索的 。验证
以下:
|
429 RESOURCE_EXHAUSTED
|
您已超出
API 请求配额或
报告配额。
阅读错误消息,确定超出的配额类型:
|
500 INTERNAL
|
API 出现内部错误。使用
指数
退避错误处理策略来等待并重试请求。如果
错误仍然存在,联系人
支持。 |
504 DEADLINE_EXCEEDED
|
该 API 需要很长时间才能完成
请求。使用
指数
退避错误处理策略来等待并重试请求。如果
错误仍然存在,联系人
支持。 |
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-08-31。
[null,null,["最后更新时间 (UTC):2025-08-31。"],[[["\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). |"]]