Google Cloud Channel API

Name: Cloud Channel API
Brand: Cloud Channel API
Availability: InStock

✓ Official Vendor SpecE CommerceOrder Managementoauth246 EndpointsREST

Install Jentic One Beta

Connect the Cloud Channel API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cloud Channel API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 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 | sh

Step 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 instance

Jentic 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.

Capabilities

What an agent can do with Cloud Channel API.

Provision Cloud Identity for a new reseller customer

List purchasable offers and SKUs available to a customer

Create, suspend, or cancel entitlements that represent a customer's subscription

GET STARTED

Start building with Cloud Channel API

Explore with Jentic

View OpenAPI Document

For Agents

Manage Google Cloud reseller customers, entitlements, offers, and Pub/Sub change subscriptions across Google Cloud, Workspace, Maps, and Chrome. Useful for partner provisioning, billing, and lifecycle automation.

Use for: I need to provision Cloud Identity for a new Workspace customer, List every purchasable offer for a customer, Create a Workspace Business Standard entitlement for a customer, Transfer a customer's existing Workspace entitlement to our reseller account

Not supported: Does not configure end-user Workspace settings, charge end-customer credit cards, or manage GCP runtime resources - use for reseller customer, entitlement, and offer management only.

Use Cases

Patterns agents use Cloud Channel API for, with concrete tasks.

★ New Reseller Customer Onboarding

Resellers use the Cloud Channel API to onboard a new customer end to end: create the customer record, provision Cloud Identity, look up purchasable offers, place an order for the chosen SKU, and confirm the entitlement is active. The flow can run unattended in under a minute and replaces a previously manual sequence in Partner Sales Console.

Call POST /v1/{customer}:provisionCloudIdentity, then POST /v1/{parent}/entitlements with the chosen offer name to create the subscription

Entitlement Lifecycle Automation

Billing platforms use the entitlement endpoints to suspend, change offer, or cancel a customer's subscription based on internal events such as non-payment or upgrade requests. Each lifecycle action is a long-running operation, so callers poll for completion before reporting status to the customer.

Call POST /v1/{name}:suspend with the entitlement resource name, then poll /v1/{name}/operations until the operation completes

Real-Time Entitlement Change Notifications

Operations teams subscribe a Pub/Sub topic to the channel partner account so that any customer or entitlement change publishes a message. Downstream systems update CRM, billing, and provisioning records without polling.

Call POST /v1/{account}:register with the Pub/Sub topic name to begin receiving entitlement change events

AI Agent Reseller Operations via Jentic

An agent invoked by a partner ops team uses the Cloud Channel API to provision new customers, place orders, and answer status queries. Through Jentic, the agent searches by intent, loads the operation schema, and executes against the partner account without ever holding the underlying OAuth refresh token.

Search Jentic for 'create google workspace entitlement', execute against POST /v1/{parent}/entitlements with the offer name, and report the resulting entitlement state

Key Endpoints

46 endpoints — 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.

METHOD

PATH

DESCRIPTION

GET

/v1/products

List purchasable products

GET

/v1/{+customer}:listPurchasableOffers

List offers a customer can buy

POST

/v1/{+customer}:provisionCloudIdentity

Provision Cloud Identity for a new customer

POST

/v1/{+account}:register

POST

/v1/{+account}:unregister

Unregister a Pub/Sub topic

GET

/v1/{+account}:listSubscribers

List Pub/Sub subscribers on the reseller account

GET

/v1/{+customer}:queryEligibleBillingAccounts

List billing accounts eligible for a customer

GET

/v1/products

List purchasable products

GET

/v1/{+customer}:listPurchasableOffers

List offers a customer can buy

POST

/v1/{+customer}:provisionCloudIdentity

Provision Cloud Identity for a new customer

POST

/v1/{+account}:register

POST

/v1/{+account}:unregister

Unregister a Pub/Sub topic

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Cloud Channel OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a Google Workspace entitlement' or 'provision cloud identity for a customer', and Jentic returns the matching Cloud Channel operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Cloud Channel API through Jentic.

What authentication does the Cloud Channel API use?

The Cloud Channel API uses OAuth 2.0 with the apps.order scope. Tokens are issued for a delegated reseller service account configured in Partner Sales Console. Through Jentic, the OAuth credential lives in your Jentic One instance and the agent receives a short-lived access token only - the underlying credential never enters agent context.

Can I provision a new Workspace customer with this API?

Yes. Create a customer with POST /v1/{parent}/customers, then call POST /v1/{customer}:provisionCloudIdentity to create the customer's Cloud Identity tenancy. After that, place an entitlement order against a purchasable offer to activate Workspace, Cloud, Maps, or Chrome SKUs.

What are the rate limits for the Cloud Channel API?

Cloud Channel API quotas are published per-method in the Google Cloud console under the Cloud Channel API quota page; typical defaults are several thousand read requests per minute per project, with much lower per-minute limits on customer creation and entitlement mutation operations.

How do I receive entitlement change events through Jentic?

Search Jentic for 'register cloud channel pubsub' and execute against POST /v1/{account}:register with your Pub/Sub topic. Cloud Channel publishes a message for every customer and entitlement change so downstream agents can react without polling.

Can I transfer an existing customer's entitlements to my reseller account?

Yes. Use the entitlement transfer operations (transferEntitlements and transferEntitlementsToGoogle on the customers resource). Transfers are long-running operations and require the customer to authorise the move. The API enforces eligibility based on the offer and the original reseller relationship.

Is the Cloud Channel API free?

The Cloud Channel API itself has no per-call charge for authorised resellers. Customer-facing offers and SKUs are billed to the reseller via the linked billing account at the rates negotiated in the partner agreement.

Can I limit what my agent is allowed to do with the Cloud Channel API?

Yes. Because Jentic One is self-hosted, you set the rules in your own instance, and Cloud Channel puts the customer and account ids in the URL path (/v1/{+customer}, /v1/{+account}), so a rule can pin your agent to a single customer or account. You decide exactly which operations it may call, so you can let it list purchasable offers and provision Cloud Identity for that customer while excluding entitlement suspension or cancellation. The OAuth credential stays in your instance and is injected at execution time, so the agent never holds the reseller token itself.

Google Cloud Channel API

Connect the Cloud Channel API to your agent

Capabilities

Start building with Cloud Channel API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs