价格、API 限制和配额
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
Search Ads 360 Reporting API 会对 API 操作强制执行限制，以确保所有用户的系统性能达到最佳水平。
价格
Search Ads 360 Reporting API 的使用费用已包含在 Search Ads 360 的总体价格中。使用该 API 无需支付额外费用。
查询限制
以下限制适用于通过 Search 或 SearchStream 方法执行的查询操作。
- 每个项目每位用户每分钟 3,000 次查询
- 每个项目每分钟 3,000 次查询
- 每个项目每天 150,000 次查询
API 的每天操作限制
API 的每天使用限制是根据每个 Google Cloud 项目执行的 API 操作数量确定的。
无论结果是通过 SearchAds360Service.SearchStream 进行流式传输还是通过 SearchAds360Service.Search 调用进行分页，单个查询或报告都计为一次操作。
了解详情。
下表列举了一些示例来说明具体是如何计数的：
| API 请求
|
计入每日限额的操作
|
操作：Search
数量：53 个广告组
服务：SearchAds360Service
|
1
|
操作：SearchStream
数量：45 个广告系列
服务：SearchAds360Service
|
1
|
超出这些限制的请求会被拒绝，并显示以下错误：RESOURCE_EXHAUSTED。
搜索请求
Search 或 SearchStream 请求计为一次操作，并计入用户的每天操作配额。无论批次数量是多少，一个 SearchStream 请求都算作一次 API 操作。
gRPC 限制
所有 Search Ads 360 报告 API 客户端库均使用 gRPC 生成请求和响应。默认情况下，gRPC 的消息大小为 4 MB。
回答不得超过此限制。例如，包含大量字段的搜索请求可能会生成大小超出 4 MB 的响应。为避免超出此限制，您可以减少所选字段的数量、缩减页面大小或使用流式传输。
超出此限制的请求不会生成 SearchAds360Error，但会生成 429 Resource Exhausted gRPC 错误。请参阅 gRPC 错误代码和消息列表。
分页请求
分页请求（例如包含有效 next_page_token 的请求）不计入用户的每天操作配额。不过，包含过期或无效网页令牌的分页请求会生成异常，并计入每天操作配额。
已分页的请求（例如搜索请求）还受到 Page size cannot exceed 10,000 rows 限制，如果违反此限制，则会被拒绝，并显示以下错误：INVALID_PAGE_SIZE。
如需详细了解分页，请参阅将结果分页。
返回 API 异常的请求
凡是被拒且显示 SearchAds360Failure 的请求，仍将计入用户的每天操作配额中。
不过，虽已失败但未返回 SearchAds360Failure 的请求（例如网络级错误导致的请求）不会计入用户的每天操作配额中，因为这些请求从未到达服务。例如，网络连接失败。
其他类型的限制
在请求中使用一个包含太多项的重复字段（例如操作列表）可能会导致以下错误：REQUEST_SIZE_LIMIT_EXCEEDED。此错误消息也可能是由其他问题导致的。
在发出 Search Ads 360 查询语言查询时，IN 子句中的项数上限为 20,000。如果超出该限制，系统会返回 FILTER_HAS_TOO_MANY_VALUES 错误。
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-08-29。
[null,null,["最后更新时间 (UTC)：2025-08-29。"],[[["\u003cp\u003eThe Search Ads 360 Reporting API has usage limits to maintain optimal performance, including query limits and daily operation limits.\u003c/p\u003e\n"],["\u003cp\u003eAPI usage is included in the Search Ads 360 pricing with no extra fees.\u003c/p\u003e\n"],["\u003cp\u003eQuery limits include 3,000 queries per minute per project per user, 3,000 queries per minute per project, and 150,000 queries per day per project.\u003c/p\u003e\n"],["\u003cp\u003eDaily API usage limits apply per Google Cloud project, with each query or report counting as one operation, even for streamed or paged results.\u003c/p\u003e\n"],["\u003cp\u003eExceeding these limits results in specific error responses, such as \u003ccode\u003eRESOURCE_EXHAUSTED\u003c/code\u003e for exceeding daily limits or query limits and \u003ccode\u003eINVALID_PAGE_SIZE\u003c/code\u003e for exceeding page size limits.\u003c/p\u003e\n"]]],["The Search Ads 360 Reporting API has usage limits: 3,000 queries per minute per user/project, 3,000 queries per minute per project, and 150,000 queries per day per project. Each `Search` or `SearchStream` request counts as one operation, with a 4MB gRPC response size limit. Exceeding these limits, having an invalid page token or an API exception counts towards daily quota. Paginated requests with valid tokens do not count. The API is included in Search Ads 360 pricing.\n"],null,["# Pricing, API Limits and Quotas\n\nThe Search Ads 360 Reporting API enforces limits on API operations to ensure optimal system performance for all users.\n\nPricing\n-------\n\nUse of the Search Ads 360 Reporting API is included in the overall pricing of Search Ads 360. There are no additional fees for using the API.\n\nQuery Limits\n------------\n\nThe following limits apply to query operations performed through the Search or SearchStream methods.\n\n- 3,000 queries per minute per project per user\n- 3,000 queries per minute per project\n- 150,000 queries per day per project\n\nDaily API operation limits\n--------------------------\n\nDaily API usage limits are based on the number of API operations made per\nGoogle Cloud project.\n\nA single query or report is counted as one operation, regardless of the results\nbeing streamed through\n[`SearchAds360Service.SearchStream`](/search-ads/reporting/api/reference/rpc/google.ads.searchads360.v0.services#google.ads.searchads360.v0.services.SearchAds360Service.SearchStream)\nor paged from a\n[`SearchAds360Service.Search`](/search-ads/reporting/api/reference/rpc/google.ads.searchads360.v0.services#google.ads.searchads360.v0.services.SearchAds360Service.Search) call.\n[Learn more](/search-ads/reporting/concepts/streaming#rate_limits).\n\nThe following table gives some examples of the accounting:\n\n| API request | Operations counted towards Daily Limit |\n|------------------------------------------------------------------------------|----------------------------------------|\n| Operation: `Search` Count: 53 ad groups Service: `SearchAds360Service` | 1 |\n| Operation: `SearchStream` Count: 45 campaigns Service: `SearchAds360Service` | 1 |\n\nRequests that violate these limits are rejected with the error:\n[`RESOURCE_EXHAUSTED`](/search-ads/reporting/api/reference/rpc/google.ads.searchads360.v0.errors#quotaerror).\n\nSearch requests\n---------------\n\nA `Search` or `SearchStream` request counts as one operation against the user's\ndaily operation quota. One `SearchStream` request counts as one API operation\nirrespective of the number of batches.\n\ngRPC limitations\n----------------\n\nAll of the Search Ads 360 Reporting API [client libraries](/search-ads/reporting/client-libraries/client-libraries) use\n[gRPC](//grpc.io/) for generating requests and responses. By default, gRPC has a\nmessage size of 4 MB.\n\nResponses must not exceed this limit. For example, a search request that\nincludes a lot of fields may generate a response that exceeds 4 MB in size. To\navoid this limit, you can reduce the number of selected fields, reduce the page\nsize, or use [streaming](/search-ads/reporting/concepts/streaming).\n\nRequests that violate this limitation will *not* generate a\n[`SearchAds360Error`](/search-ads/reporting/api/reference/rpc/google.ads.searchads360.v0.errors#searchads360error), but will generate a\n`429 Resource Exhausted` gRPC error. Refer to the [list of gRPC error codes and\nmessages](https://github.com/grpc/grpc/blob/master/doc/statuscodes.md).\n\nPaginated requests\n------------------\n\nPaginated requests (for example, requests that contain a valid\n`next_page_token`) are not counted against a user's daily operation quota.\nHowever, pagination requests that contain an expired or invalid page token will\ngenerate an exception and will count against the daily operation quota.\n\nRequests that are paginated, such as search requests, are also subject to the\n`Page size cannot exceed 10,000 rows` limitation and are rejected if it violates\nthis limit, with the error:\n[`INVALID_PAGE_SIZE`](/search-ads/reporting/api/reference/rpc/google.ads.searchads360.v0.errors#requesterror).\n\nFor more details on pagination, refer to [Paging through\nresults](/search-ads/reporting/concepts/pagination).\n\nRequests that return API exceptions\n-----------------------------------\n\nRequests that are rejected with a\n[`SearchAds360Failure`](/search-ads/reporting/api/reference/rpc/google.ads.searchads360.v0.errors#searchads360failure) still count against the\nuser's daily operation quota.\n\nRequests that fail but don't return a\n[`SearchAds360Failure`](/search-ads/reporting/api/reference/rpc/google.ads.searchads360.v0.errors#searchads360failure), such as from an error at\nthe network level, won't count against the user's daily operation quota\nsince the requests would never reach the service. An example of this is a\nnetwork connectivity failure.\n\nOther types of limits\n---------------------\n\nA repeated field, such as a list of operations, that has too many items in a\nrequest can incur the error:\n[`REQUEST_SIZE_LIMIT_EXCEEDED`](/search-ads/reporting/api/reference/rpc/google.ads.searchads360.v0.errors#google.ads.searchads360.v0.errors.SizeLimitErrorEnum).\nThis same error message can also be due to other issues.\n\nWhen making a [Search Ads 360 Query Language](/search-ads/reporting/concepts/query-language) query, the maximum number of items\nwithin an `IN` clause is 20,000. If you exceed that limit, a\n[`FILTER_HAS_TOO_MANY_VALUES`](/search-ads/reporting/api/reference/rpc/google.ads.searchads360.v0.errors#queryerror)\nerror is returned."]]
