Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Com a API Content for Shopping, você pode usar o recurso
merchantsupport
para criar uma página de diagnóstico no app para seus comerciantes. A API Merchant
oferece a resolução de problemas, que tem a mesma funcionalidade.
Visão geral
Ao migrar da Content API, observe que há mudanças nos nomes e estruturas de serviços e métodos:
A mudança mais significativa na resposta da API é a consolidação dos objetos AccountIssue e ProductIssue em um único objeto RenderedIssue. Isso simplifica seu código, fornecendo uma estrutura consistente
para todos os tipos de problemas.
A API Merchant renomeia o campo issues como rendered_issues.
Identificadores
Mude os identificadores da API Content da seguinte forma para a API Merchant.
Método
API Content for Shopping
API Merchant
renderaccountissues
{merchant_id}
accounts/{ACCOUNT_ID}
renderproductissues
{PRODUCT_ID}
accounts/{ACCOUNT_ID}/products/{PRODUCT_ID}
TriggerAction
{merchant_id}
accounts/{ACCOUNT_ID}
Solicitações
Mude suas solicitações da API Content da seguinte forma para a API Merchant.
Ação
API Content for Shopping
API Merchant
Renderizar problemas no nível da conta
POST https://shoppingcontent.googleapis.com/content/v2.1/MERCHANT_ID/merchantsupport/renderaccountissues
POST https://merchantapi.googleapis.com/issueresolution/v1/accounts/ACCOUNT_ID:renderaccountissues
Renderizar problemas de um produto
POST https://shoppingcontent.googleapis.com/content/v2.1/MERCHANT_ID/merchantsupport/renderproductissues/PRODUCT_ID
POST https://merchantapi.googleapis.com/issueresolution/v1/accounts/ACCOUNT_ID/products/PRODUCT_ID:renderproductissues
Ação acionadora
POST https://shoppingcontent.googleapis.com/content/v2.1/MERCHANT_ID/merchantsupport/triggeraction
A mudança mais significativa na resposta da API é a consolidação dos objetos AccountIssue e ProductIssue em um único objeto RenderedIssue.
Isso simplifica seu código, fornecendo uma estrutura consistente para todos os tipos
de problemas.
Campos renomeados
O novo nome do campo issues de nível superior na resposta é renderedIssues. Ela contém uma lista de objetos RenderedIssue.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Não contém as informações de que eu preciso","missingTheInformationINeed","thumb-down"],["Muito complicado / etapas demais","tooComplicatedTooManySteps","thumb-down"],["Desatualizado","outOfDate","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Problema com as amostras / o código","samplesCodeIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-08 UTC."],[],[],null,["# Migrate merchant support\n\nWith Content API for Shopping, you can use the\n[merchantsupport](/shopping-content/reference/rest/v2.1/merchantsupport)\nresource to create an in-app diagnostics page for your merchants. Merchant API\noffers Issue resolution, which supports the same functionality.\n\nOverview\n--------\n\nWhen migrating from Content API, observe the following that there are changes to\nthe service and method names and structures:\n\n- The most significant change in the API response is the consolidation of the `AccountIssue` and `ProductIssue` objects into a single `RenderedIssue` object. This should simplify your code by providing a consistent structure for all types of issues.\n- Merchant API renames the `issues` field as `rendered_issues`.\n\nIdentifiers\n-----------\n\nChange your Content API identifiers as follows for Merchant API.\n\n| Method | Content API for Shopping | Merchant API |\n|-----------------------|--------------------------|-----------------------------------------------|\n| `renderaccountissues` | `{merchant_id}` | `accounts/{ACCOUNT_ID}` |\n| `renderproductissues` | `{PRODUCT_ID}` | `accounts/{ACCOUNT_ID}/products/{PRODUCT_ID}` |\n| `TriggerAction` | `{merchant_id}` | `accounts/{ACCOUNT_ID}` |\n\nRequests\n--------\n\nChange your Content API requests as follows for Merchant API.\n\n| Action | Content API for Shopping | Merchant API |\n|--------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Render account level issues for an account | ` POST https://shoppingcontent.googleapis.com/content/v2.1/`\u003cvar translate=\"no\"\u003eMERCHANT_ID\u003c/var\u003e`/merchantsupport/renderaccountissues ` | ` POST https://merchantapi.googleapis.com/issueresolution/v1/accounts/`\u003cvar translate=\"no\"\u003eACCOUNT_ID\u003c/var\u003e`:renderaccountissues ` |\n| Render issues for a product | ` POST https://shoppingcontent.googleapis.com/content/v2.1/`\u003cvar translate=\"no\"\u003eMERCHANT_ID\u003c/var\u003e`/merchantsupport/renderproductissues/`\u003cvar translate=\"no\"\u003ePRODUCT_ID\u003c/var\u003e` ` | ` POST https://merchantapi.googleapis.com/issueresolution/v1/accounts/`\u003cvar translate=\"no\"\u003eACCOUNT_ID\u003c/var\u003e`/products/`\u003cvar translate=\"no\"\u003ePRODUCT_ID\u003c/var\u003e`:renderproductissues ` |\n| Trigger action | ` POST https://shoppingcontent.googleapis.com/content/v2.1/`\u003cvar translate=\"no\"\u003eMERCHANT_ID\u003c/var\u003e`/merchantsupport/triggeraction ` | ` https://merchantapi.googleapis.com/issueresolution/v1/accounts/`\u003cvar translate=\"no\"\u003eACCOUNT_ID\u003c/var\u003e`:triggeraction ` |\n\nThe most significant change in the API response is the consolidation of\n`AccountIssue` and `ProductIssue` objects into a single `RenderedIssue` object.\nThis should simplify your code by providing a consistent structure for all types\nof issues.\n\nRenamed fields\n--------------\n\nThe new name for the top-level `issues` field in the response is\n`renderedIssues`. It contains a list of `RenderedIssue` objects.\n\n| Content API for Shopping | Merchant API |\n|--------------------------|------------------|\n| `issues` | `renderedIssues` |\n\nRenamed models\n--------------\n\n| Content API for Shopping | Merchant API |\n|-----------------------------------|-----------------|\n| - `AccountIssue` - `ProductIssue` | `RenderedIssue` |"]]
