GetFTR (Get Full Text Research) is a publisher-run technical service that checks, in real time, whether a specific reader is entitled to access a specific article — at the moment they encounter it in a search engine, citation manager, or other discovery tool, before they ever click through to a publisher’s site. It answers a narrow but high-friction question: “does this reader’s institution have rights to this exact DOI, right now?” GetFTR does not authenticate the reader itself; it checks entitlement and hands the actual access-control decision back to the publisher. This guide explains what GetFTR is, who runs it, how the entitlement check actually works, where researchers encounter it, and how it relates to open access and to the separate, complementary problem of federated authentication.
What GetFTR is and who runs it
GetFTR was announced in December 2019 by a group of five major scholarly publishers — the American Chemical Society (ACS), Elsevier, Springer Nature, Taylor & Francis, and Wiley — as a shared, freely available API that discovery platforms could use to check article-level entitlements directly with publishers. The service began operating in 2020. It is publisher-led and publisher-funded: it grew out of publishers’ own initiative rather than a library-, funder-, or standards-body-led process, which is a meaningful distinction from services like DOI registration or open access mandates that are typically governed by multi-stakeholder or nonprofit bodies. According to GetFTR’s own site, more than 80 publishers now participate, including Elsevier, Wiley, Springer Nature, Oxford University Press, SAGE, Taylor & Francis, the American Chemical Society, IEEE, IOP Publishing, Thieme, PNAS, and EBSCO Information Services, among others.
Because GetFTR was built by publishers for publisher content, its scope is inherently publisher-side: it can only check entitlements at publishers that have integrated with it. A DOI belonging to a non-participating publisher simply won’t return a GetFTR entitlement result. That publisher-led origin also drew early scrutiny from librarians and the library-technology community when the service launched, chiefly around governance transparency and how the underlying usage/entitlement data would be handled — concerns that shaped later public discussion of GetFTR alongside its more library- and standards-body-governed counterpart, SeamlessAccess (see the comparison below).
How the entitlement check actually works
The mechanics are what make GetFTR useful at the point of discovery rather than after a redirect. When a discovery tool (a search engine, citation manager, or database) displays a result with a DOI, it can call the GetFTR API with that DOI. GetFTR uses the DOI to identify which publisher owns the article — via the Crossref API — and routes the entitlement query to that publisher’s own systems. The publisher then checks whether the requesting reader is entitled to access, using one of two signals passed with the request: a SAML EntityId identifying the reader’s institution, or the reader’s IP address (commonly used for on-campus, IP-authenticated access). Critically, GetFTR itself does not log the reader in or verify their identity — it relies on whichever institutional signal is already available and lets the publisher’s own access-control system make and enforce the actual decision. GetFTR describes this pattern as usable without requiring full federated authentication up front, sometimes referred to as deferred authentication: the entitlement check can happen before the reader is asked to authenticate at all, and full sign-in (if the publisher requires it to actually view the article) only happens at the point of click-through.
The result returned to the discovery tool is simple: whether the reader appears entitled to the full text at that publisher, so the interface can show a direct “view PDF” or “read article” link instead of a generic, and often paywalled, publisher landing page. GetFTR also layers in retraction and errata status, sourced from Crossref and Retraction Watch, so a discovery tool can flag a retracted or corrected article to the reader at the same point of discovery.
Where researchers actually encounter GetFTR
Researchers rarely visit GetFTR directly. It is designed to be invisible infrastructure embedded inside the tools researchers already use to find literature: reference managers and discovery platforms including Mendeley, ReadCube, ResearchGate, Scopus, Semantic Scholar, and Clarivate products, among other participating platforms, that have integrated the GetFTR API. GetFTR also offers a free browser extension that adds entitlement and retraction-status checking to pages a researcher visits directly, rather than only inside an integrated discovery tool.
For research offices and libraries, the practical effect is fewer researchers hitting a paywall page and manually hunting for an accessible copy, forwarding requests to the library, or emailing a corresponding author — friction that GetFTR is explicitly designed to remove at the moment a reader is deciding whether an article is worth pursuing.
GetFTR vs. SeamlessAccess: entitlement-checking vs. authentication
GetFTR is frequently mentioned alongside SeamlessAccess, and the two are often confused, but they solve different problems in the same access chain:
- GetFTR checks entitlement — whether a specific reader’s institution has rights to a specific article — and surfaces that answer at the point of discovery, before the reader clicks through.
- SeamlessAccess handles authentication — letting a researcher sign in with their institutional credentials via federated single sign-on, so a publisher (or any participating service) can recognize who the reader’s institution is in the first place.
The two are complementary rather than competing: GetFTR’s entitlement check can rely on the same institutional identifier (a SAML EntityId) that federated authentication services like SeamlessAccess establish, and a reader who has already signed in via SeamlessAccess-style federated authentication generally has a smoother, more accurate GetFTR entitlement check than one relying on IP address alone. They are also governed differently. SeamlessAccess grew out of the RA21 (Resource Access for the 21st Century) initiative and operates under a multi-stakeholder coalition with library-, standards-, and identity-federation-sector participants, whereas GetFTR was built and is run by the publishers themselves. That governance difference was a significant part of the early library-sector commentary on the two services when both launched in the same period (2019–2020).
In short: SeamlessAccess answers “who is this reader, from an identity standpoint?” while GetFTR answers “does this reader’s institution have rights to this specific article, right now?” A researcher can benefit from either independently, but the smoothest discovery-to-full-text experience uses both together.
Why this matters for research administration
Access friction is a recurring, quantifiable drag on research productivity: a researcher who cannot immediately tell whether their institution already has access to an article either abandons the search, requests an author’s accepted manuscript some other way, or routes a request through the library — all slower than clicking a working link. GetFTR is one of a small set of infrastructure services (alongside institutional repositories, library link resolvers, and open-access discovery tools) aimed at closing that gap by making entitlement information available at the point a reader is actually deciding whether to pursue an article, rather than only after a failed click-through. It does not replace a library’s subscription or licensing relationship with a publisher — it surfaces the existing entitlement faster and more precisely.
Frequently asked questions
Is GetFTR free to use?
Yes, for readers and for the discovery tools that integrate it. GetFTR describes itself as a freely available API for discovery platforms, and the browser extension is also free to install.
Does GetFTR give me access I wouldn’t otherwise have?
No. GetFTR only checks and surfaces entitlements that already exist — through an institutional subscription, an open-access license, or another access route the publisher recognizes. It does not grant new access.
Is GetFTR the same as SeamlessAccess?
No. GetFTR checks whether you’re entitled to a specific article; SeamlessAccess handles signing you in via your institution’s federated identity so publishers know who you are. They are designed to work together, not to replace each other.
Do all publishers support GetFTR?
No. GetFTR only works for publishers that have integrated with its API — more than 80 as of this writing, including several of the largest scholarly publishers — so entitlement checks are unavailable for articles from non-participating publishers.
Does using GetFTR require my institution to do anything?
Entitlement checks can work off IP address alone for on-campus access, but they are more accurate when paired with an institutional SAML identifier, the same kind of identifier used in federated authentication services like SeamlessAccess.
