Import exposures from file

Imports exposure data into an EDM from flat files uploaded to a storage bucket.

Prior to running this operation, you must upload the exposure data to a storage bucket using AWS. Once uploaded to the storage bucket, you can use this operation to import the data into the EDM.

This operation represents the final step in both the MRI and ALM Import workflows. Depending on the value specified for importType, initiaties either an MRI_IMPORT or ALM_IMPORT job.

Multi-relational import

Multi-relational import (MRI) is a process for importing exposure data into an EDM from source files uploaded to Amazon Simple Storage Service (Amazon S3).

The MRI process imports account, location, reinsurance exposure data from source files that have been uploaded to a storage bucket. MRI also leverages a distinct import mapping file that defines the relationships between the account, location, and reinsurance exposures and between source file columns and EDM database columns.

The request body specifies the ID of a storage bucket (bucketId), the ID of the EDM (dataSourceName), and the text delimiter used to structure exposure data in the source files. If the storage bucket contains multiple data source files, specify the ID number of each file (e.g. accountsFileId, locationsFileId, reinsuranceFileId) and the import mapping file (mappingFileId) as needed:

     "importType": "MRI",
     "bucketId": 35678,
     "dataSourceName": "myEDMdataSource",
     "accountsFileId": 777777,
     "locationsFileId": 888888,
     "reinsuranceFileId": 999999,
     "mappingFileId": 555555,
     "currency": "USD",
     "locale": "en-GB",
     "delimiter": "TAB",
     "appendLocations": true,
     "portfolioId": 1245,


Data Migration Recipe

The MRI import process combines RMS Risk Modeler APIs and custom processes that leverage Amazon Web Services (AWS). For step-by-step instructions, see Multi-Relational Input.

ALM import

The Aggregate Loss Model (ALM) import workflow enables you to create aggregate portfolios by means of importing exposure data from flat files uploaded to an Amazon S3 storage bucket.

In this scenario, the flat file contains exposure values, aggregated by geographic unit (e.g., CRESTA) or line of business (e.g., Commercial).

The request body specifies the ID of the storage bucket (bucketId), the ID of the EDM (dataSourceName), and the IDs of the portfolios.

    "importType": "ALM",
    "bucketId": 35677,
    "dataSourceName": "myEdmDatasource",
    "portfolioIds": [3]

The LOBs that may be modeled differs depending on the modeled countries licensed. For non-modeled countries, ALM supports only residential (SPER) and commercial lines (COM) of business.


Idemptopotent Operation

This operation supports idempotency by means of idempotency keys. To learn more, see Idempotent Requests.



To perform this operation, a principal must be assigned the appropriate role-based permissions:

UnderwriterTechnical UnderwriterRisk AnalystPortfolio ManagerCat Modeler