Google Reader Revenue Subscription Linking API
Browse all Google APIs✓ Official Vendor SpecMediaContent Deliveryoauth23 EndpointsREST
For Agents
Link, update, and unlink Google reader identities with publisher subscriptions so reader entitlements are recognized across Google surfaces.
Use for: I need to link a Google reader to an active publisher subscription, Update the entitlement metadata when a reader upgrades their plan, Remove the subscription link when a reader cancels, Retrieve the current entitlement state for a Google reader
Not supported: Does not process payments, run paywalls, or send subscriber email — use only to link, update, and unlink Google reader identities with publisher subscription records.
The Reader Revenue Subscription Linking API lets news publishers tie a Google reader identity to a publisher subscription so that signed-in Google users see their entitlements honored across Google surfaces. Publishers exchange reader IDs and subscription metadata with Google to mark a reader as entitled, update existing entitlements, or remove the link when a subscription ends. The API is the connective tissue between a publisher's subscription system of record and Google's reader-facing surfaces.
Install Jentic One Beta
Connect the Reader Revenue Subscription Linking API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Reader Revenue Subscription Linking 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.
1
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 | sh2
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 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.
Capabilities
What an agent can do with Reader Revenue Subscription Linking API.
Create or update a reader-to-subscription link with the publisher's entitlement metadata
Retrieve the current subscription link for a Google reader identity
Delete a reader-subscription link when a reader cancels or unsubscribes
Synchronize entitlement state from a publisher's subscription system of record into Google
Honor reader entitlements consistently across Google reader-facing surfaces
Drive subscription linking from webhook handlers when subscriptions change
Use Cases
Patterns agents use Reader Revenue Subscription Linking API for, with concrete tasks.
★ Initial Reader Onboarding
When a reader signs in to a publisher's site with their Google account and their subscription is verified, the publisher calls Subscription Linking to register the entitlement with Google. From then on, the reader's entitlement is honored on Google reader surfaces.
Call PATCH /v1/publications/{publication}/readers/{reader_id} with subscription metadata when a verified reader signs in for the first time.
Subscription Lifecycle Sync
Publishers run their subscription system of record (Stripe, Recurly, Zuora, in-house) and need entitlement changes there to flow to Google. Webhook handlers on the publisher side translate billing events into Subscription Linking API calls so Google's view of the entitlement always matches the source of truth.
When the billing system fires a subscription.updated webhook, look up the linked Google reader and call the upsert endpoint with the new plan tier and renewal date.
Cancellation and Unlink
When a reader cancels or their subscription lapses, the publisher must remove the entitlement link so Google does not continue to show the reader as entitled. Subscription Linking exposes a delete operation that performs this unlink cleanly.
When a reader cancels, call DELETE /v1/publications/{publication}/readers/{reader_id} to remove the entitlement from Google.
Agent-Driven Entitlement Reconciliation
An agent monitors the publisher's billing data and reconciles entitlement state with Google through Jentic, calling the Subscription Linking API to add, update, or remove links so the Google view of who is entitled stays in sync with the publisher's system of record.
Search Jentic for link a google reader to a subscription, load the schema for the readers upsert operation, and execute it for the affected reader.
Key Endpoints
3 endpoints — the reader revenue subscription linking api lets news publishers tie a google reader identity to a publisher subscription so that signed-in google users see their entitlements honored across google surfaces.
METHOD
PATH
DESCRIPTION
GET
/v1/{+name}
Retrieve a reader-subscription link
PATCH
/v1/{+name}
Create or update a reader-subscription link
DELETE
/v1/{+name}
Delete a reader-subscription link
GET
/v1/{+name}
Retrieve a reader-subscription link
PATCH
/v1/{+name}
Create or update a reader-subscription link
DELETE
/v1/{+name}
Delete a reader-subscription link
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Google OAuth 2.0 credentials are stored encrypted in the Jentic vault. Scoped, short-lived access tokens are issued per call so the publisher's OAuth client secret and refresh token never enter the agent context.
Intent-based discovery
Agents search Jentic by intent (link a reader, unlink a reader, get reader entitlement) and Jentic returns the matching Subscription Linking operation with its input schema, removing the need to interpret the discovery doc for a three-endpoint API.
Time to first call
Direct integration takes 1-3 days because the auth path runs through Reader Revenue Manager and webhook handlers must be wired to the publisher's billing system. Through Jentic: under 1 hour for the API calls themselves once the OAuth setup is in place.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Reader Revenue Subscription Linking API through Jentic.
What authentication does the Reader Revenue Subscription Linking API use?
The API uses Google OAuth 2.0 with publisher-scoped credentials issued through the Reader Revenue Manager onboarding. Through Jentic the OAuth credentials live encrypted in the vault and short-lived access tokens are injected at call time so the refresh token never enters the agent context.
Does this API process payments or charge subscribers?
No, billing stays with the publisher's existing system. This API only links a Google reader identity to a subscription record so Google can recognize the entitlement on Google surfaces.
What are the rate limits for the API?
The API exposes three operations and is intended for event-driven calls in response to subscription lifecycle changes. Rate limits are documented by the Reader Revenue Manager team and are sized for normal subscriber-event throughput, not for full-base reconciliation sweeps in tight loops.
How do I unlink a reader through Jentic?
Search Jentic for unlink a google reader from a subscription, load the schema for the readers delete operation which maps to DELETE /v1/{+name} on a reader resource, and execute it with the reader's resource name when the subscription is cancelled.
Is the Reader Revenue Subscription Linking API free?
API access is included with Reader Revenue Manager onboarding for eligible publishers and is not separately metered. Eligibility and onboarding details are documented on the Reader Revenue Manager publisher site.
How do I update an entitlement when a reader changes plan?
Call the upsert operation on the reader resource with the new plan tier, renewal date, and any other entitlement metadata; the API replaces the prior link in place rather than requiring a delete-then-create.
GET STARTED