May 2025
Highlights
The May release introduces updates to the Admin Data, Import, and Risk Data APIs.
- The Risk Data API offers enhanced filtering and sorting of EDMs.
- Moody's Insurance Solutions has released version 2.0 of the Moody's RMS™ North America Wildfire HD Model that features an enhanced US region of the model and expands coverage to include the Hawaiian Islands.
- Moody's Insurance Solutions has released version 25.0 of the geocoding engine. Version 25 includes significant geocoding enhancements that expand global coverage and increase precision.The geocoding and hazard data versions available in the Platform APIs now include 25.0.
Admin Data API
Search Archives
The Search Archives operation (/platform/admindata/v1/archives
) now supports filtering and sorting of archives by databaseType
and owner
.
Property | Type | Comparision | List | Logical |
---|---|---|---|---|
databaseType | String | = , != , LIKE , NOT LIKE | IN , NOT IN | AND , OR |
owner | String | = , != , LIKE , NOT LIKE | IN , NOT IN | AND , OR |
Data can be sorted by databaseType
or owner
values in ascending or descending order.
Batch API
The Create Batch Job operation (POST
/platform/batch/v1/jobs/
) initiates a batch job that manages the processing of multiple operations in a workflow.
All operations are defined in the body of the request package. These operations are known as tasks within the workflow. Each task is defined as a JSON object in the request package and processed as a separate job by the workflow engine.
This operation now supports the inclusion of CONVERT_EVENT_RATE_LOSS
jobs in user-defined workflows. The Convert Event Rates and Losses operation can be specified as a task in a batch job:
{
"name": "BatchEventLossRequest",
"settings": {
"combineBatchEditAndGeohazard": false,
"disableUnderwriterReports": false
},
"tasks": [
{
"label": "convertEventLoss",
"operationUri": "/platform/riskdata/v1/analyses/2863639/convert-event-rate-loss",
"requestBody": {
"analysisName": "",
"eventRateSchemeIds": [163],
"eventLossAdjustmentSchemeIds": [2]
},
"dependsOn": [],
"continueOnFailure": false,
"skipMissingVariables": false
}
]
}
Risk Data API
Search Analysis Results and Get Analysis Result
The Search Analysis Results operation (GET
/platform/riskdata/v1/analyses
) and Get Analysis Result operation (GET
/platform/riskdata/v1/analyses/{analysisId}
) now return the exposureResourceName
property, which identifies the name of the EDM containing the analysis result.
[
{
"analysisId": 4778860,
"analysisName": "rms_rdmfileservice_testdata_edm: PORTFOLIO: Port_All_Acct_De_SIM",
"createDate": "2025-05-19T13:40:47",
"description": "RM2.0_API_BEFL_V18_V2",
"sourceRdmName": "",
"analysisRegroupType": "Not Required",
"exposureResourceType": "PORTFOLIO",
"engineVersion": "RL18",
"groupType": "ANLS",
"exposureResourceId": 2,
"exposureName": "rms_rdmfileservice_testdata_edm",
"jobId": 35073627,
"jobGuid": "23cf95bd-bc48-436d-8def-bffde67d5e68",
"isGroup": false,
"modelProfile": {
"id": 567,
"code": "",
"name": "RM2.0_API_BEFL_V18_V2"
},
"outputProfile": {
"id": 21,
"code": "",
"name": "OP_Detailed_Universal"
},
"engineType": "DLM",
"analysisStatus": "Analyzed",
"analysisType": "Exceedance Probability",
"peril": "Flood",
"subPeril": "Off + On Plain Flood",
"region": "Belgium",
"lossAmplification": "None",
"analysisMode": "Distributed",
"insuranceType": "Property",
"vulnerabilityCurve": "Vulnerability - Default",
"username": "[email protected]",
"eventRateSchemeNames": [
{
"id": 0,
"code": "0",
"name": "RMS Stochastic Event Rates"
}
],
"currency": {
"currencyName": "US Dollar",
"currencyCode": "USD",
"currencyScheme": "RMS",
"currencyAsOfDate": "2020-03-01T00:00:00Z",
"currencyVintage": "RL18"
},
"engineSubType": "Simulated Losses",
"analysisFramework": "PLT",
"simulationSetId": 0,
"simulationPeriods": 0,
"exposureSetGuid": "3a0a1a4a-259f-48cc-9ba9-bf773563064b",
"uri": "/platform/riskdata/v1/analyses/4778860",
"exposureResourceName": "Port_All_Acct_Detail",
"variationId": 8481,
"eventInfo": {
"eventDateBehavior": "",
"eventDate": ""
},
"entitlement": "",
"securableUri": "/platform/riskdata/v1/exposureSet/2689424",
"analysisUuid": "4e3cdf59-57ea-48a0-b2c0-c8a1a44d94eb",
"appAnalysisId": 122345,
"engineId": 100,
"statusId": 102,
"typeId": 102,
"perilCode": "FL",
"subPerilId": 3145728,
"regionCode": "BE",
"lossAmplificationId": 0,
"modeId": 2,
"insuranceTypeId": 1,
"vulnerabilityCurveId": 0,
"engineSubTypeCode": "SL",
"isMultiEvent": false,
"engineSubTypeId": 2,
"securableId": 2689424,
"securableType": "exposureSet",
"tagIds": [
1,
2,
3
]
},
...
]
Simulate PLT Analysis
The Simulate PLT Analysis operation (POST
/platform/riskdata/v1/analyses/{analysisId}/simulate-losses
) now accepts the optional regionalPerilSettings
object that specifies multiple simulation sets for use in calculating PLT analyses based on the specified ELT base analysis .
{
"regionPerilSettings": [
{
"eventRateSchemeId": 142,
"simulationSetId": 62,
"simulationPeriods": 800000,
"modelRegionCode": "NAWS"
},
{
"eventRateSchemeId": 184,
"simulationSetId": 104,
"simulationPeriods": 800000,
"modelRegionCode": "AUEQ"
}
]
}
The regionalPerilSettings
array specifies a list of region-specific simulation set settings. Each object defines a simulationSetId
, simuationPeriod
and modelRegionCode
. Each object representing simulation details for region peril model. The regionPerilSettings
is required for ELT analysis with more than one region peril, e.g. grouped analysis results, which typically consist of multiple region perils.
Formerly, this operation required that the client specify a simulationSetId
and simulationPeriods
in the request object. These parameters are now optional. If the regionalPeriodSettings
parameter is specified, the simulationSetId
, simulationSetName
, andsimulationPeriods
paramerers must be omitted.
Exposures
The Get EDM operation (GET
/platform/riskdata/v1/exposures/{exposureId}
) and Search EDMs operation (GET
/platform/riskdata/v1/exposures
) now returns metadata about the EDM including createdBy
, createdAt
, updatedAt
and updatedBy
properties.
The Search EDMs operation supports response filtering based the value of a subset of properties. Depending on the property, you may use a combination of comparison operators, list operators, and logical operators.
EDMs returned by this operator can be filtered by createdAt
, createdBy
, updatedAt
, and updatedBy
property values:
Property | Data Type | Comparison | List | Logical |
---|---|---|---|---|
createdAt | date-time | = , < , > , >= , <= | AND , OR | |
createdBy | string | = , != , LIKE , NOT LIKE | IN , NOT IN | AND , OR |
updatedAt | date-time | = , < , > , >= , <= | AND , OR | |
updatedBy | string | = , != , LIKE , NOT LIKE | IN , NOT IN | AND , OR |
This operation supports sorting response data by createdBy
, createdAt
, updatedBy
, updatedAt
in ascending or descending order.
Locations
Moody's Insurance Solutions has released version 2.0 of the Moody's RMS™ North America Wildfire HD Model that features an enhanced US region of the model and expands coverage to include the Hawaiian Islands.
Several Risk Modeler API operations now support several new peril objects: wildFireCommunityPreparedness
,wildFireCommunityMatchFlag
, wildFireMechanicalTreatment
, wildFireAccessibility
.
The updated frPerformance
object is specified or returned in the following operations:
- Create Location (
POST
/riskmodeler/v1/locations
) - Get Location (
GET
/riskmodeler/v1/locations/{locationid}
) - Update Location (
PUT
/riskmodeler/v1/locations/{locationid}
) - Create FR Peril (
POST
/riskmodeler/v1/locations/{locationid}/locationfrdetail
) - Update FR Peril (
PUT
/riskmodeler/v1/locations/{locationId}/locationfrdetail/{getlocationfrdetail}
) - Get FR Peril (
GET
/riskmodeler/v1/locations/{locationId}/locationfrdetail/{getlocationfrdetail}
) - Process User-Defined Workflow (
POST
/riskmodeler/v1/workflows
) - Manage Exposures in Batch (
POST
/riskmodeler/v3/exposurebatches
)
For example, the Create FR Peril operation now accepts a request body that includes these objects:
{
"id": 0,
"siteLimit": 100,
"siteDeduct": 0,
"combinedLimit": 0,
"combinedDeduct": 0,
"yearUpgrade": "9999",
"startDate": "9999-12-31T00:00:00.000Z",
"completionDate": "9999-12-31T00:00:00.000Z",
"percentComplete": 100,
"fireDepartmentRatingModifier": {
"id": 0,
"code": "",
"name": ""
},
"fireDepartmentRating": {
"id": 0,
"code": "",
"name": ""
},
"sprinklerSystem": {
"id": 0,
"code": "",
"name": ""
},
"remoteAlarm": {
"id": 0,
"code": "",
"name": ""
},
"frPackage": {
"id": 0,
"code": "",
"name": ""
},
"frProtect": {
"id": 0,
"code": "",
"name": ""
},
"frSalvage": {
"id": 0,
"code": "",
"name": ""
},
"frSpecieStorage": {
"id": 0,
"code": "",
"name": ""
},
"wildFireMatch": {
"id": 0,
"code": "",
"name": ""
},
"nonRankingCombinedDeduct": 0,
"nonRankingSiteDeductible": 0,
"isValid": false,
"wildFireCommunityPreparedness": {
"id": 0,
"code": "",
"name": ""
},
"wildfireCommunityMatch": {
"id": 0,
"code": "",
"name": ""
},
"wildFireMechanicalTreatment": {
"id": 0,
"code": "",
"name": ""
},
"ifmStructCondition": {
"id": 0,
"code": "",
"name": ""
},
"ifmEquipLocation": {
"id": 0,
"code": "",
"name": ""
},
"ifmSiteHazard": {
"id": 0,
"code": "",
"name": ""
}
}
Geocoding Data Updates
Version 25 includes significant geocoding enhancements that expand global coverage and increase precision.
The geocoding and hazard data versions available in the Platform APIs now include 25.0.
More information about these geocoding software changes is available in the following documents, which will be available with the Version 25 release:
EDM and RDM Upload and Download
Version 25 databases are added to the versions supported for upload. The upload process supports Moody's EDM databases in RiskLink/RiskBrowser versions 13, 15, 16, 17, 18, 21, 22, 23, 24, and 25. These can be created using SQL Server versions 2014 SP3, 2016 SP3, and 2019. During upload, the EDM schema is updated to RiskLink version 25 and to SQL Server version 2019.
Beginning with this update, RDMs are exported in Moody's Version 25 format only. For situations when you want to share the database with someone who is not on Version 25 or use it in an environment that is not upgraded to Version 25, Moody's provides a script on Support Center that downgrades the RDM to the version they need. Before running an upgrade/downgrade script on a database downloaded from an Intelligent Risk Platform™ application, run the RDM_transfer_from_RM.sql
script on the database. The script is provided in DBSetup and with the upgrade/downgrade scripts. Download the script from the Support Center.