What's Coming in July 2025
Highlights
The July release introduces updates to the Exchange Data API, Legacy API, Variation API, and Moody's Insurance Solutions Developer Portal access controls.
Moody's publishes preliminary information to inform stakeholders ahead of the targeted Intelligent Risk Platform update. Note that these described features are not guaranteed for the next update or any subsequent updates and may be changed without notice. The definitive list of features will be provided in the Changelogs at the time of the official release.
Developer Portal Access Controls
Beginning with the July 2025 release, the Moody's Insurance Solutions Developer Portal will require that all visitors log in using an Intelligent Risk Platform user account and credentials.
Every Intelligent Risk Platform developer that requires access to the developer portal will need their own user account and login credentials. Licensed users can log into the Moody's Insurance Solutions Developer Portal using their email address and password.
Contact your Intelligent Risk Platform client success manager for more information.
Schedule
- June 25, 2025: Tenant administrators can begin assigning the IRP Developer role to user groups.
- July 9, 2025: Visitors must log in using their Moody's Intelligent Risk Platform credentials. Unlicensed visitors cannot access or view Intelligent Risk Platform API documentation after this date.
For tenant administrators
Intelligent Risk Platform tenant administrators are encouraged to create new user accounts and user groups as soon as possible.
Developers that require access to Moody's Insurance Solutions Developer Portal should be added to a group assigned the IRP Developer role. The IRP Developer role is a special role that enables users to access the Moody's Insurance Solutions Developer Portal. Any user that is a member of group assigned this role can access the Moody's Insurance Solutions Developer Portal. This role confers no other access rights, permissions, or entitlements to group members.
Tenant administrators can begin assigning the IRP Developer role to groups on June 25 2025.
- Create a user account for each Intelligent Risk Platform developer.
- Create a distinct user group for these Intelligent Risk Platform developers.
- Assign the IRP Developer role to the group.
- Assign the Intelligent Risk Platform developer user accounts to the group.
For detailed instructions, see User Administration in Help Center.
Once assigned a user account, developers can log into the Moody's Insurance Solutions Developer Portal using their email address and password.
For developers
Beginning July 9, 2025, visitors to Moody's Insurance Solutions Developer Portal will be required to log in to view Intelligent Risk Platform API documentation and developer resources.
- Contact your client success manager and request an Intelligent Risk Platform user account.
Your tenant administrator will provide with a user name (usually company email address) and instructions for setting up a password. - Set up your Intelligent Risk Platform account.
- Click the Log In button at the top Moody's Insurance Solutions Developer Portal.
- Log in to the Insurance Solutions Developer Portal using your Intelligent Risk Platform email and password
Exchange Data API
Create Share Request
The Create Share Request operation ( POST
/platform/exchangedata/v1/sharekeys/{shareKey} /sharerequests
) now creates share requests that share multiple exposures or analysis results.
A share request is a request to make exposure or analysis data available to a recipient. Every share request is identified by a share key, which enables a specific recipient to access the data.
This operation now accepts a resourceMap
parameter that maps shared exposures and analyses. This mapping enables the client application to identify analyses that are based upon particular exposures.
{
"shareRequestName": "group share",
"recipientShareKey": "HS6FOPYSRP",
"recipientEmail": "",
"comment": "",
"resources": [
{
"resourceType": "EXPOSURE",
"resourceUris": [
"/platform/riskdata/v1/exposures/13694811",
"/platform/riskdata/v1/exposures/13693834",
"/platform/riskdata/v1/exposures/55555" //This exposure does not have any Analysis associated with it
]
},
{
"resourceType": "ANALYSIS",
"resourceUris": [
"/platform/riskdata/v1/analyses/16931626",
"/platform/riskdata/v1/analyses/16932326",
"/platform/riskdata/v1/analyses/12345",
"/platform/riskdata/v1/analyses/1111" //Analysis 1111 is not associated with any Exposure
],
"resourceMap": [
{
"exposureId": 13694811,
"analysisIds": [
16931626, //Associated with exposureId = 13694811
16932326
]
},
{
"exposureId": 13693834,
"analysisIds": [
12345 //Associated with exposureId = 13693834
]
}
]
}
]
}
The resourceMap
defines an array of objects that map analyses (specified in the ANALYSIS
resource type object) to exposures (specified in the EXPOSURES
resource type object).
-->
Get Share Request
The Get Share Request operation (GET
/platform/exchangedata/v1/sharekeys/{shareKey}/sharerequests /sharerequest/{id}
) now returns information about mappings between shared exposures and analyses.
The resourceType
object returns additional information about the share request:
EXPOSURE
resource type objects now return theedmVersion in each
resourceProperties` object.ANALYSIS
resource type objects now return theanalysisEngineType
andanalysisFramework
properties (e.g.ELT
,PLT
) in eachresourceProperties
object.
[
{
"shareRequestId": 3468,
"shareRequestName": "group share",
"shareKey": "LDG07QLRCR",
"shareKeyName": "sharekey 2024",
"recipientShareKey": "HS6FOPYSRP",
"recipientShareKeyName": "Celtic Re",
"status": "Accepted",
"createdBy": "[email protected]",
"recipientEmail": "",
"updatedBy": "[email protected]",
"createdAt": "2025-03-20T14:50:24.639246Z",
"updatedAt": "2025-03-20T14:50:44.305511Z",
"comment": "",
"shareRequestType": "OUTBOUND",
"isPackage": true,
"resources": [
{
"resourceType": "ANALYSIS",
"resourceSize": "0 bytes",
"resourceUris": [
"/platform/riskdata/v1/analyses/16932326",
"/platform/riskdata/v1/analyses/16931626"
],
"resourceProperties": [
{
"resourceUri": "/platform/riskdata/v1/analyses/16932326",
"resourceName": "Ami_180_1",
"resourceSize": "0 bytes",
"exposureName": "dabase67",
"analysisFramework": "ELT",
"analysisType": "EP",
"analysisEngineType": "DLM",
"exposureId": 13694811
},
{
"resourceUri": "/platform/riskdata/v1/analyses/16931626",
"resourceName": "RMS_RL18_Ref_TestData_EDM_4",
"resourceSize": "0 bytes",
"exposureName": "dabase67",
"analysisFramework": "PLT",
"analysisType": "EP",
"analysisEngineType": "HD",
"exposureId": 13694811
}
]
},
{
"resourceType": "EXPOSURE",
"resourceSize": "156 MB",
"resourceUris": [
"/platform/riskdata/v1/exposures/13694811",
"/platform/riskdata/v1/exposures/13693834"
],
"resourceProperties": [
{
"resourceUri": "/platform/riskdata/v1/exposures/13694811",
"resourceName": "dabase67",
"resourceSize": "78 MB",
"edmVersion": "24"
},
{
"resourceUri": "/platform/riskdata/v1/exposures/13693834",
"resourceName": "database3",
"resourceSize": "78 MB",
"edmVersion": "24"
}
]
}
]
},
Review Share Request
The Review Share Request operation (POST
/platform/exchangedata/v1/sharekeys/{shareKey} /sharerequests/{shareRequestId}/review
)
enables a Data Exchange Admin to accept or reject both inbound and outbound share requests.
The operation now returns a resourceMap
array that includes resource type-specific information:
- If the resource type is
EXPOSURE
, each object returns theexposureId
,resourceName
, andsecurableId
. - If the resource type is
ANALYSIS
, each object may return a mapping between anexposureId
and an array ofanalysisIds
or a mapping between asecurableId
an array ofanalysisIds
.
{
"reviewType": "INBOUND_ACCEPT",
"settings": {
"comment": "accepting",
"serverId": 5308,
"securableId": 771011,
"resources": [
{
"resourceType": "EXPOSURE",
"resourceMap": [
{
"exposureId": 21321312,
"resourceName": "banana",
"securableId": 345
},
{
"exposureId": 21321313,
"resourceName": "co6okie34",
"securableId": 234
},
{
"exposureId": 21321314,
"resourceName": "blueberry",
"securableId": 123
}
]
},
{
"resourceType": "ANALYSIS",
"resourceMap": [
{
"exposureId": 13694811,
"analysisIds": [16931626, 16932326]
},
{
"analysisIds": [16931626, 16932326],
"securableId": 771034
},
{
"analysisIds": [23121, 1691231232326],
"exposureId": 1234
}
]
}
]
}
}
Legacy API
The Create Output Profile operation (POST
/analysis-settings/outputprofiles
) enables the client to create an output profile.
An output profile is a configuration that identifies the loss tables, EP metrics, and statistics output to an analysis result. This output profile specifies the granularity (resolution) of the results returned in the analysis and the financial perspectives used to calculate modeled losses.
This operation now supports improved support for the modeling locatons and policies covered by facultative cessions using HD models. The metricsRequests
parameter now enables the client to specify Facultative
as the resolution (geographic granularity) of computed statistics (STATS
), EP curves (EP
), and loss tables (LOSS_TABLES
).
The metricRequests
array specifies a list of objects that determine the metrics returned in an analysis. Each object maps a metric type (e.g. EP
), a financial perspective (e.g. FA
), and granularity (e.g. Facultative
) to define metric request settings. Thegranularity
value specifies the resolution of the metric data.
The granularity
and perspective
of each metric can be specified to support the modeling of facultative cessions using HD models.
{
"excludeDefaultMetrics": true,
"metricRequests": [
{
"metricType": "STATS",
"includeIntermediateSums": false,
"granularity": ["Facultative"],
"perspective": "FA"
},
{
"metricType": "EP",
"includeIntermediateSums": false,
"granularity": ["Facultative"],
"perspective": "FA"
},
{
"metricType": "LOSS_TABLES",
"includeIntermediateSums": false,
"granularity": ["Facultative"],
"perspective": "FA"
}
],
"name": "My Fac Cession Output Profile"
}
The Facultative
granularity is applicable only to analysis modeled using HD models. If the output profile is used with an DLM model, the granularity value is ignored.
Formerly, if the model profile specified FA
(facultative) as the value of the perspective
parameter, the analysis would return AAL (UNCERTAINTY
), EP curves (EP
), and PLT (LOSS_TABLES
) by default when analyzing portfolios using HD models, which could cause the analysis to crash if the portfolio included hundreds of thousands of facultative cessions. This change provides cat modelers with greater control when modeling these porfolios.
Variation API
The Create Variation Job operation now accepts an optional riskViews
parameter, which determines whether risk-by-peril data is provided for the portfolio variations created in the request.
An exposure variation is a snapshot of an existing exposure (e.g. a portfolio variation of portfolio). Exposure variations enable tenants to ensure that reports and data exports accurately reflect the actual state of an exposure. Distinct exposure variations may be distinguished by distinct treaties or currency schemes.
This new riskViews
parameter accepts a Boolean value. If true
, the resulting portolio variation can return risk-by-peril views, which is akin to a flattened denormalized risk view that returns total insurable values (TIVs) values pre-computed by peril for quick analytics and reporting.
Entitlements
To run this operation the client must belong to a tenant that has been assigned the
RI-EXPOSUREIQ
entitlement.