Alma integrates with external systems, such as vendor systems, Enterprise Resource Planning (ERP) systems, metadata management systems, and remote storage systems, via standard protocols, such as S/FTP. This section describes how to configure the integrations between Alma and external systems. It is organized according to the external systems.

For more information about the industry standards that are supported by Alma, see the Standards Dashboard.


In general, configuring an integration with external system includes 2 parts:

  • Handle the data transition between Alma and the External system. e.g. map the exported invoices fields to the external system fields.
  • Define an External integration profile in Alma

The data transition handling, including XSDs and XML samples, is described in this section.

The External profile definitions in Alma are done inside Alma, and therefore is explained as part of the online-help. Note that a link to the relevant sections of the online-help is available as part of each integration explanation.


Alma integrations are illustrated in the following diagram:

For more information about the specific standard or integration, click on the link below.

Alma Domain Names

Ex Libris providers institutions with the required domain names to access Alma. The domain names are unique for each institution.

For most purposes, including all HTTP/S access, a single domain name is required. In all Alma documentation, this URL is referred to as <Alma domain>. An example <Alma domain>:

A second domain name is provided for configuring Primo’s access to Alma’s delivery; the second domain name is required for technical reasons to enable staff users to have both Alma and Primo open simultaneously in the same browser, and is relevant for those using regular Primo (not VE). This domain name is referred to in the documentation as <Alma delivery domain>. An example <Alma delivery domain>:

For more information regarding domain names, refer to Alma’s OLH.