HumDay

Gets the reader entitlements for a publication reader in Google Reader Revenue Subscription Linking

A documented Google Reader Revenue Subscription Linking operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.

Automate this

What this operation does

Gets the reader entitlements for a publication reader.

  • GETReads data · publicationsreaderrevenuesubscriptionlinking.googleapis.com/v1/{name}

How HumDay uses it

  1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
  2. The contract names it. Before anything is built, you see exactly which Google Reader Revenue Subscription Linking operations the program may use, and this is one of them.
  3. You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.

Other Google Reader Revenue Subscription Linking operations

All 3 Google Reader Revenue Subscription Linking operations

Questions

Can HumDay gets the reader entitlements for a publication reader in Google Reader Revenue Subscription Linking?
Yes. This operation is published in Google Reader Revenue Subscription Linking's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
Does this change anything in my Google Reader Revenue Subscription Linking account?
No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Google Reader Revenue Subscription Linking.
Do I need to write code?
No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Google Reader Revenue Subscription Linking account.

Where this came from

Read from a published API description for Google Reader Revenue Subscription Linking at readerrevenuesubscriptionlinking.googleapis.com/$discovery/rest?version=v1. The description above is the provider’s own wording, not ours. Last published 2023-04-21.