Client libraries
We recommend using a client library, because they provide improved security and
language integration, and support user authorization. The Merchant API client
libraries use gRPC and are designed to work with our code
samples in the same language.
Here are our most recent client libraries and code samples:
| Sub-API |
Client libraries |
Code samples |
| Accounts |
|
| Conversions |
|
| Data sources |
|
| Inventories |
|
| Local feeds partnership (LFP) |
|
| Notifications |
|
| Products |
|
| Promotions |
|
| Quota |
|
| Reports |
|
| Reviews |
|
To set up a client library, download and run one of our code
samples from
GitHub. See the language pages in the left sidebar for installation
instructions.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-02-17 UTC.
[null,null,["Last updated 2025-02-17 UTC."],[[["Client libraries enhance security, integrate with your programming language, and facilitate user authorization."],["The Merchant API client libraries utilize gRPC and align with provided code samples."],["Current client libraries and code samples are available for Java and PHP across various sub-APIs like Inventories, Products, and Reports."],["To begin, download and execute a code sample from GitHub and refer to the language-specific setup instructions."]]],[]]
