Merchant API design

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.

The Merchant API includes the following sub-APIs:

  • Accounts: Manage merchant accounts at scale.
  • Products: Manage product data, like price and availability.
  • Data sources: View and manage the data sources for your products.
  • Inventories: Showcase your products by store or region on Google.
  • Reports: View data on your products, performance, and competitive landscape across Google.
  • Promotions: Create and manage promotions to showcase special offers for your products.
  • Local feeds partnership: Upload your local product inventory feed.
  • Conversion sources: Manage conversion sources for your account.

The Merchant API is in beta and will include more sub-APIs over time.

Transport

The Merchant API's default transport mechanism is gRPC. You can also use REST.

See the quickstart guide for more information.

Versioning

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.