2026.09.a

🥥

Highlights

The 2026.09.b release introduces updates to the Import and Risk Data APIs.

• The Import API introduces new operations that support the ALM import workflow. This workflow enables tenants to upload aggregate exposure data to an ALM import folder and import that data into aggregate portfolios in a specific EDM.

Learn More

Moody's RMS Australia Cyclone and Flood HD Model

The Australia Cyclone and Flood HD Model (AUCY) can be used to calculate losses from wind, inland flood, and coastal flood sub-perils independently or in combination. This model is available across standard HD analysis types: Exceedance Probability, Scenario, and Historical. No Footprint files are available in the initial release.

Three simulation sets (PETs) are currently available: a combined default PET, a cyclone-events-only PET, and a non-cyclone-flood-events-only PET. The model also supports custom PETs that can be specified in a model profile.

The Australia Cyclone and Flood Model includes ALM profiles for EP and scenario analyses to facilitate the modeling of aggregate or low-resolution data. Wind and Wind + Flood profiles are available at the CRESTA resolution for commercial, residential, and industrial lines of business.

The model also supports a variety of windstorm settings: pluvial flood risk and flood defenses, including bespoke fluvial defenses, a Cyclone Reinsurance Pool option, which lets you model losses ceded to or not ceded to the pool, and set a post-cyclone time window Loss amplification with a configurable PLA scale factor.

Import API

The Import API introduces new operations and updates to existing API operations that support a new ALM workflow:

This operation enables tenants to upload aggregate exposure data to an ALM import on the tenant's Amazon S3 bucket, and import that data into aggregate portfolios in a specific EDM. Both PROPERTY and WORKERS_COMP aggregate exposure data are supported aggregate exposure data are supported.. The operation also supports editing the uploaded data prior to import.

The Retrieve File Upload Credentials, Retrieve Aggregate Exposure Data, and Update Aggregate Exposure Data operations are new Import API operations that support the ALM workflow. This release includes updates to the Create Import Folder, Create Import Job, and Get Import Job operations. The Import API does not expose an API operation for uploading data to import folders. To upload data to an import folder, use the Amazon S3 APIs.

Create Import Folder

The Create Import Folder operation (POST /platform/import/v1/folders) operation now supports the creation ALM import folders that can be used to import aggregate exposure data into an aggregate exposure.

An import folder is a temporary storage location and a logical path on the tenant’s Amazon S3 bucket. Exposure resource data (e.g. aggregate portfolio data) uploaded to an import folder, can be imported into the Intelligent Risk Platform using Import API operations.

An ALM import folder is a type of import folder that supports the ALM modeling workflow. Once created the folder accepts uploads of CSV or TXT files of aggregate portfolio data, which can imported as aggregate portfolios on the Intelligent Risk Platform.

The folderType body parameter is required in the request:

{
  "folderType": "ALM"
}

If successful, returns 201 Created and a response that includes the folderType and folderId.

{
  "folderType": "ALM",
  "folderId": "43636"
}

The folderId must be specified in the body of Create Import Job request. This operation now supports importing from ALM import folders.

Create Import File

The Create Import File operation (POST /platform/import/v1/folders/{folderId}/files) retrieves pre-signed security credentials that enable the client to upload aggregate PROPERTY or WORKERS_COMP data to the specified ALM import folder on the tenant's Amazon S3 bucket.

The response object returns the presignParms object that returns the pre-signed credentials (accessKeyId, secretAccessKey, sessionToken, path, region) that can be used to upload aggregate portfolio data to the ALM import folder. The Import API does not expose an API operation for uploading data to import folders. To upload data to an import folder, use the Amazon S3 APIs. Once uploaded to the ALM folder, the client can use the Create Import Job operation to import that data as aggregate portfolios into the specified EDM.

The request specifies the required fileName, fileType, and fileInputType parameters in the request body:

{
  "fileName": "ms-re-wc-payroll-q3.csv",
  "fileType": "aggregate-exposure-data",
  "fileInputType": "ALM"
}

The parameters specify information about the file to be uploaded to the ALM import folder including fileName, fileType, and fileInputType:

Note the format of the specified file determines the default text delimiter of the structured content in the file. For CSV files, the default text delimiter the comma; for TXT files, it is the tab character.

If successful, response returns 201 Created HTTP status code and a response that includes a fileId and an uploadDetails object that includes uploadUrl and a set of pre-signed parameters that can be used to upload a file of aggregate portfolio data to the import folder on the tenant's Amazon S3 bucket.

{
  "fileId": "541039",
  "uploadDetails": {
    "uploadUrl": "https://rms-tenants-ppe-eu-west-1.s3.amazonaws.com/4000540/import/alm/43636/541039-ms-re-wc-payroll-q3.csv",
    "presignParams": {
      "accessKeyId": "<base64>",
      "secretAccessKey": "<base64>",
      "sessionToken": "<base64>",
      "path": "<base64>",
      "region": "<base64>"
    }
  }
}

The response returns the fileId and the uploadDetails object that contains information the client can use to upload data to the import folder suing the Amazon S3.

The presignParams object returns the temporary security credentials that enable you to programmatically sign AWS requests. Signing helps to secure requests by verifying the identity of the requester and protecting the data in transit.

Retrieve Aggregate Exposure Data

The Retrieve Aggregate Exposure Data operation (POST /platform/import/v1/folders/{folderId}/ files/{fileId}/retrieve-aggregate-exposures) parses the aggregate exposure data uploaded to the specified ALM folder and returns values as a two-dimensional array whose rows correspond to resolutionValues and whose columns correspond to lobs.

The required insuranceType parameter (PROPERTY or WORKERS_COMP) largely determines the validity of the specified parameter values. The source of the lobs varies depending on the insurance type of the data. For PROPERTY data the lobs are derived from the line-of-business columns in the uploaded data. For WORKERS_COMP the uploaded does not contain a line-of-business column; rather, the lob is derived from the value of the OccScheme and Occ Type columns in the uploaded file.

The request body specifies instructions for reading the raw file (delimiter, dataRowStart, columnMapping), identifies the properties used to interpret or aggregate the uploaded data (countryCode, resolution, dependencyResolution), and, optionally, converts the resolution of aggregate values (resolutionConversionFrom, resolutionConversionTo). The required insuranceType parameter specifies the type of data in uploaded file (PROPERTY or WORKERS_COMP). The insuranceType largely determines the validity of the specified parameter values. For example, the columnMapping parameter, which defines map between the column position in the file and the aggregate portfolio property, is different depending on the insurance type of the data.

Property Requests

For PROPERTY requests, the columnMapping parameter includes the geography properties (State, County) plus one entry for each line of business.

{
  "insuranceType": "PROPERTY",
  "delimiter": "Tab",
  "dataRowStart": 1,
  "countryCode": "US",
  "resolution": "County",
  "dependencyResolution": "State",
  "resolutionConversionFrom": "County",
  "resolutionConversionTo": "County",
  "columnMapping": {
    "State": "1",
    "County": "2",
    "AUTOMOBILE": "3",
    "COMMERCIAL": "4",
    "MOBILE HOME": "5",
    "RESIDENTIAL": "6"
  }
}

Property Responses

The response returns aggregate exposure data for the PROPERTY insurance type:

{
  "insuranceType": "PROPERTY",
  "countryCode": "US",
  "resolution": "State (Tornado only)",
  "dependencyResolution": "State",
  "resolutionConversionFrom": "County",
  "resolutionConversionTo": "State (Tornado only)",
  "columnMapping": {
    "State": "1",
    "County": "2",
    "AUTOMOBILE": "3",
    "COMMERCIAL": "4",
    "MOBILE HOME": "5",
    "RESIDENTIAL": "6"
  },
  "lobs": ["AUTOMOBILE", "COMMERCIAL", "MOBILE HOME", "RESIDENTIAL"],
  "resolutionValues": [
    {
      "code": "AK",
      "name": "Alaska",
      "statecode": "02",
      "id": "US"
    },
    {
      "code": "AL",
      "name": "Alabama",
      "statecode": "01",
      "id": "US"
    }
  ],
  "values": [
    [101.0, 202.0, 303.0, 404.0],
    [505.0, 606.0, 707.0, 808.0]
  ],
  "errorMessages": []
}

Workers Compensation Requests

For WORKERS_COMP, the columnMapping must specify the State, County, Occ Scheme, Occ Type, and Payroll.

The WORKERS_COMP option is available for US-based exposures only.

{
  "insuranceType": "WORKERS_COMP",
  "delimiter": "Tab",
  "dataRowStart": 1,
  "countryCode": "US",
  "resolution": "County",
  "dependencyResolution": "State",
  "resolutionConversionFrom": "County",
  "resolutionConversionTo": "County",
  "columnMapping": {
    "State": "1",
    "County": "2",
    "Occ Scheme": "3",
    "Occ Type": "4",
    "Payroll": "5"
  }
}

The request parameters specify a job that aggregates exposure data:

In WORKERS_COMP request, the columnMapping object specifies State, County, Occ Scheme, Occ Type, Payroll properties, which define a grid based on United States locations:

Workers Compensation Responses

For Workers' Comp, the server maps each row's (Occ Scheme, Occ Type) to one of the fixed wc_cntrylob classes and sums Payroll into that column, so lobs is the fixed class list regardless of the file's columns.

The response returns a dependencyResolution that varies (e.g. County depends on State).

{
  "insuranceType": "WORKERS_COMP",
  "countryCode": "US",
  "resolution": "County",
  "dependencyResolution": "State",
  "resolutionConversionFrom": "County",
  "resolutionConversionTo": "County",
  "columnMapping": {
    "State": "1",
    "County": "2",
    "Occ Scheme": "3",
    "Occ Type": "4",
    "Payroll": "5"
  },
  "lobs": [
    "Construction",
    "General Workers Comp",
    "Hotel/Motel",
    "Light Manufacturing",
    "Medical",
    "Office",
    "Other Manufacturing",
    "Restaurant",
    "Retail Trade",
    "Wholesale Trade"
  ],
  "resolutionValues": [
    {
      "code": "001",
      "name": "BELKNAP COUNTY",
      "id": "NH"
    },
    {
      "code": "003",
      "name": "BRISTOL COUNTY",
      "id": "RI"
    }
  ],
  "values": [
    [0.0, 0.0, 0.0, 0.0, 1000.0, 0.0, 0.0, 0.0, 0.0, 0.0],
    [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 1111.0]
  ],
  "errorMessages": []
}

The response returns:

The resolutionValues property defines an array of resolution objects. Ordered row labels of values; one object per resolution bucket that appears in the file. Only buckets present in the file are returned; no country-wide zero-fill. Each object consists of three values: code, name, and id:

The values property defines an array of arrays. The aggregated exposure grid; one row per resolutionValues entry and one column per lobs entry, including zero columns. Property cells carry monetary exposure; Workers' Comp cells carry payroll summed into the mapped class.

source-column map. For Property, the geography fields plus one column per line of business; for Workers' Comp, State, County, Occ Scheme, Occ Type, and Payroll.

Update Aggregate Exposure Data

The Update Aggregate Exposure Data operation (POST /platform/import/v1/folders/{folderId}/files/ {fileId}/update-aggregate-exposures) edits aggregate exposure data uploaded to an ALM import folder on the tenant's Amazon S3 bucket.

The required folderId and fileId path parameters identify the location of the data on the tenant's Amazon S3 bucket. The request body identifies the "location" of data to update and the value of the updated values. This operation is idempotent per folder.

The request body differs depending the specified insuranceType parameter (PROPERTY or WORKERS_COMP):

For PROPERTY requests, the intersection of elements in the lobs array (i.e. column) and elements in the resolutionValues array (i.e. row) define a grid that identifies the location of the loss data values collected in the values array. The client may add or remove location rows in the grid.

{
  "insuranceType": "PROPERTY",
  "countryCode": "US",
  "resolution": "State (Tornado only)",
  "resolutionConversionFrom": "County",
  "resolutionConversionTo": "State (Tornado only)",
  "lobs": ["AUTOMOBILE", "COMMERCIAL", "MOBILE HOME", "RESIDENTIAL"],
  "resolutionValues": [
    {
      "code": "AK",
      "name": "Alaska",
      "statecode": "02",
      "id": "US"
    },
    {
      "code": "AL",
      "name": "Alabama",
      "statecode": "01",
      "id": "US"
    }
  ],
  "values": [
    [150.0, 202.0, 303.0, 404.0],
    [505.0, 606.0, 0.0, 808.0]
  ]
}

If successful, the operation returns an 200 OK HTTP status and a response body that returns the countryCode, resolution and rowsPersisted of the updated data.

{
  "countryCode": "US",
  "resolution": "County",
  "rowsPersisted": 3
}

Create Import Job

The Create Import Job operation (POST /platform/import/v1/jobs) now supports the creation of ALM import jobs, which imports aggregate exposure data uploaded to an ALM folder as aggregate portfolios.

An aggregate portfolio is a collection of exposure values aggregated by geographic unit (e.g. CRESTA) or by line of business (e.g. Commercial). An aggregate portfolio is defined by a cedant peril, and other attributes.

The ALM import type creates an ALM_IMPORT import jobs that imports aggregate portfolio data (i.e. aggregate exposures) from the specified ALM import folder. The required importType and resourceUri parameters identify the job type and the EDM into which the aggregate portfolios are imported.

{
  "importType": "ALM",
  "resourceUri": "/platform/riskdata/v1/exposures/{id}",
  "settings": {
    "folderId": 43636,
    "portfolioIds": [123, 235]
  }
}

If successful, returns 201 Created HTTP status and initiates an ALM_IMPORT job. The response returns the job URL in the Location header. The job imports the specified aggregate portfolios writes and these exposure resources to the specified EDM (resourceUri) as aggregate portfolios.

Legacy API

Search Batch Templates

The Search Batch Template operation (GET /analysis-settings/batchtemplates?entitlement=EIQ, TIQ) returns a list of batch templates.

A batch template is a collection of analysis settings that are used to generate report views in UnderwriteIQ. Batch templates may specify model profile settings, event rate sets, output profile versions, analysis settings including DLM configurations and analysis currency, and report settings.

This operation supports filtering results by multiple entitlements. The entitlement query parameter now accepts a comma-separated list of entitlement values.

curl --request GET \
     --url 'https://api-euw1.rms.com/analysis-settings/batchtemplates?entitlement=EIQ%2C%20TIQ' \
     --header 'accept: application/json'\

Risk Data API

The Edit Aggregate Portfolio Data operation (PUT /platform/riskdata/v1/exposures/{exposureId}/ aggregateportfolios/{id}/aggregate-exposures-lists) updates aggregate portfolio data uploaded to the ALM import folder.

This operation enables the client to review and edit the data uploaded to an ALM folder prior to importing that data as aggregate portfolios.

The required countryCode and resolution body parameters identify the "slice" of data to be updated. The operation specifies an array of values that adds or replaces an existing set of values in the uploaded aggregate profile data. Each index in the values array corresponds to an element in the resolutionValues array (i.e. the row) and an element in the lobs array (i.e. the column). A positive number saves that cell and 0 clears it.

If the file contains PROPERTY data, the request supports updates to the resolution values for the specified countryCode and resolution.

{
  "countryCode": "US",
  "resolution": "State",
  "lobs": ["AUTOMOBILE"],
  "resolutionValues": [
    { "code": "06", "name": "California" }
  ],
  "values": [
    [ 125000000.0 ]
  ]
}`

The significance of the elements in values array differ depending on the industry type of the uploaded aggregate portfolio data (PROPERTY or WORKERS_COMP). The lobs and resolutionValues parameters that identify the column and row headers of the uploaded data values are different in PROPERTY or WORKERS_COMP data.

The lobs parameter defines an array of column headers. For PROPERTY data, these values correspond to the line of businesses columns in the file. For WORKERS_COMP, the request accepts one of ten values: Construction, General Workers Comp, Hotel/Motel, Light Manufacturing, Medical, Office, Other Manufacturing, Restaurant, Retail Trade, Wholesale Trade

The resolutionValues parameter defines an array of objects, which specify geographic row labels for values. WORKERS_COMP the allowed values are State, County, Postal Code. It's a single value per request, and it labels the resolutionValues rows.

If the file contains WORKERS_COMP data, the request supports updates to the resolution values for the specified countryCode and resolution.

{
  "countryCode": "US",
  "resolution": "State",
  "lobs": ["Office", "Manufacturing"],
  "resolutionValues": [
    {
      "code": "06",
      "name": "California"
    },
    {
      "code": "36",
      "name": "New York"
    }
  ],
  "values": [
    [125000000.0, 47000000.0],
    [98000000.0, 33000000.0]
  ]
}

As an API consumer editing a WORKERS_COMP aggregate portfolio, who could already read its WC grid (US, State/County/Postal Code resolutions, wc_cntrylob LOB columns), they are also able to save edits through the same endpoint and DTO with no WC-specific request shape.

As an API consumer, who submits a slice whose values dimensions don't match resolutionValues × lobs, or references an unknown resolution/LOB/code, or sends a non-US countryCode for a WC portfolio, they receive 400 with {code, message, logId, details[]} identifying the failing field, and no values are persisted.

Create Location

The Create Location operation (POST /platform/riskdata/v1/exposures/{exposureId}/locations) now supports the definition of secondary modifiers as objects.

The locationWsDetail, locationFlDetail, locationEqDetail, locationFrDetail, locationTrDetail parameters are now defined as object consisting of three string properties: id, code, and name.

{
  "property": {
    "locationNumber": "LOC-10001",
    "yearBuilt": "2020",
    "inceptDate": "2026-01-01T00:00:00.000Z",
    "expireDate": "2027-01-01T00:00:00.000Z"
  },
  "locationWsDetail": {
    "wsRemDesign": {
      "id": 2,
      "code": "2",
      "name": "Aluminium frame"
    },
    "wsRemSpec": {
      "id": 0,
      "code": "0",
      "name": "Unknown"
    },
    "wsRemMitigation": {
      "id": 1,
      "code": "1",
      "name": "Standard"
    },
    "wsRemSite": {
      "id": 0,
      "code": "0",
      "name": "Unknown"
    }
  },
  "locationFlDetail": {
    "flRemDesign": {
      "id": 3,
      "code": "3",
      "name": "Reinforced"
    },
    "flRemSpec": {
      "id": 0,
      "code": "0",
      "name": "Unknown"
    },
    "flRemMitigation": {
      "id": 0,
      "code": "0",
      "name": "Unknown"
    },
    "flRemSite": {
      "id": 0,
      "code": "0",
      "name": "Unknown"
    },
    "ifmEquipLocation": {
      "id": 1,
      "code": "1",
      "name": "Above ground floor"
    },
    "ifmSiteHazard": {
      "id": 0,
      "code": "0",
      "name": "Unknown"
    },
    "depreciationAge": {
      "id": 1,
      "code": "1",
      "name": "0-5 years"
    }
  },
  "locationEqDetail": {
    "eqRemDesign": {
      "id": 0,
      "code": "0",
      "name": "Unknown"
    },
    "eqRemSpec": {
      "id": 0,
      "code": "0",
      "name": "Unknown"
    },
    "eqRemMitigation": {
      "id": 0,
      "code": "0",
      "name": "Unknown"
    },
    "eqRemSite": {
      "id": 0,
      "code": "0",
      "name": "Unknown"
    }
  },
  "locationFrDetail": {
    "frRemDesign": {
      "id": 0,
      "code": "0",
      "name": "Unknown"
    },
    "frRemSpec": {
      "id": 0,
      "code": "0",
      "name": "Unknown"
    },
    "frRemMitigation": {
      "id": 0,
      "code": "0",
      "name": "Unknown"
    },
    "frRemSite": {
      "id": 0,
      "code": "0",
      "name": "Unknown"
    }
  },
  "locationTrDetail": {
    "trRemDesign": {
      "id": 0,
      "code": "0",
      "name": "Unknown"
    },
    "trRemSpec": {
      "id": 0,
      "code": "0",
      "name": "Unknown"
    },
    "trRemMitigation": {
      "id": 0,
      "code": "0",
      "name": "Unknown"
    },
    "trRemSite": {
      "id": 0,
      "code": "0",
      "name": "Unknown"
    }
  }
}

Update Location

The Update Location operation (PUT /platform/riskdata/v1/exposures/{exposureId}/locations/{locationId}) now supports the definition of secondary modifiers as objects.

The locationWsDetail, locationFlDetail, locationEqDetail, locationFrDetail, locationTrDetail parameters are now defined as object consisting of three string properties: id, code, and name.

Get EP Metrics

The Get EP Metrics operation (GET /platform/riskdata/v1/analyses/{analysisId}/ep) now returns treaty and policy level metrics for HD results.

In previous releases, the Risk Data API returned policy- or treaty-level metrics for DLM analysis only.

Get EP Statistics

The Get EP Statistics operation (GET /platform/riskdata/v1/analyses/{analysisId}/stats) now returns treaty and policy level metrics for HD results,

In previous releases, the Risk Data API returned policy- or treaty-level metrics for DLM analysis only.