If you are using a system to harvest COUNTER 5 data via the SUSHI API, you might need to make a change to your settings.
SUSHI harvesting can be done with a system like the ALMA Analytics module, LibInsights, or with a number of other systems. When the system communicates with our servers to get your usage reports, two pieces of information are sent along to identify your organization: a customer_id and an api_key. The customer_id is your so called “business partner ID” and has been the same since we started providing COUNTER 5 data.
However, until late 2020 the api_key was the same for all customers, namely the api_key was C1UrvZ1891CwS2iUcPQizrCv25La2r3J. Now we give each customer their own unique api_key and from later this month the generic api_key will not work any longer. You can find your organization’s unique api_key on [the Access page] of the Librarian Portal.
Diana Petrowicz is a Marketing Manager in the Institutional Marketing team, based in the London office. She manages 'The Link' blog, creates web content for the librarian webpage and produces the Library Link newsletter to keep the librarian community updated on trends and news.