Stay organized with collections
Save and categorize content based on your preferences.
We designed the Merchant API to be familiar to Content API for Shopping
developers, yet simpler and more flexible. Here's some detailed information on
the design of the Merchant API:
Sub-APIs
The Merchant API is a collection of sub-APIs. The sub-APIs are groups of related
services and resources. This design means you can choose to use only the
sub-APIs needed for your unique integration.
Sub-APIs are versioned separately. This means you don't need to do anything if
we update a sub-API that you don't use. You only need to update your code when
new versions of the sub-APIs you use are released.
Versions that end in "beta" are subject to change or removal.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-02-06 UTC."],[[["The 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."],["It's designed for flexibility, allowing developers to choose and use only the specific sub-APIs relevant to their needs."],["The API supports both gRPC and REST transport mechanisms and features independent versioning for each sub-API, minimizing the impact of updates on existing integrations."],["Although in beta and subject to change, Google provides at least 30 days' notice for breaking changes, ensuring developers have ample time to adapt."],["The Merchant API shares similarities with the Content API for Shopping but aims to provide a simpler and more adaptable development experience."]]],[]]