COUNTER support

If you are a syndicating platform and would like to provide COUNTER  compliant off-platform usage data to syndicating publishers, GetFTR can provide the publisher’s internal customer IDs in entitlement responses, which when added to usage data, enable aggregation of on and off-platform usage by the publisher.

GetFTR Entitlements API

To receive customer IDs in responses, integrators must set up their configuration  like this:

• Disable the GetFTR Entitlement Cache for their requests
• Disable the GetFTR OA Service for their requests
• Enable CustomerIDs in responses

This ensures that they will receive unaltered responses from publisher APIs and the CES, which can contain the publisher’s internal customer ID for each entitlement, if they support the use case:

"org": {
    "ipv4": "1.2.3.4",
    "customerID": "1234567890"
}

GetFTR Centralised Entitlements Service

Direct integrators of the GetFTR Centralised Entitlements Service must set the "X-GETFT-FEATURE-PUBLISHER-IDS" header to the value of "true" in their requests to receive internal customer IDs in the API responses. The IDs will be included in the "publisherIds" array of the entitlement response:

{
    "items": [
        {
            "doi": "10.1234/doi",
            "entitled": true,
            "document": "https://document-link.com",
            "accessType": "PAID",
            "identifiers": [
                0
            ],
            "publisherIds": [
                {
                    "source": "publisher.name",
                    "customerId": "1234567890"
                }
            ],
            ...
        }
    ]
}