...
Because we do not have unlimited API access, we are being cautious in distributing API keys beyond those needed for core library workflows until we have a better understanding of how our transactions are counted.
When we cutover to Alma, we will begin to have API reporting tools available that will tell us how our usage of APIs compares to our cap number, and we will have a better sense of how broadly we can distribute API keys for various projects. In mid-August, we will also begin to have access to our premium sandbox, which will be a test environment with a snapshot of Duke’s data, allowing for testing of API tools prior to using them against production Alma.
We will update this page when we begin accepting requests for API keys.
In the meantime, if If an API key is needed for a workflow, please open a support ticket via https://support.lib.duke.edu and assign it to the Alma queue.
You must include the following:
A description of the project or integration that you need the key for;
Whether you need a key/keys for Alma production, Alma premium sandbox, or both;
What areas of Alma the keys need access to, and whether the access should be read-only, or read/write.
API Key areas
Acquisition: https://developers.exlibrisgroup.com/alma/apis/acq/
Analytics: https://developers.exlibrisgroup.com/alma/apis/analytics/
Configuration: https://developers.exlibrisgroup.com/alma/apis/conf/
Access to configuration that requires read/write access should be explained fully in the request
Courses: https://developers.exlibrisgroup.com/alma/apis/courses/
Electronic: https://developers.exlibrisgroup.com/alma/apis/electronic/
Partners (Resource Sharing): https://developers.exlibrisgroup.com/alma/apis/partners/
Task-lists: https://developers.exlibrisgroup.com/alma/apis/tasklists/
Users: https://developers.exlibrisgroup.com/alma/apis/users/
API Key Distribution
API keys will be created by LSIS staff.
...