Sharing Entitlements

Publishers can share their entitlements with GetFTR using the Google Subscriber Links Archive format. GetFTR selected this format because it is already widely adopted by publishers.

By sharing entitlements, publishers benefit from centralized entitlement checking, removing the necessity to develop and maintain their own entitlement APIs. Centralized entitlement checking reduces the need for entitlement requests to be routed to the publisher, thereby significantly lowering latency. Typically, entitlement requests through the GetFTR Centralized Entitlements API are resolved in under 10ms.

The GetFTR Centralized Entitlements API identifies a user’s institution based on their IPv4 address and performs DOI-level entitlement checks, considering institutional subscriptions and access rights to the requested content.

Onboarding

To onboard to the GetFTR Centralized Entitlements API, publishers must share their entitlements by providing a URL to their Google Subscriber Links Archive. This archive contains entitlement information for all of the publisher’s content.

Schedule

Entitlement ingestion can be scheduled flexibly—daily, bi-weekly, weekly, or monthly, and at specific days or times. This ensures that your entitlements are updated promptly, allowing the API to consistently access the most current information.

Authentication

The GetFTR Crawler identifies itself using the following IPv4 address:

108.128.195.86

Additionally, every request from the crawler includes this User-Agent header:

GetFTR Subscriber Links Agent

One or both identifiers should be added to your website’s whitelist to allow the GetFTR Crawler to access your entitlements.

⸻

Once the location and update schedule for your Google Subscriber Links Archive have been configured and the GetFTR Crawler is whitelisted, ingestion will commence at the next scheduled update. Subsequently, your entitlements will become available through the GetFTR Centralized Entitlements API.