Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
Content API for Shopping impone cuotas y límites estrictos en algunas funciones.
Todas las cuotas y los límites están sujetos a eliminación, reducción o cambio en cualquier momento y sin previo aviso.
Política de cuotas
En promedio, no actualices tus productos más de dos veces al día ni tus cuentas secundarias más de una vez al día.
Cuotas de llamadas a métodos
Content API for Shopping ajusta automáticamente tus cuotas de products y accounts según tu uso. El uso de accounts se basa en el límite de cuentas secundarias.
A continuación, te indicamos cómo hacemos un seguimiento del uso de tu cuota:
Las cuotas son por método. Por ejemplo, el método get tiene una cuota distinta del método update.
Los métodos patch se consideran en las cuotas de get y update.
Cada llamada a método dentro de un custombatch se cuenta de forma independiente en la cuota de ese método.
Las llamadas se descuentan de la cuota de la cuenta con la que te autenticas cuando realizas la llamada. Por ejemplo, si te autenticas como una cuenta avanzada, las llamadas se registran en la cuota de tu cuenta avanzada, pero si te autenticas como una de tus cuentas secundarias, las llamadas se registran en la cuota de la cuenta secundaria.
Verifica tus cuotas
Para verificar la cuota y el uso actuales de una cuenta, llama a quotas.list con el merchantId de la cuenta.
Te recomendamos que revises tus cuotas periódicamente para asegurarte de tener suficiente para tu implementación.
La cuota automática solo se aplica a los servicios products y accounts. Si necesitas un aumento de la cuota de cualquier otro servicio, alcanzaste tu cuota diaria de los servicios products o accounts, o necesitas un aumento temporal de accounts o los productos services, comunícate con nosotros y envíanos la siguiente información:
Es su ID de Merchant Center.
En qué métodos alcanzaste los límites de cuota
Una estimación de cuántas llamadas por día necesitas para esos métodos.
El motivo por el que necesitas un aumento de la cuota
Errores
Si superas las cuotas de Content API for Shopping, recibirás los siguientes errores:
Por minuto: quota/request_rate_too_high
Por día: quota/daily_limit_exceeded
Para ver tus cuotas y el uso, y solicitar un aumento de cuota por día o por minuto, consulta Cómo consultar tus cuotas.
too_many_subaccounts: Maximum number of sub-accounts reached
Límites de representación de recursos
En los siguientes límites, se describen restricciones notables para ciertos valores de cadena y campos de array dentro de las representaciones de recursos que se usan en la API de Content. Estos límites son los mismos para Content API y su función correspondiente en Merchant Center. Es posible que esta lista de límites no esté completa y que estos límites
no se puedan extender.
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Falta la información que necesito","missingTheInformationINeed","thumb-down"],["Muy complicado o demasiados pasos","tooComplicatedTooManySteps","thumb-down"],["Desactualizado","outOfDate","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Problema con las muestras o los códigos","samplesCodeIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 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[]`"]]
