[null,null,["最終更新日 2025-09-03 UTC。"],[[["\u003cp\u003eThe Merchant API offers a collection of sub-APIs for managing various aspects of your online product data and presence on Google, including accounts, products, inventory, and reports.\u003c/p\u003e\n"],["\u003cp\u003eIt's designed for flexibility, allowing developers to choose and use only the specific sub-APIs relevant to their needs.\u003c/p\u003e\n"],["\u003cp\u003eThe API supports both gRPC and REST transport mechanisms and features independent versioning for each sub-API, minimizing the impact of updates on existing integrations.\u003c/p\u003e\n"],["\u003cp\u003eAlthough in beta and subject to change, Google provides at least 30 days' notice for breaking changes, ensuring developers have ample time to adapt.\u003c/p\u003e\n"],["\u003cp\u003eThe Merchant API shares similarities with the Content API for Shopping but aims to provide a simpler and more adaptable development experience.\u003c/p\u003e\n"]]],[],null,["We designed Merchant API to be familiar to Content API for Shopping developers,\nyet simpler and more flexible. Here's some detailed information on the design of\nMerchant API.\n\nSub-APIs\n\nMerchant API is a collection of sub-APIs. The sub-APIs are groups of related\nservices and resources. This design means you can choose to use only the\nsub-APIs needed for your unique integration.\n\nMerchant API includes the following sub-APIs:\n\n- **[Accounts](/merchant/api/guides/accounts/overview)**: Manage Merchant Center accounts at scale.\n- **[Conversions](/merchant/api/guides/conversion-sources/overview)**: Manage conversion sources for your account.\n- **[Data sources](/merchant/api/guides/data-sources/overview)**: View and manage the data sources for your products.\n- **[Issue resolution](/merchant/api/guides/accounts/view-issues)**: Obtain issues impacting your account and create an in-app diagnostics page.\n- **[Inventories](/merchant/api/guides/inventories/overview):** Showcase your products by store or region on Google.\n- **[Local feeds\n partnership](/merchant/api/guides/local-feeds-partnership/overview)**: Upload your local product inventory feed.\n- **[Notifications](/merchant/api/guides/accounts/notifications)**: Manage notification subscriptions.\n- **[Order tracking](/merchant/api/guides/order/overview)**: Provide historical order tracking data to improve shipping estimates and enhance listings with shipping annotations.\n- **[Products](/merchant/api/guides/products/overview)**: Manage product data, like price and availability.\n- **[Product Studio](/merchant/api/guides/product-studio/overview)**: Use Google Product Studio to generate product images and text suggestions automatically.\n- **[Promotions](/merchant/api/guides/promotions/overview)**: Create and manage promotions to showcase special offers for your products.\n- **[Quota](/merchant/api/reference/rest/quota_v1/accounts.quotas)**: Check the API quota of your accounts.\n- **[Reports](/merchant/api/guides/reports/overview):** View data on your products, performance, and competitive landscape across Google.\n- **[Reviews](/merchant/api/guides/reviews/products)**: Manage product and seller reviews.\n\nTransport\n\nMerchant API's default transport mechanism is [gRPC](//grpc.io/docs/guides/).\nYou can also use\n[REST](//en.wikipedia.org/wiki/Representational_state_transfer).\n\nSee the [quickstart guide](/merchant/api/guides/quickstart#use_grpc_or_rest) for\nmore information.\n\nEnums\n\nEnum fields across Merchant API might be exposing new values in the future. Your\ncode should be structured in such a way that it can handle unrecognized values\ngracefully. You should monitor the occurrence of unrecognized enum values and\nintervene to keep the code up to date.\n\nVersioning\n\nSub-APIs are versioned separately. This means you don't need to do anything if\nwe update a sub-API that you don't use. You only need to update your code when\nnew versions of the sub-APIs you use are released. For more information, see\n[Versioning](/merchant/api/guides/versioning).\n\nVersions that end in \"beta\" are subject to change or removal.\n| **Note:** During the Merchant API beta, we might make breaking changes without updating the major version. We'll give at least 30 days of notice before making a breaking change. For the duration of the beta, all sub-APIs will remain on v1beta."]]
