Content API for Shopping에는 일부 기능에 엄격한 할당량과 제한이 적용됩니다.
모든 할당량과 한도는 언제든지 통지 없이 삭제, 축소 또는 변경될 수 있습니다.
할당량 정책
평균적으로 제품은 하루에 두 번 이상, 하위 계정은 하루에 한 번 이상 업데이트하지 않습니다.
메서드 호출 할당량
Content API for Shopping은 사용량에 따라 products 및 accounts 할당량을 자동으로 조정합니다. accounts 사용량은 하위 계정 한도를 기준으로 합니다.
Google에서 할당량 사용을 추적하는 방법은 다음과 같습니다.
할당량은 메서드별로 적용됩니다. 예를 들어 get 메서드에는 update 메서드와 별도의 할당량이 있습니다.
patch 메서드는 get 및 update 할당량에 모두 반영됩니다.
custombatch 내의 각 메서드 호출은 해당 메서드의 할당량에 별도로 반영됩니다.
통화는 전화를 걸 때 인증한 계정의 할당량에 반영됩니다. 예를 들어 고급 계정으로 인증하면 고급 계정의 할당량에 따라 호출 수가 집계되지만 하위 계정 중 하나로 인증하면 하위 계정의 할당량에 따라 호출 수가 집계됩니다.
내 할당량 확인
계정의 현재 할당량과 사용량을 확인하려면 계정의 merchantId를 사용하여 quotas.list를 호출합니다.
구현에 충분한 할당량이 있는지 정기적으로 확인하는 것이 좋습니다.
자동 할당량은 products 및 accounts 서비스에만 적용됩니다. 다른 서비스의 할당량을 늘려야 하거나, products 또는 accounts 서비스의 일일 할당량에 도달했거나, accounts 또는 제품 services의 일시적인 할당량 증액이 필요한 경우 다음 정보를 포함하여 Google에 문의하세요.
판매자 센터 ID입니다.
할당량 한도에 도달한 메서드
이러한 메서드에 하루에 필요한 호출 횟수에 대한 추정치입니다.
할당량을 늘려야 하는 이유
오류
Content API for Shopping 할당량을 초과하면 다음과 같은 오류가 발생합니다.
분당: quota/request_rate_too_high
일일: quota/daily_limit_exceeded
할당량 및 사용량을 확인하고 일일 또는 분당 할당량 증가를 요청하려면 할당량 확인을 참고하세요.
too_many_subaccounts: Maximum number of sub-accounts reached
리소스 표현 한도
다음 제한사항은 Content API에 사용되는 리소스 표현 내에서 특정 문자열 값 및 배열 필드에 적용되는 주목할 만한 제한사항을 설명합니다. 이러한 제한은 Content API와 판매자 센터의 해당 기능에 모두 동일하게 적용됩니다. 이 한도 목록은 완전하지 않을 수 있으며 한도를 연장할 수 없습니다.
[null,null,["최종 업데이트: 2025-07-25(UTC)"],[[["\u003cp\u003eThe Content API for Shopping has quotas and limits that can change without notice, with product and sub-account updates recommended no more than twice and once per day, respectively.\u003c/p\u003e\n"],["\u003cp\u003eThe API adjusts \u003ccode\u003eproducts\u003c/code\u003e and \u003ccode\u003eaccounts\u003c/code\u003e quotas dynamically, tracking usage per method, including within \u003ccode\u003ecustombatch\u003c/code\u003e and based on the authenticated account.\u003c/p\u003e\n"],["\u003cp\u003eQuota usage can be checked with \u003ccode\u003equotas.list\u003c/code\u003e, and increases for specific services or if daily limits are reached can be requested through Google Merchant Center support.\u003c/p\u003e\n"],["\u003cp\u003eExceeding quotas results in specific errors like \u003ccode\u003equota/request_rate_too_high\u003c/code\u003e or \u003ccode\u003equota/daily_limit_exceeded\u003c/code\u003e, while resource representation limits exist for certain string and array field values.\u003c/p\u003e\n"],["\u003cp\u003eResource representation limits, which cannot be extended, apply to elements like shipping settings, affecting the number of services, groups, labels, and subtables allowed.\u003c/p\u003e\n"]]],["The Content API for Shopping has quotas and limits that can change without notice. It's advised to update products no more than twice daily and sub-accounts once. Quotas are per-method, with `patch` methods impacting both `get` and `update` quotas. The `products` and `accounts` quotas are automatically adjusted, but other services or temporary increases require contacting support. `quotas.list` checks current usage. Errors indicate `request_rate_too_high` (per minute) or `daily_limit_exceeded` (per day). Some resource limits like shipping settings exist.\n"],null,["# Quotas and limits\n\nThe Content API for Shopping imposes strict quotas and limits on some features.\nAll quotas and limits are subject to elimination, reduction, or change at any\ntime, without notice.\n| **Note:** If you need to call `datafeeds.fetchnow` more than once per day, we recommend you use the [`products`](/shopping-content/reference/rest/%0Av2.1/products) service instead to update your product data. We cannot provide a quota increase on `datafeeds.fetchnow`.\n\nQuota policy\n------------\n\nOn average, don't update your products more than twice per day, and\nyour sub-accounts more than once per day.\n\nMethod call quotas\n------------------\n\nThe Content API for Shopping automatically adjusts your\n[`products`](/shopping-content/reference/rest/v2.1/products) and\n[`accounts`](/shopping-content/reference/rest/v2.1/accounts) quotas based on\nyour usage. Your `accounts` usage is based on your sub-accounts limit.\n\nHere's how we track your quota usage:\n\n- Quotas are per-method. For example, the `get` method has a separate quota from the `update` method.\n- `patch` methods count against both your `get` and `update` quotas.\n- Each method call within a `custombatch` counts separately against that method's quota.\n- Calls count against the quota of the account you authenticate as when you make the call. For example, if you authenticate as an [advanced\n account](//support.google.com/merchants/answer/188487), calls count against your advanced account's quota, but if you authenticate as one of your sub-accounts, calls count against the sub-account's quota.\n\n| **Note:** The [`merchantsupport`](/shopping-content/reference/rest/v2.1/merchantsupport) methods always count against the quota for the account whose issues are requested. This might not be the account authenticating the request.\n\n### Check your quotas\n\nTo check the current quota and usage for an account, call\n[`quotas.list`](/shopping-content/reference/rest/v2.1/quotas/list) with the\n`merchantId` of the account.\n\nWe recommend checking your quotas periodically to ensure you have sufficient\nquota for your implementation.\n\nAutomatic quota only applies to the `products` and `accounts` services. If you\nneed an increased quota for any other service, you're hitting your daily quota\nfor the `products` or `accounts` services, or you need a temporary increase for\nthe `accounts` or products `services`,\n[contact us](https://support.google.com/merchants/contact/shopping_api_support_form)\nwith the following information:\n\n- Your Merchant Center ID.\n- Which methods you've reached your quota limits on.\n- An estimation of how many calls per day you need for those methods.\n- The reason you need a quota increase.\n\n### Errors\n\nIf you exceed the Content API for Shopping quotas, you receive the following\nerrors:\n\n- Per minute: `quota/request_rate_too_high`\n- Per day: `quota/daily_limit_exceeded`\n\n| **Note:** Calls that receive `quota/request_rate_too_high`, `quota/daily_limit_exceeded`, or authentication errors don't count towards the daily quota but any other unsuccessful calls are counted towards it.\n\nTo view your quotas and usage, and request a per-day or per-minute quota\nincrease, see [Check your quotas](#check_your_quotas).\n\nThe following errors can't be resolved by automatic quota increases, and require\nyou to [request additional quota of items, feeds or\nsub-accounts](//support.google.com/merchants/contact/additional_items):\n\n- `too_many_items: Merchant quota exceeded`\n- `too_many_subaccounts: Maximum number of sub-accounts reached`\n\nResource representation limits\n------------------------------\n\nThe following limits describe notable restrictions for certain string values and\narray fields within the resource representations used in the Content API. These\nlimits are the same for both the Content API and their corresponding feature in\nthe Merchant Center. This list of limits may not be complete, and these limits\ncannot be extended.\n\n| Resource | Field | Limit |\n|----------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|\n| [shippingsettings](/shopping-content/reference/rest/v2.1/shippingsettings) | Shipping services per country (`services`). Shipping groups per shipping service (`rateGroups`). Labels per shipping group (`applicableShippingLabels`). Subtables per shipping group (`subtables`). Number of rows or columns in a single [rate table](#note2). Length of shipping labels. | 20 20 30 100 150 100 |\n\nThe number of rows or columns in a rate table affects the following array fields:\n\n- Array fields within `rowHeaders` or `columnHeaders`:\n - `prices[]`\n - `weights[]`\n - `numberOfItems[]`\n - `postalCodeGroupNames[]`\n - `locations[]`\n - `rows[]`\n - `cells[]`"]]
