The Cloud Channel API gives Google Cloud resellers a unified surface for managing customers, entitlements, offers, and subscriptions across Google Cloud, Google Workspace, Maps, and Chrome. Resellers can provision Cloud Identity for new customers, place orders against purchasable offers, transfer entitlements between accounts, and subscribe to Pub/Sub feeds that publish customer and entitlement change events. The API also exposes channel-partner-specific reporting and repricing operations for distributors managing nested partner accounts.
46 endpointsGoogle Content API for Shopping lets merchants programmatically manage the product listings, accounts, datafeeds, and shopping ads configuration that surface across Google Shopping, Free Listings, and Buy on Google. Retailers can upload product data in batches, monitor product status and disapprovals, manage local inventory and store codes, and configure shipping and tax settings. The API supports multi-account hierarchies for agencies and large retailers, and includes endpoints for orders, returns, and promotions on supported markets.
135 endpointsThe Google Workspace Reseller API lets authorized partners place and manage orders for Google Workspace and other Google subscription products at scale, mirroring functionality that resellers otherwise perform manually in the Channel Services console. Operations cover customer creation and updates, subscription orders, plan changes, seat changes, renewal settings, suspension and reactivation, and trial-to-paid conversion. Resellers use it to drive provisioning workflows, billing transitions, and customer lifecycle management directly from their own systems.
17 endpointsThe Manufacturer Center API lets brand manufacturers submit and maintain authoritative product data and product certifications used across Google's shopping surfaces. Brands push canonical attributes such as GTIN, MPN, brand name, image, product detail, and feature descriptions, plus regulatory or industry certifications, so retailers and Google's shopping experiences show accurate manufacturer-supplied content. The API is scoped per Manufacturer Center account and is distinct from Merchant Center, which is used by retailers to upload their own offers.
8 endpointsStep 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.