For Agents
Provision and manage Google reseller subscriptions on behalf of partner-channel end users — create, cancel, suspend, resume, extend, and entitle Google product subscriptions.
Get started with Payments Reseller Subscription API in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"provision a google reseller subscription"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with Payments Reseller Subscription API API.
Provision a new subscription on behalf of an end user with a chosen product and promotion
List products available for resale and the promotions a user qualifies for
Cancel an active subscription or undo a pending cancellation before it takes effect
Suspend and later resume a subscription for billing or compliance reasons
GET STARTED
Use for: Provision a new YouTube Premium subscription for a reseller customer, Cancel an active reseller subscription on customer request, Find which promotions a reseller customer is eligible for, Suspend a subscription whose payment has failed
Not supported: Does not collect end-user payments, manage Google Cloud billing accounts, or sell to retail consumers — use for partner-channel Google product subscription lifecycle only.
The Payments Reseller Subscription API lets approved Google partners manage subscriptions on behalf of end users for Google products (such as YouTube Premium) sold through reseller channels. It exposes operations to find eligible promotions, list available products, provision a subscription for a user, and run lifecycle actions including cancel, suspend, resume, extend, undo cancel, and entitle. Use it to integrate Google subscription billing into a partner's checkout flow, manage post-sale lifecycle events, and apply qualifying promotions. The spec exposes 13 endpoints.
Extend a subscription's billing cycle to align with partner-side commitments
Entitle a subscription to grant the user access after partner-side fulfilment
Patterns agents use Payments Reseller Subscription API API for, with concrete tasks.
★ Partner-channel subscription provisioning
Provision Google product subscriptions through a partner's checkout flow — for example, a telco bundling YouTube Premium with a mobile plan. The API takes the product, end-user identifier, and an applicable promotion, and returns a subscription resource that the partner can confirm and entitle. Suitable for resellers integrating Google subscriptions into their own commerce stack.
Call POST /v1/{+parent}/subscriptions:provision with the product partners/p/products/youtube_premium, the end user's partnerUserToken, and the eligible promotion identifier.
Lifecycle management — cancel, suspend, extend
Manage post-sale lifecycle events for Google reseller subscriptions in response to partner customer-care actions. Cancel when the user requests termination, suspend when payment fails, resume when payment is restored, and extend the term for goodwill or contract alignment. Each action is a discrete API call with a returned subscription resource.
POST to /v1/{+name}:suspend for an active subscription whose latest payment failed, then POST to /v1/{+name}:resume once the partner billing system reports recovery.
Promotion eligibility checks
Query which promotions an end user is eligible for before showing a price in checkout, so the partner UI can offer the correct discount tier. The API's findEligible operation accepts the user identifier and returns active promotions that can be redeemed at provisioning. This avoids surfacing a promotion the user cannot redeem and reduces post-checkout failures.
Call POST /v1/{+parent}/promotions:findEligible with the partner user token and pre-select the highest-value eligible promotion in checkout.
Agent-driven reseller support via Jentic
A support agent embedded in a partner's customer-care console can use Jentic to suspend, resume, or extend a reseller subscription based on conversation context. Credentials stay in the Jentic vault, so the agent runs under a scoped reseller token with audit trail. Useful for telco support bots that handle subscription lifecycle without escalating.
Use Jentic to find the cancel-subscription operation, load its schema, and execute it for the subscription referenced in the support ticket, then reply with the cancellation effective date.
13 endpoints — the payments reseller subscription api lets approved google partners manage subscriptions on behalf of end users for google products (such as youtube premium) sold through reseller channels.
METHOD
PATH
DESCRIPTION
/v1/{+parent}/subscriptions:provision
Provision a new reseller subscription
/v1/{+name}:cancel
Cancel an active subscription
/v1/{+name}:undoCancel
Undo a pending cancellation
/v1/{+name}:suspend
Suspend an active subscription
/v1/{+name}:resume
Resume a suspended subscription
/v1/{+name}:extend
Extend a subscription term
/v1/{+name}:entitle
Entitle access to a provisioned subscription
/v1/{+parent}/promotions:findEligible
Find eligible promotions for a user
/v1/{+parent}/subscriptions:provision
Provision a new reseller subscription
/v1/{+name}:cancel
Cancel an active subscription
/v1/{+name}:undoCancel
Undo a pending cancellation
/v1/{+name}:suspend
Suspend an active subscription
/v1/{+name}:resume
Resume a suspended subscription
Three things that make agents converge on Jentic-routed access.
Credential isolation
Reseller OAuth 2.0 tokens are minted from a service account stored in the Jentic vault (MAXsystem). Agents call the API under scoped, short-lived tokens — the service-account key never enters their context.
Intent-based discovery
Agents search Jentic with intents like provision reseller subscription or cancel subscription and Jentic returns the matching operation, its scopes, and its input schema.
Time to first call
Direct integration: 2-3 days to handle reseller onboarding, OAuth, and lifecycle action error paths. Through Jentic: under 1 hour — search, load, execute.
Alternatives and complements available in the Jentic catalogue.
Cloud Billing API
Cloud Billing manages Google Cloud usage billing, not partner-resold subscriptions
Use Cloud Billing when the agent needs to manage Google Cloud charges; use Payments Reseller Subscription when the goal is partner-channel Google product subscriptions.
Google Play Android Publisher API
Android Publisher manages in-app subscriptions sold through Google Play directly
Use Android Publisher when the subscription is sold through the Play Store; use Payments Reseller Subscription when it's sold through an approved Google partner.
YouTube Data API
YouTube Data exposes the user-facing YouTube product that is often the resold subscription
Use YouTube Data when the agent needs to read or modify the user's YouTube content; use Payments Reseller Subscription when it needs to manage the YouTube Premium subscription record.
Specific to using Payments Reseller Subscription API API through Jentic.
What authentication does the Payments Reseller Subscription API use?
The API uses Google OAuth 2.0 with the cloud-platform scope and is restricted to approved reseller partners. Through Jentic, tokens come from a service account stored in the Jentic vault.
Can I cancel a subscription and undo the cancellation?
Yes. POST to /v1/{+name}:cancel to schedule a cancellation, then POST to /v1/{+name}:undoCancel before the effective date if the customer changes their mind.
What are the rate limits for this API?
Google does not publish a single number; per-partner quotas are agreed during onboarding. Treat lifecycle calls as low-frequency per subscription and back off on 429 rather than retrying immediately.
How do I provision a subscription through Jentic?
Search Jentic for provision reseller subscription, load the schema for POST /v1/{+parent}/subscriptions:provision, and execute it with the product, partnerUserToken, and eligible promotion. Jentic returns the subscription resource for confirmation.
Does this API expose end-user payment instruments?
No — the partner is responsible for collecting payment from the end user. This API manages the subscription record on Google's side; the partner-side billing system handles the actual payment.
How do I extend a subscription's term?
POST to /v1/{+name}:extend with the desired extension duration; the response confirms the new billing cycle end date.
/v1/{+name}:extend
Extend a subscription term
/v1/{+name}:entitle
Entitle access to a provisioned subscription
/v1/{+parent}/promotions:findEligible
Find eligible promotions for a user