CSS API overview

  • The CSS API manages your CSS and controls your CSS Products portfolio.

  • The CSS API and Merchant API serve different purposes and use different account types and IDs.

  • Use the CSS API (v1) with a CSS Domain ID for CSS account and product management.

  • Use the Merchant API (v1) with a standard Merchant Center ID for standard Merchant Center account and product management.

  • Do not use a CSS Domain ID with the Merchant API or a Merchant Center ID with the CSS API for product endpoints to avoid errors.

You can use the CSS API to manage your CSS and control your CSS Products portfolio.

The CSS API is a redesign of the CSS features in Content API for Shopping.

CSS API versus Merchant API

Understanding the distinction between the CSS API and the Merchant API is key to effectively managing your products. Each API serves a different purpose and operates on different account types and ID spaces:

  • CSS API (v1): Use this API for all functionalities related to managing CSS accounts and their associated CSS products. This API uses the css.googleapis.com hostname and requires a CSS Domain ID for product operations.

    • Example: POST https://css.googleapis.com/v1/accounts/{cssDomainId}/cssProductInputs:insert

  • Merchant API (v1): Use this API for all functionalities related to standard Merchant Center accounts and their products. This API uses the merchantapi.googleapis.com hostname and requires a standard Merchant Center ID.

    • Example: POST https://merchantapi.googleapis.com/v1/accounts/{merchantId}/productInputs:insert

Key takeaway: Don't use a CSS Domain ID with the Merchant API for product endpoints, and don't use a Merchant Center ID with the CSS API product endpoints. Using the wrong ID with the wrong API will result in errors.

The CSS API and Merchant API together replace the older Content API for Shopping (v2.1), which should no longer be used.

Here are some reasons to upgrade to the CSS API:

See Get started for more information.

Next
Quickstart