Moody’s strongly recommends that Risk Modeler and UnderwriteIQ tenants use the Platform APIs instead of the Risk Modeler APIs for all future projects.

Changelog
Back to All

2026.01.c

about 1 month ago

🥥

Highlights

The 2026.01.c release introduces updates to the ExportV2 collection.

  • The Exports V2 collection now supports exporting exposure and analysis result data using different versions of the EDM and RDM database schemas.
  • The Exports V2 collection now supports exporting statistics and metrics segmented at specific output levels (granularities).
  • The Reports V1 colection now returns accumulation by treaty reports.
    Learn More

Reports

The Get Report operation (GET /riskmodeler/v1/reports/{id}) now returns the ACCUMULATIONS_BY_TREATY report.

A report view is a collection of reports that return exposure-specific metrics and statistics. The report view is generated automatically whenever an UnderwriteIQ client creates exposures in batch using the Exposure Bulk Edit operation.

This operation now returns the ACCUMULATIONS_BY_TREATY report.

{
  "analysisIds": [64605],
  "lossDetails": [
    {
      "lossType": "EP",
      "outputLevels": ["Admin1"],
      "perspectives": ["GU"]
    }
  ],
  "exportType": "RDM",
  "type": "ResultsExportInputV2",
  "exportFormat": "CSV",
  "nonWeightedPlt": true,
  "additionalOutputs": []
}

This operation requires the RI-UNDERWRITEIQ entitlement.

SQL Server Updates

Microsoft plans to end extended support of SQL Server 2016 on July 14, 2026. As a result, the Intelligent Risk Platform™ will end support for SQL Server 2016 in June 2026. This change may affect Export API jobs that export data to EDM or RDM databases.

Export Data Module

The Export Data Module to File operation (POST /riskmodeler/v2/exports) now supports exporting statistics and metrics segmented at specific output levels, i.e. granularities.

The ResultsExportInputV2 export type supports exporting analysis result data (loss tables, EP metrics, and statistics) to a flat file in CSV or PARQUET format. This operation now supports exporting result data grouped by output level.

An output level is a category that identifies the granularity of analysis result data, i.e. the resolution level used to aggregate computed losses. This operation now supports exporting loss details at the following output levels: Account, Admin1 by Cedant, Admin1 by LOB by Cedant, Admin1 by LOB, Admin1, Admin2 by Cedant, Admin2 by LOB by Cedant, Admin2 by LOB, Admin2, Cedant, City by LOB, City, Country by Cedant, Country by LOB by Cedant, Country by LOB, Country, Cresta by Cedant, Cresta by LOB by Cedant, Cresta by LOB, Cresta, District/Admin3 by LOB, District/Admin3, Facultative, LOB, Location, Other GeoID by LOB, Other GeoID, Policy, Portfolio, PostalCode by Cedant, PostalCode by LOB by Cedant, PostalCode by LOB, PostalCode, Treaty

The outputlevels parameter specifies a list of output levels that specify the granularity of exported losses :

{
  "analysisIds": ["36976"],
  "exportFormat": "CSV",
  "exportType": "RDM",
  "lossDetails": [
    {
      "lossType": "EP",
      "outputLevels": [
        "Admin1",
        "Admin1 by Cedant",
        "Admin1 by LOB",
        "Admin1 by LOB by Cedant",
        "Admin2",
        "Admin2 by Cedant",
        "Admin2 by LOB",
        "Admin2 by LOB by Cedant",
        "Account",
        "Cedant",
        "City",
        "City by LOB",
        "Country",
        "Country by Cedant",
        "Country by LOB",
        "Country by LOB by Cedant",
        "Cresta",
        "Cresta by Cedant",
        "Cresta by LOB",
        "Cresta by LOB by Cedant",
        "District",
        "District by LOB",
        "LOB",
        "Location",
        "Other GeoID",
        "Other GeoID by LOB",
        "Policy",
        "Portfolio",
        "PostalCode",
        "PostalCode by Cedant",
        "PostalCode by LOB",
        "PostalCode by LOB by Cedant",
        "Treaty",
        "Facultative"
      ],
      "perspectives": ["GU"]
    }
  ],
  "type": "ResultsExportInputV2",
  "nonWeightedPlt": false
}

Export Data Module

The Export Data Module to File operation (POST /riskmodeler/v2/exports) now supports exporting exposure and analysis result data in differnt versions of the Intelligent Risk Platform database schemas.

This operation now accepts a schemaVersion parameter that specifies the version of the EDM or RDM database schema of the exported exposure or result data.

The schemaVersion parameter can be specified in the body of Export Data Module requests with the EDM, RDM, and LOCATION_RESULTS export types. The parameter accepts the following values: v18, v21, v22, v23, v24, v25:

{
  "type": "ExposureExportInput",
  "exportType": "EDM",
  "exportFormat": "BAK",
  "sourceDatasource": "_20240719_EDM2EDM01_LMAq",
  "destinationDatasource": "Destination_EDM",
  "exposureType": "ACCOUNT",
  "exposureIds": [1391],
  "sqlServerVersion": "2019",
  "download": true,
  "createnew": true,
  "exportOptions": {
    "exportAccounts": true,
    "exportLocations": true,
    "exportPolicies": true,
    "exportTreaties": true,
    "exportReinsuranceInfo": true,
    "exportPerilDetailsInfo": true
  },
  "sqlVersion": "2016",
  "schemaVersion": "v18"
}

The RDM export type supports exporting analysis result data to both new and existing hosted RDM database on Data Bridge.

  • Result data exported to new RDM databases can be exported in different database schema versions. The request accepts schemaVersion parameter values of v18, v21, v22, v23, v24, v25.
  • Result data exported to existing RDM database can only be exported to the current version of the RDM database schema (i.e. v25). The schemaVersion parameter specified in the request is ignored.

Background

All Intelligent Risk Platform exposure and analysis result data is defined according to a database schema that specifies the table names, fields, data types of exposure and result data and the relationships between these entities. The EDM database schema and RDM database schema define the structure of data in on-premise EDM and RDM databases. These same schemas define the structure of data managed on the Intelligent Risk Platform.

Moody's Insurance Solutions periodically releases new versions of these database schemas. As new features are added to the Intelligent Risk Platform, new versions of the EDM database schema and RDM schema are released that support the required tables, fields, and data types.

This feature supports the following use cases:

  • Tenants can share data with teams and partners on older environments without the need to update primary EDMs or RDMs.
  • Tenants can maintain stable integrations by exporting to data versions that are required by downstream tools.
  • Tenants can track the data version of exported data, which supports auditing and troubleshooting.