canonical: https://jentic.com/apis/googleapis.com/cloudchannel

# Google Cloud Channel API

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.

## For AI 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.

## Scope

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.

## Capabilities

- 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
- Transfer entitlements between reseller accounts
- Subscribe a Pub/Sub topic to customer and entitlement change events
- Run repricing operations for distributors managing channel partners
- Query eligible billing accounts for a customer before placing an order

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

| 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 | Register a Pub/Sub topic for entitlement change events |
| 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 |

## Key resources

- **Customers** — Reseller-owned customer records and Cloud Identity provisioning
- **Entitlements** — Customer subscriptions to Google Cloud, Workspace, Maps, and Chrome offers
- **Offers** — Purchasable offers and SKUs available to a customer
- **ChannelPartnerLinks** — Links between distributors and the channel partners they manage

## Why Jentic

- **Setup:** Wiring the Cloud Channel API by hand means setting up Google OAuth 2.0 reseller credentials, minting short-lived tokens against the apps.order scope, and addressing customer and account resources by name against cloudchannel.googleapis.com yourself. Through Jentic you install once, import the Cloud Channel API from the API Directory, store the OAuth credential once, and your agent calls it.
- **Permission scoping:** Cloud Channel puts the customer and account ids in the URL path (/v1/{+customer}, /v1/{+account}), so a rule can pin your agent to one customer: it can list purchasable offers and provision cloud identity for that customer and nothing else. You choose the operations it may call, so entitlement cancellation or suspension are not included unless you add them.
- **Credential handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Cloud Billing API** — Manages billing accounts and sub-accounts that fund reseller-provisioned customers
- **Cloud Identity API** — Manages users, groups, and devices in the Cloud Identity tenancy that Cloud Channel provisions
- **Google Workspace Admin SDK** — Configures Workspace settings for customers whose subscriptions are sold via Cloud Channel

## FAQ

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