Requesting Alma API keys
Alma provides the ability to access data via API calls, using scripts or tools like Postman.
We have a daily limit of API calls for all work done by the libraries, which includes requesting items, accessioning and managing records between CAIASoft and Alma, printing spine labels, and other workflows.
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.
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 areas include:
Acquisition: Acquisitions - Ex Libris Developer Network
Analytics: Analytics - Ex Libris Developer Network
Bibs: Bibliographic Records and Inventory - Ex Libris Developer Network
Configuration: Configuration and Administration - Ex Libris Developer Network
Electronic: Electronic Resources - Ex Libris Developer Network
Partners (Resource Sharing): Resource Sharing Partners - Ex Libris Developer Network
Task-lists: Task Lists - Ex Libris Developer Network
Note that read/write access to the Configuration API will generally not be granted.
If you have an application that requires that access, please be sure to include a full explanation in the support ticket for LSIS review.
API Key Distribution
API keys will be created by LSIS staff.
They will create distinct API keys for separate use cases, so that if a particular API key needs to be reset, it does not break multiple services.
Keys will be distributed via 1Password vaults.
Key requests need to specify
which environment the key is for - production or premium sandbox - you need two keys if you need to do the work in both environments
what type of access is needed
whether the access needed is read-only, or read/write.
Areas of access:
Acquisition
Analytics
Bibliographic Records and Inventory (Bibs)
Configuration
Courses
Electronic
Task-lists
Users
The API key breakdown roughly corresponds to how the API documentation is organized on REST APIs - Ex Libris Developer Network