[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-04。"],[[["\u003cp\u003eChannel Services has resource limits, including one account per reseller domain, unlimited customers, entitlements, and channel partner links.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Workspace seat limits are set at 50,000, with the possibility to contact support for an increase, and trial durations are limited to 30 days for applicable SKUs.\u003c/p\u003e\n"],["\u003cp\u003eThe Test Partner Sales Console has a limit of 10 seats and a 1-day trial duration, with test domain naming convention and Google Workspace entitlements marked for deletion.\u003c/p\u003e\n"],["\u003cp\u003eCloud Channel API rate limits are enforced at 60-second intervals, with varying request limits per minute depending on the specific API method, and an overall limit of 120 for all other endpoints.\u003c/p\u003e\n"],["\u003cp\u003eBest practices for managing API rate limits include using a client-side rate limiter, implementing exponential backoff, following polling recommendations for \u003ccode\u003eoperations.get\u003c/code\u003e, and waiting a few seconds to retry after a \u003ccode\u003erateLimitExceeded\u003c/code\u003e error.\u003c/p\u003e\n"]]],[],null,["# Quotas & limits\n\nChannel Services limits\n-----------------------\n\nThe table below lists several limits applying to Channel Services\n\n### Resources limits\n\n### Google Workspace limits\n\n#### Limits specific to Test Partner Sales Console\n\nThere are additional considerations when using a Test Partner Sales Console:\n\n- Customers need to follow the test domain naming convention.\n- Google Workspace entitlements are marked for deletion 3 days after creation, and deleted weekly.\n\nCloud Channel API rate limits\n-----------------------------\n\nAPI rate limits define the number of requests that can be made to the\nCloud Channel API. Limits exist on a per-project basis and all API requests,\nincluding invalid requests, incur a quota cost.\n\nRate limits are enforced at **60 second (1 minute)** intervals. If you reach\nyour limit within 60 seconds, you need to wait for your quotas to refresh to\nmake more requests.\n\nWe have different quota buckets for different groups of endpoints. Quota usages\nin each bucket are evaluated independently. The following table lists the\nspecific and default per-project Cloud Channel API quota limits, and the\nmethods to which they apply.\n\nIf you need a higher rate limit for API requests, you can request an increase\nvia the\n[Google Cloud console](https://console.cloud.google.com/iam-admin/quotas).\n\n### Best practices\n\nHere are some best practices to help you with the API rate limits on\nCloud Channel API.\n\n- Use a client-side rate limiter to set an artificial rate limit.\n This can keep one client from using all of your quotas.\n\n- Use\n [exponential backoff](https://wikipedia.org/wiki/Exponential_backoff)\n to progressively space out requests once you reach your quota. This gives the\n server time to refill your buckets.\n\n- Follow polling recommendations described for all methods returning an\n Operation when calling `operations.get`\n\n- If you receive a 403 error with the message `rateLimitExceeded`, wait a\n few seconds and try your request again. Quotas are refilled every 60\n seconds, so your request should succeed after waiting for the next refresh."]]
