Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
Con Content API for Shopping, puedes usar el recurso merchantsupport para crear una página de diagnóstico integrada en la aplicación para tus comercios. La API de Merchant ofrece la resolución de problemas, que admite la misma funcionalidad.
Descripción general
Cuando migres desde la API de Content, ten en cuenta los siguientes cambios en los nombres y las estructuras de los servicios y métodos:
El cambio más significativo en la respuesta de la API es la consolidación de los objetos AccountIssue y ProductIssue en un solo objeto RenderedIssue. Esto debería simplificar tu código, ya que proporciona una estructura coherente para todos los tipos de problemas.
La API de Merchant Center cambia el nombre del campo issues a rendered_issues.
Identificadores
Cambia tus identificadores de Content API de la siguiente manera para Merchant API.
Método
Content API for Shopping
API de Merchant
renderaccountissues
{merchant_id}
accounts/{ACCOUNT_ID}
renderproductissues
{PRODUCT_ID}
accounts/{ACCOUNT_ID}/products/{PRODUCT_ID}
TriggerAction
{merchant_id}
accounts/{ACCOUNT_ID}
Solicitudes
Cambia tus solicitudes de Content API de la siguiente manera para Merchant API.
Acción
Content API for Shopping
API de Merchant
Renderiza los problemas a nivel de la cuenta para una cuenta
POST https://shoppingcontent.googleapis.com/content/v2.1/MERCHANT_ID/merchantsupport/renderaccountissues
POST https://merchantapi.googleapis.com/issueresolution/v1/accounts/ACCOUNT_ID:renderaccountissues
Problemas de renderización de un producto
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
Acción de activación
POST https://shoppingcontent.googleapis.com/content/v2.1/MERCHANT_ID/merchantsupport/triggeraction
El cambio más significativo en la respuesta de la API es la consolidación de los objetos AccountIssue y ProductIssue en un solo objeto RenderedIssue.
Esto debería simplificar tu código, ya que proporciona una estructura coherente para todos los tipos de problemas.
Campos con el nombre cambiado
El nuevo nombre del campo issues de nivel superior en la respuesta es renderedIssues. Contiene una lista de objetos RenderedIssue.
[[["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-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` |"]]
