Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
custombatch é um método comum que permite agrupar várias chamadas de API, conhecidas como "entradas", em uma única solicitação HTTP. Cada entrada faz referência apenas a uma
única chamada de método.
O lote personalizado é uma boa opção quando:
Você acabou de começar a usar a API e tem muitos dados de produtos para fazer upload.
Você precisa sincronizar os dados locais com o servidor enviando muitas atualizações e exclusões.
Fazer solicitações em lote
O envio de solicitações em lote é semelhante ao envio de chamadas de API em paralelo. Não há garantia de que a ordem das entradas definidas na solicitação estará na ordem em que são executadas. Recomendamos que você não use
chamadas interdependentes em uma única solicitação em lote, como criar e atualizar
a mesma remessa.
Da mesma forma, as respostas recebidas para solicitações em lote podem ser retornadas em uma ordem diferente daquela das entradas da solicitação. O BatchId pode ser usado para correlacionar solicitações e respostas, já que as respostas podem ser retornadas fora de sequência.
É possível fazer solicitações em lote na API chamando o método custombatch apropriado:
Recursos e métodos de lote personalizados correspondentes
Para evitar erros ao fazer upload de lotes grandes, recomendamos limitar o tamanho
das solicitações custombatch a no máximo 1.000 entradas. Os máximos a seguir
se aplicam a solicitações custombatch:
50.000 entradas por solicitação de custombatch
Tamanho da transferência de 32 MB
As chamadas que excedem os máximos resultam nos seguintes erros request_too_large:
"Too many requests in a batch."
"Request payload size exceeds the limit: %d bytes."
[null,null,["Última atualização 2025-08-13 UTC."],[[["\u003cp\u003eThe Merchant API is the new version of the Content API for Shopping and is now in beta.\u003c/p\u003e\n"],["\u003cp\u003eUse the \u003ccode\u003ecustombatch\u003c/code\u003e method to group several API calls into a single HTTP request for efficiency, especially for initial data uploads and synchronization.\u003c/p\u003e\n"],["\u003cp\u003eBatch requests have a limit of 50,000 entries and 32Mb transfer size; exceeding these limits will result in errors.\u003c/p\u003e\n"],["\u003cp\u003eThere's no guarantee that batched requests will be executed or returned in the order they were defined; use \u003ccode\u003eBatchId\u003c/code\u003e to correlate requests and responses.\u003c/p\u003e\n"],["\u003cp\u003eFor more details and to learn how the Merchant API can improve your integration, visit the announcement blog post.\u003c/p\u003e\n"]]],["The Merchant API beta, a new version of the Content API for Shopping, is introduced. It uses `custombatch`, a method to group multiple API calls into a single HTTP request for efficient data uploading and synchronization. `Custombatch` suits large data transfers but doesn't guarantee execution order. `BatchId` correlates requests and responses. Batches can have top-level or entry-specific errors. There is a recommended limit of 1,000 entries per batch with maximum limits of 50,000 entries, and 32Mb size.\n"],null,["# Batch requests\n\n`custombatch` is a common method that allows you to group several API calls,\nknown as \"entries\" into one single HTTP request. Each entry only references a\nsingle method call.\n\nCustom batch is a good choice when:\n\n- You've just started using the API and have a lot of product data to upload.\n- You need to synchronize local data with the server by sending lots of updates and deletes.\n\nMake batch requests\n-------------------\n\nSending batch requests is similar to sending API calls in parallel. Note that\nthere is no guarantee that the order of entries defined in the request will\nbe in the order that they are executed. We recommend that you don't use\ninterdependent calls in a single batch request (such as creating and updating\nthe same shipment).\n\nSimilarly, the responses received for batched requests may be returned in a\ndifferent order to that of the request entries. The `BatchId` can be used to\ncorrelate requests and responses since the responses may be returned out of\nsequence.\n| **Note:** Batch requests have two failure modes: one for top-level errors and one for errors resulting from individual entries in the batch. If a request fails because of a top-level error, responses for individual entries are not returned.\n\nYou can batch requests in the API by calling the appropriate `custombatch`\nmethod:\n\n| Resources and their corresponding custom batch methods ||\n|--------------------|------------------------------------------------------------------------------------------------------|\n| `Accounts` | [`accounts.custombatch`](/shopping-content/reference/rest/v2.1/accounts/custombatch) |\n| `Accountstatuses` | [`accountstatuses.custombatch`](/shopping-content/reference/rest/v2.1/accountstatuses/custombatch) |\n| `Accounttax` | [`accounttax.custombatch`](/shopping-content/reference/rest/v2.1/accounttax/custombatch) |\n| `Datafeeds` | [`datafeeds.custombatch`](/shopping-content/reference/rest/v2.1/datafeeds/custombatch) |\n| `Datafeedstatuses` | [`datafeedstatuses.custombatch`](/shopping-content/reference/rest/v2.1/datafeedstatuses/custombatch) |\n| `Localinventory` | [`localinventory.custombatch`](/shopping-content/reference/rest/v2.1/localinventory/custombatch) |\n| `Liasettings` | [`liasettings.custombatch`](/shopping-content/reference/rest/v2.1/liasettings/custombatch) |\n| `Pos` | [`pos.custombatch`](/shopping-content/reference/rest/v2.1/pos/custombatch) |\n| `Products` | [`products.custombatch`](/shopping-content/reference/rest/v2.1/products/custombatch) |\n| `Productstatuses` | [`productstatuses.custombatch`](/shopping-content/reference/rest/v2.1/productstatuses/custombatch) |\n| `Shippingsettings` | [`shippingsettings.custombatch`](/shopping-content/reference/rest/v2.1/shippingsettings/custombatch) |\n\nLimits\n------\n\nTo avoid errors when uploading large batches, we recommend limiting the size\nof `custombatch` requests to a maximum of 1,000 entries. The following maximums\napply to `custombatch` requests:\n\n- 50,000 entries per `custombatch` request\n- 32Mb transfer size\n\nCalls that exceed the maximums result in the following `request_too_large`\nerrors:\n\n- `\"Too many requests in a batch.\"`\n- `\"Request payload size exceeds the limit: %d bytes.\"`"]]
