할당량은 메서드별로 적용됩니다. 예를 들어 get 메서드에는 update 메서드와 별도의 할당량이 있습니다.
각 요청은 유형과 관계없이 한 번 집계됩니다. 예를 들어 250개의 항목에 대한 list 요청은 250개의 get 요청이 아닌 1회로 집계됩니다.
할당량은 API 요청을 실행하는 사용자를 기준으로 청구됩니다. 사용자가 고급 계정의 직접 회원인 경우 고급 계정 수준에서 할당량이 청구됩니다.
할당량은 호출 시 인증하는 비교 쇼핑 서비스 (CSS) 그룹, CSS, 계정 또는 하위 계정에 적용됩니다. 예를 들어 고급 계정으로 인증하면 호출이 고급 계정의 할당량에 반영되지만 하위 계정 중 하나로 인증하면 호출이 하위 계정의 할당량에 반영됩니다.
이 다이어그램은 CSS 그룹, CSS, 계정, 하위 계정의 계층 구조를 보여줍니다.
내 할당량 확인
계정의 현재 할당량과 사용량을 확인하려면 계정의 name를 사용하여 quotas.list를 호출합니다.
자동 할당량은 products 및 accounts 서비스에만 적용됩니다. 다른 서비스의 할당량을 늘려야 하거나, products 또는 accounts 서비스의 일일 할당량에 도달했거나, accounts 또는 제품 services의 일시적인 할당량 증액이 필요한 경우 다음 정보를 포함하여 Google에 문의하세요.
판매자 센터 ID
할당량 한도에 도달한 메서드
이러한 메서드에 필요한 일일 호출 수의 추정치
할당량을 늘려야 하는 이유
할당량 증가가 임시로 또는 영구적으로 필요한지 여부
구현에 충분한 할당량이 있는지 또는 할당량이 자동으로 조정되는 방식을 확인하기 위해 주기적으로 할당량을 확인하는 것이 좋습니다.
오류
할당량을 초과하면 다음과 같은 오류가 발생합니다.
분당: quota/request_rate_too_high
일일: quota/daily_limit_exceeded
할당량 및 사용량을 확인하고 일일 또는 분당 할당량 증가를 요청하려면 할당량 확인을 참고하세요.
[null,null,["최종 업데이트: 2025-08-08(UTC)"],[[["\u003cp\u003eMerchant API utilizes automatic quota adjustments for \u003ccode\u003eproducts\u003c/code\u003e and \u003ccode\u003eaccounts\u003c/code\u003e services based on usage, tracking requests per-method and applying quotas to specific CSS groups or accounts.\u003c/p\u003e\n"],["\u003cp\u003eUpdates are limited to twice per day for products and once per day for sub-accounts.\u003c/p\u003e\n"],["\u003cp\u003eYou can request quota increases for services other than \u003ccode\u003eproducts\u003c/code\u003e and \u003ccode\u003eaccounts\u003c/code\u003e, exceeding daily quotas, or requiring temporary increases by contacting Google Merchant Center support.\u003c/p\u003e\n"],["\u003cp\u003eExceeding quotas results in specific errors, such as \u003ccode\u003equota/request_rate_too_high\u003c/code\u003e (per minute) and \u003ccode\u003equota/daily_limit_exceeded\u003c/code\u003e (per day), with instructions for checking and requesting increases.\u003c/p\u003e\n"],["\u003cp\u003eResource representations have inherent limits, notably affecting \u003ccode\u003eshippingsettings\u003c/code\u003e with restrictions on shipping services, groups, labels, and table dimensions.\u003c/p\u003e\n"]]],[],null,["# Quotas and limits\n\nMerchant API features carry strict quotas and limits.\n| **Note:** Quotas and limits are subject to elimination, reduction, or change at any time, without notice.\n\nUpdate policy\n-------------\n\nMerchant API enforces the following policies in terms of updates:\n\n- You can only update your products up to twice per day.\n- You can only update your sub-accounts once per day.\n\nQuota-related changes between Merchant API and Content API for Shopping\n-----------------------------------------------------------------------\n\n- Quota will be counted per resource, not per method. This means some services are now linked.\n- The absence of custom batching doesn't affect quota calculation. For example, a batch request containing 500 insert requests will be charged as 500 individual insert method requests.\n- Quota automation for accounts and products remains in place.\n- To determine your current quota usage and limits, including automation and overrides, use the [Quota.list method](/merchant/api/reference/rest/quota_v1/accounts.quotas/list).\n\n| **Note:** For the `accounts.list` method, quota and limits usage are charged for each user, and not for the Merchant Center ID or the advanced account ID. To list several sub-accounts, you should use the `accounts.listSubaccounts` method, which is more suitable for advanced accounts use case.\n\nMethod call quotas\n------------------\n\nMerchant API automatically adjusts call quotas for your\n[`products`](/merchant/api/guides/products/overview) and\n[`accounts`](/merchant/api/guides/accounts/overview) based on your usage.\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- Each request counts once, regardless of its type. For example, we count a `list` request of 250 items once, not as 250 `get` requests.\n- Quota is charged based on the user who makes the API request. If the user is a direct member of an advanced account, the quota will be charged at the level of the advanced account.\n- Quotas apply to the Comparison Shopping Services (CSS) group, CSS, account, or [sub-accounts](/merchant/api/guides/accounts/sub-accounts) against which you authenticate when you make the call. For example, if you authenticate as an [advanced account](https://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\u003cbr /\u003e\n\nThe diagram shows the hierarchy of CSS groups, CSS, accounts, and sub-accounts.\n\n### Check your quotas\n\nTo check the current quota and usage for an account, call\n[`quotas.list`](/merchant/api/reference/rest/quota_v1/accounts.quotas/list)\nwith the `name` of the account.\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`, [contact\nus](/merchant/api/support/get-help) with the following information:\n\n- Your Merchant Center ID\n- The methods you've reached your quota limits on\n- An estimate of the number of calls per day you need for those methods\n- The reason you need a quota increase\n- Whether it's a temporary or permanent increase\n\nWe recommend checking your quotas periodically to ensure you have sufficient\nquota for your implementation, or how your quota is adjusted automatically.\n\n### Errors\n\nIf you exceed the quotas, you receive the following errors:\n\n- Per minute: `quota/request_rate_too_high`\n- Per day: `quota/daily_limit_exceeded`\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 Merchant API. These\nlimits are the same for both the Merchant API and their corresponding feature in\nthe Merchant Center.\n\nNote that this list of limits may not be complete. We won't extend these limits.\n\n| Resource | Field | Limit |\n|------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|\n| [`shippingsettings`](/merchant/api/reference/rest/accounts_v1/accounts.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[]`"]]