用量限额
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
由于 Google Vault API 是一项共享服务，因此我们会应用配额和限制，以确保所有用户都能公平使用该服务，并保护 Google Workspace 系统的整体健康状况。
产品限制
您所在组织中同时执行的导出操作不能超过 20 个。
API 请求配额
每个组织每分钟最多可以执行 600 次 matter 读取操作，包括通过 Vault API 和 vault.google.com 发出的请求，无论涉及的项目和用户数量是多少。
下表列出了每个项目每分钟的请求限额：
| 每个项目每分钟读取请求数 |
| 导出、事宜和已保存的查询 |
120 |
| 暂停 |
228 |
| 长时间运行的操作 |
300 |
| 每个项目每分钟的写入请求数 |
| 导出 |
20 |
| 暂停 |
60 |
| Matter 权限 |
30 |
| Matter |
60 |
| 已保存的查询 |
45 |
| 每个项目每分钟的搜索（计数）请求数 |
| 搜索次数 |
20 |
按方法划分的配额用量
请求使用的配额取决于所调用的方法。
下表列出了每种方法的配额用量：
| 方法 |
配额费用 |
matters.close
matters.create
matters.delete
matters.reopen
matters.update
matters.undelete
|
1 项事宜（阅读）
1 项事宜（撰写） |
matters.count |
1 个 |
matters.get |
已读 1 项诉讼或调查 |
matters.list |
10 项诉讼或调查 |
matters.addPermissions
matters.removePermissions
|
1 个实体的读取
1 个实体的写入
1 个实体的权限写入 |
matters.exports.create |
1 次导出读取
10 次导出写入 |
matters.exports.delete |
1 次导出写入 |
matters.exports.get |
已读取 1 项导出任务 |
matters.exports.list |
5 次导出读取 |
matters.holds.addHeldAccounts
matters.holds.create
matters.holds.delete
matters.holds.removeHeldAccounts
matters.holds.update
|
1 个实物读取
1 个实物写入
1 个保留读取
1 个保留写入 |
matters.holds.list |
1 项诉讼或调查已读
3 项保全已读 |
matters.holds.accounts.create
matters.holds.accounts.delete
matters.holds.accounts.list
|
1 个实物读取
1 个实物写入
1 个保留读取
1 个保留写入 |
matters.savedQueries.create
matters.savedQueries.delete
|
1 次实况读取
1 次实况写入
1 次已保存查询读取
1 次已保存查询写入 |
matters.savedQueries.get |
1 次事宜读取
1 次已保存的查询读取 |
matters.savedQueries.list |
1 次实况读取
3 次已保存的查询读取 |
operations.get |
1 次长时间运行的操作读取 |
解决基于时间的配额错误
如果您超出每分钟或每个组织的配额，通常会收到 429: Too many requests HTTP 状态代码响应。
对于所有基于时间的错误（每 X 分钟最多 N 个请求），我们建议您的代码捕获异常并使用截断指数退避，以确保设备不会产生过大的负载。
指数退避算法是网络应用的标准错误处理策略。指数退避算法以指数方式重试请求（不断增加各次请求之间的等待时间，直到达到最大退避时间）。如果请求仍然失败，请务必逐渐增加请求之间的延迟时间，直到请求成功为止。
示例算法
指数退避算法以指数方式重试请求（不断增加各次重试之间的等待时间，直到达到最大退避时间）。例如：
- 向 Google Vault API 发出请求。
- 如果请求失败，请等待 1 +
random_number_milliseconds 秒后再重试请求。
- 如果请求失败，请等待 2 +
random_number_milliseconds 秒后再重试请求。
- 如果请求失败，请等待 4 +
random_number_milliseconds 秒后再重试请求。
- 依此类推，等待时间上限为
maximum_backoff。
- 继续等待并重试，直至达到重试次数上限，但不会增加重试之间的等待时间。
其中：
- 等待时间为
min(((2^n)+random_number_milliseconds), maximum_backoff)，其中，n 会在每次迭代（请求）后增加 1。
random_number_milliseconds 是小于或等于 1,000 的毫秒数（随机值）。这有助于避免出现以下情况：许多客户端在某些情况下全部同步进行处理并同时执行重试操作，导致同步发送每一波请求。每次重试请求后，系统都会重新计算 random_number_milliseconds 值。maximum_backoff 通常为 32 或 64 秒。哪个值更为适当，这取决于用例。
客户端在达到 maximum_backoff 时间后可以继续重试。
此后执行的重试不需要继续增加退避时间。例如，如果客户端使用的 maximum_backoff 时间为 64 秒，则在达到此值后，客户端可以每 64 秒重试一次。到了特定时间点后，客户端应停止无限重试。
重试之间的等待时间和重试次数取决于您的用例和网络条件。
申请增加配额
根据项目的资源用量，您可能需要申请调整配额。服务账号的 API 调用被视为使用单个账号。我们无法保证您的调整配额请求一定会得到批准。如果配额调整请求会大幅增加配额值，则可能需要更长时间才能获得批准。
并非所有项目的配额都完全相同。随着您对 Google Cloud 的使用量逐步增加，您可能需要增加配额值。如果您预计用量即将显著增加，可以在 Google Cloud 控制台的“配额”页面中主动申请调整配额。
如需了解详情，请参阅以下资源：
价格
Google Workspace 客户可免费使用 Google Vault API。
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-08-29。
[null,null,["最后更新时间 (UTC)：2025-08-29。"],[],[],null,["# Usage limits\n\nAs the Google Vault API is a shared service, we apply quotas and limitations\nto make sure it's used fairly by all users and to protect the overall\nhealth of the Google Workspace system.\n\nProduct limits\n--------------\n\n\nYou can have no more than 20 exports in progress across your organization.\n\nAPI request quotas\n------------------\n\nEach organization is allowed 600 matter reads per minute, across all projects and users,\nincluding requests through the Vault API and vault.google.com.\n\nThe following tables list the per-minute per-project request limits:\n\n| Read requests per minute per project ||\n|---------------------------------|-----|\n| Export, matter, and saved query | 120 |\n| Hold | 228 |\n| Long-running operation | 300 |\n\n| Write requests per minute per project ||\n|--------------------|----|\n| Export | 20 |\n| Hold | 60 |\n| Matter permissions | 30 |\n| Matter | 60 |\n| Saved query | 45 |\n\n| Search (count) requests per minute per project ||\n|---------------|----|\n| Search counts | 20 |\n\nQuota usage by method\n---------------------\n\nThe quota used by a request depends on the method called.\nThe following table lists the per-method quota usage:\n\n| Method | Quota costs |\n|-----------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|\n| `matters.close` `matters.create` `matters.delete` `matters.reopen` `matters.update` `matters.undelete` | 1 matter read 1 matter write |\n| `matters.count` | 1 count |\n| `matters.get` | 1 matter read |\n| `matters.list` | 10 matter reads |\n| `matters.addPermissions` `matters.removePermissions` | 1 matter read 1 matter write 1 matter permissions write |\n| `matters.exports.create` | 1 export read 10 export writes |\n| `matters.exports.delete` | 1 export write |\n| `matters.exports.get` | 1 export read |\n| `matters.exports.list` | 5 export reads |\n| `matters.holds.addHeldAccounts` `matters.holds.create` `matters.holds.delete` `matters.holds.removeHeldAccounts` `matters.holds.update` | 1 matter read 1 matter write 1 hold read 1 hold write |\n| `matters.holds.list` | 1 matter read 3 hold reads |\n| `matters.holds.accounts.create` `matters.holds.accounts.delete` `matters.holds.accounts.list` | 1 matter read 1 matter write 1 hold read 1 hold write |\n| `matters.savedQueries.create` `matters.savedQueries.delete` | 1 matter read 1 matter write 1 saved query read 1 saved query write |\n| `matters.savedQueries.get` | 1 matter read 1 saved query read |\n| `matters.savedQueries.list` | 1 matter read 3 saved query reads |\n| `operations.get` | 1 long-running operation read |\n\nResolve time-based quota errors\n-------------------------------\n\n\nIf you exceed a per-minute or per-organization quota, you usually get a\n`429: Too many requests` HTTP status code response.\n\n\nFor all time-based errors (maximum of N requests per X minutes), we recommend\nyour code catches the exception and uses a *truncated exponential backoff* to make sure your\ndevices don't generate excessive load.\n\n\nExponential backoff is a standard error handling strategy for network applications. An\nexponential backoff algorithm retries requests using exponentially increasing wait times\nbetween requests, up to a maximum backoff time. If requests are still unsuccessful, it's\nimportant that the delays between requests increase over time until the request is successful.\n\n### Example algorithm\n\n\nAn exponential backoff algorithm retries requests exponentially, increasing the wait time\nbetween retries up to a maximum backoff time. For example:\n\n1. Make a request to Google Vault API.\n2. If the request fails, wait 1 + `random_number_milliseconds` and retry the request.\n3. If the request fails, wait 2 + `random_number_milliseconds` and retry the request.\n4. If the request fails, wait 4 + `random_number_milliseconds` and retry the request.\n5. And so on, up to a `maximum_backoff` time.\n6. Continue waiting and retrying up to some maximum number of retries, but don't increase the wait period between retries.\n\n\nwhere:\n\n- The wait time is `min(((2^n)+random_number_milliseconds), maximum_backoff)`, with `n` incremented by 1 for each iteration (request).\n- `random_number_milliseconds` is a random number of milliseconds less than or equal to 1,000. This helps to avoid cases in which many clients are synchronized by some situation and all retry at once, sending requests in synchronized waves. The value of `random_number_milliseconds` is recalculated after each retry request.\n- `maximum_backoff` is typically 32 or 64 seconds. The appropriate value depends on the use case.\n\n\nThe client can continue retrying after it has reached the `maximum_backoff` time.\nRetries after this point don't need to continue increasing backoff time. For\nexample, if a client uses a `maximum_backoff` time of 64 seconds, then after reaching\nthis value, the client can retry every 64 seconds. At some point,\nclients should be prevented from retrying indefinitely.\n\n\nThe wait time between retries and the number of retries depend on your use case\nand network conditions.\n\nRequest a quota increase\n------------------------\n\n\nDepending on your project's resource usage, you might want to request a quota\nadjustment. API calls by a service account are considered to be using a\nsingle account. Applying for an adjusted quota doesn't guarantee approval. Quota adjustment\nrequests that would significantly increase the quota value can take longer to be approved.\n\n\nNot all projects have the same quotas. As you increasingly use Google Cloud over\ntime, your quota values might need to increase. If you expect a notable upcoming\nincrease in usage, you can proactively\n[request quota adjustments](https://cloud.google.com/docs/quota#requesting_higher_quota)\nfrom the [Quotas page](https://console.cloud.google.com/iam-admin/quotas)\nin the Google Cloud console.\n\nTo learn more, see the following resources:\n\n- [About quota adjustments](https://cloud.google.com/docs/quotas/overview#about_increase_requests)\n- [View your current quota usage and limits](https://cloud.google.com/docs/quota#viewing_your_quota_console)\n- [Request a higher quota limit](https://cloud.google.com/docs/quota#requesting_higher_quota)\n\nPricing\n-------\n\n\nAll use of Google Vault API is available at no additional cost to Google Workspace customers."]]
