🥥

Highlights

The 2026.06.c release adds enhancements to the Admin Data API, Batch API, and Exchange Data API.

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.

Learn More

Login Requirements

Beginning June 2026, the Moody's Insurance Solutions Developer Portal will require that all visitors log in to access Intelligent Risk Platform API documentation and developer resources.

Every Intelligent Risk Platform developer will need a user account. Licensed users can log into the Moody's Insurance Solutions Developer Portal using their email address and password.

Contact your tenant administrator and request an Intelligent Risk Platform user account.

Deprecations

Microsoft to End Support of SQL 2016 in July 2026

Microsoft will end its 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.

Accumulation API

The Create Accumulation Profile

The Create Accumulation Profile operation (POST /platform/riskdata/v1/accumulation/{id}/profiles) creates an accumulation profile.

An accumulation profile specifies general analysis settings (peril, geocoding version, etc.), scope (regions, layers, or targets), damages (damage factors and filters), and optional workers compensation settings.

This operation enables clients to to create accumulation profiles with up to 100,000 regions so that they can run accumulations for regulatory reports.

The Get Accumulation Profile

The Get Accumulation Profile operation (GET /platform/riskdata/v1/ accumulation/{id}/profiles/{profileId}) returns the specified accumulation profile.

An accumulation profile specifies general analysis settings (peril, geocoding version, etc.), scope (regions, layers, or targets), damages (damage factors and filters), and optional workers compensation settings.

This operation does not return the complete accumulation profile payload in the response. The size of the decompressed accumulation profile is greater than the API Gateway response size limit.

Batch API

Create Batch Job

The Create Batch Job operation (POST /platform/batch/v1/jobs) creates 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.

The response now returns groupingsetId and groupingSetSimulationPeriod in the input object:

{
    "name": "testBatchIRP",
    "settings": {
      ....
    },
    "tasks": [
        {
            "label": "groupingJob",
            "operationUri": "/platform/grouping/v1/jobs",
            "input": {
                ...
                "settings": {
                "groupingSetId": integer,
                "groupingSetSimulationPeriod": integer,
                ....
                }
            },
            "dependsOn": [
                "..."
            ],
            "continueOnFailure": "true"
        }
    ]
}

Get Batch Task

The Get Batch Task operation (POST /platform/batch/v1/jobs/{jobId}/tasks/{taskId}) returns detailed information about a specific task within a job.

A task is a subprocess that is run within the course of processing a BATCH job.

The response now returns groupingsetId and groupingSetSimulationPeriod in the output object:

Get Batch Task

The Get Batch Task operation (POST /platform/batch/v1/jobs/{jobId}/tasks/{taskId}) returns detailed information about a specific task within a job.

This operation now returns the exposureVariationId for all tasks that create new exposure varations.

For example, the Create Batch Job operation may initiate a reports job task, i.e. EXPOSURE_SUMMARY job (exposure summary report ) or EXPOSURE_DOI_REPORT job (California Department of Insurance report) creates a new exposure variation. If the task, creates an new exposure variation, this operation returns the corresponding exposureVariationId.

Copy API

Create Copy Job

The Create Copy Job operation (POST /platform/copy/v1/jobs) creates a copy of the specified account, aggregate portfolio, portfolio, or EDM.

This operation now supports the "deep-copying" of accounts associated with a portfolio.

The optional linkExistingAccounts parameter accepts a Boolean value.

• If true or undefined, this operation creates a link between the copy of the portfolio and the child accounts of the original portfolio. No copies of the accounts are created. The portfolio copy is linked to the original accounts.
• If false, the operation creates a copy of each child account of the original portfolio and creates a link between the portfolio copy and each account copy. The portfolio copy is linked to copies of original accounts.

The sample request creates a copy of a portfolio (256) and copies of accounts linked to that portfolio. The new portfolio (PC-001) is linked to copies of the child accounts linked to the original portfolio.

{
  "resourceUri": "/platform/riskdata/v1/exposures/10171/portfolios/256",
  "resourceType": "PORTFOLIO",
  "settings": {
    "name": "Portfolio Copy",
    "number": "PC-001",
    "description": "Copied portfolio",
    "linkExistingAccounts": false
  }
}

The settings object accepts five parameters:

Get Copy Job

The Get Copy Job operation (GET /platform/copy/v1/jobs/{jobId}) returns the specified Copy job.

Exchange Data API

The Get Share Request operation (GET /platform/exchangedata/v1/ sharekeys/{shareKey}/sharerequests/{shareRequestId}) returns the specified share request.

A share request is a request to transfer a copy of exposure or analysis data to another Intelligent Risk Platform tenant via Data Exchange. Every share request is identified by a share key, which enables the recipient to access the data.

This operation now returns information about program sets. If the resourceType is PROGRAM_SET. this operation returns program-specific information in the ResourceProperties object that enables the tenant to identify, understand, and properly manage shared program set resources.

{
  "shareRequestId": 456,
  "shareRequestName": "Program Set Exchange",
  "status": "Pending",
  "resources": [
    {
      "resourceType": "PROGRAM_SET",
      "resourceUris": ["/platform/riskdata/v1/programsets/12345"],
      "resourceProperties": [
        {
          "resourceUri": "/platform/riskdata/v1/programsets/12345",
          "resourceName": "Q1 2024 Program Set",
          "resourceSize": "2.5MB",
          "programSetId": 12345,
          "programId": 5678,
          "programName": "Commercial Auto",
          "inceptionDate": "2024-01-15",
          "programPrime": "Prime Carrier"
        }
      ]
    }
  ]
}

The inceptionDate, programId, programName, programPrime, programSetId properties are new:

Create Share Request

The Create Share Request operation (POST /platform/exchangedata/v1/sharekeys/ {shareKey}/sharerequests) creates a new share request.

A share request is a mechanism that enables Data Exchange partners to control outbound and inbound exchange of data through Risk Data Exchange. Both the outbound and inbound exchange must be approved by a Data Exchange Admin on each tenant. The share request identifies the data (resources) to share (e.g. EDM, analysis results, documents) and the recipient (recipientShareKey) of the exchange data.

This operation now supports sharing of program sets. The resourceType parameter now accepts PROGRAM_SET as a value in the request. Where the resource type is PROGRAM_SET, the request accepts a new resourceMap parameter that identifies a list of the programs to share.

{
  "shareRequestName": "Share Program Set",
  "recipientShareKey": "ABC123",
  "resources": [
    {
      "resourceType": "PROGRAM_SET",  # NEW enum value
      "resourceUris": [
        "/platform/riskdata/v1/programsets/12345"
      ],
      "resourceMap": [
        {
          "programSetId": 12345,
          "programIds": [5678, 5679]
        }
      ]
    }
  ]
}

The resourceMap parameter specifies a list of programs to share:

Review Share Request

The Review Share Request operation (POST /platform/exchangedata/v1/ sharekeys/{shareKey}/sharerequests/{shareRequestId}/review) approves or rejects a share request.

A share request is a request to transfer a copy of an EDM, analysis data, or exchange package to another Intelligent Risk Platform tenant via Data Exchange. No data is shared between tenants unless both the sender and recipient approve the share request.

This operation now supports share requests for program sets.

The request option now supports accepting or rejecting the sharing of program resources by program ID:

{
  "reviewType": "inbound-accept",
  "settings": {
    "name": "Accept Program Set Share",
    "resources": [
      {
        "resourceType": "PROGRAM_SET",
        "resourceMap": [
          {
            "programSetId": 12345,
            "programIds": [5678, 5679]
          }
        ]
      }
    ]
  }
}

The resourceMap parameter specifies a list of programs to share:

Export API

Create Export Job

The Create Export Job operation (POST /platform/export/v1/jobs/) creates and submits different types of export jobs (EDM, EXPOSURE_RESOURCE, EXPOSURE_VARIATION. LOCATION_RESULTS, RDM_DATABRIDGE, RDM, RESULTS, ROLLUP_RESULTS).

This operation now restricts naming conventions for exported databases in the RDM_DATABRIDGE and EDM job types:

• In RDM_DATABRIDGE export jobs, the name specified for exported databases must match the name of the database. No spaces are allowed in the name of the database.
• In EDM export jobs, the name specified for exported databases must match the name of the database. No spaces are allowed in the name of the database.

Create Export Job

The Create Export Job operation (POST /platform/export/v1/jobs/) creates and submits different types of export jobs.

The RDM_DATABRIDGE export type creates a DOWNLOAD_RDM job that exports analysis result data to a new or existing managed RDM database on Data Bridge.

This operation now accepts the share, owner, and groups parameters in RDM_DATABRIDGE exports.

{
  exportType: "RDM_DATABRIDGE",
  resourceType: "analyses",
  resourceUris:  ["/platform/riskdata/v1/analyses/{analysisId}],
  settings: {
    serverId: { serverId},
    rdmName: {RDM_Name}
    },
  share: "true",
  groups: ["guid1", "guid2", "guid3"]
}

These three parameters enable the tenant to define who owns, can share, and access the exported RDM:

Create Export Job

The Create Export Job operation (POST /platform/export/v1/jobs/) creates and submits different types of export jobs.

The EDM export type creates a DOWNLOAD_EDM job that exports the specified exposure data (accounts, portfolios, or aggregate portfolios) from the specified EDM (resourceUri) to a downloadable on-premise EDM as a database artifact (BAK or MDF).

This export type now accepts the optional preserveName parameter, which accepts a Boolean value. If true, the export database artifact preserves the name of the original EDM. If the database artifact is subsequently imported into the Intelligent Risk Platform using the Import API, the preserved name can be assigned to the imported EDM. See Create Import Job for details.

Grouping API

Create Grouping Job

The Create Grouping Job operation (POST /platform/grouping/v1/jobs) creates an analysis group, an analysis that combines multiple analyses.

In UnderwriteIQ, an analysis group combines the loss results from multiple regions, perils, or cedants to provide an overall risk assessment for an account. When you create a group, new grouped results combine the data from the component analyses. Currently, you can only group DLM exceedance probability (EP) results or HD exceedance probability results.

An analysis group is a collection of two or more analysis results or analysis groups that enable an insurer or reinsurer to better assess the risk to a customized portfolio of exposures. The analysis group may include analysis results generated using ALM, DLM, and HD models as well as other analysis groups. By combining event loss data from multiple analyses can view a unified loss result for exposures across diverse perils and regions.

This operation now accepts the groupingset and groupingSetSimulationPeriod parameters in the settings object of the request.

A grouping set is a collection of analysis settings that facilitate the creation of analysis groups. The grouping set specifies rules setting for resolving the differences between settings in the constituent DLM and HD analysis results.

{
    "resourceType": "analyses",
    "resourceUris": [
        "/platform/riskdata/v1/analyses/1776591",
        "/platform/riskdata/v1/analyses/1776517",
        "/platform/riskdata/v1/analyses/1776609"
    ],
    "settings": {
        "analysisName": "group_florida_grp_test_acc3",
        "description": "api_grouping NAEQ NAWS NAEQ NAWS NAEQ NAWS NAEQ NAWS NAEQ NAWS NAEQ NAWS NAEQ NAWS ",
        "groupingSetId": "integer",
        "groupingSetSimulationPeriod": "integer"
        "currency": {
            "code": "USD",
            "scheme": "RMS",
            "asOfDate": "2020-03-01",
            "vintage": "RL18"
        },

If the groupingSetId and groupingSetSimulationPeriod parameter is specified, the regionPerilSimulationSet is not required.

Get Grouping Job

The Get Grouping Job operation now returns the groupingSetId and groupingSetSimulationPeriod in the log object.

Create Grouping Task

The Create Grouping Task operation (POST /platform/grouping/v1/tasks) creates a grouping task that validates the specified grouping sets.

{
    "taskName": "Test Name",
    "settings": {
    "groups": [
        {
          "groupKey": "1",
          "profiles": [
            { "profileId": 1001, "eventRateSchemeId": 1 },
            { "profileId": 1002, "eventRateSchemeId": 1 }
          ],
          "groupingSetId": 1,
          "numOfSimulations": 100000,
        },
        {
          "groupKey": "2",
          "profiles": [
            { "profileId": 1001, "eventRateSchemeId": 1 },
            { "profileId": 1002, "eventRateSchemeId": 1 }
          ],
          "groupingSetId": 1,
          "numOfSimulations": 100000
    }
  ]
}

The groups array defines a list of grouping tasks objects.

If successful, creates a VALIDATE_GROUPING task to the workflow queue and returns a 201 Created HTTP status code. The task UUID is returned in the Location header of the response. Use the Get Grouping Task operation to poll the status of the job.

Get Grouping Task

The Get Grouping Task operation (POST /platform/grouping/v1/tasks/{{taskUuid}} ) returns information about the specified grouping task.

This operation returns data.

{
  "taskUuid": "a4a0d16c-ed47-4f76-8d0f-8a21e6b4bede",
  "taskName": "Sample Task Name",
  "taskType": "VALIDATE_GROUPING",
  "status": "COMPLETED",
  "createdAt": "2026-03-22T18:26:13.414810",
  "updatedAt": "2026-03-22T18:26:14.629626",
  "expiresAt": "2026-03-29T18:26:13.394685",
  "createdBy": "[email protected]",
  "output": {
    "errors": [],
    "log": {
      "validationResults": [
        {
          "groupKey": "1",
          "validation": {
            "errors": [
              {
                "message": "Sorry, you cannot group Non-EP account analyses."
              }
            ],
            "warnings": []
          }
        }
      ]
    }
  }
}

Import API

Create Import Job

The Create Import Job operation (POST /platform/import/v1/jobs) creates an import job.

This operation now restricts naming conventions for databases based on data imported in the CEDE and OED job types:

• In CEDE import jobs, the name of new databases based on imported data must match the EDM name. No spaces are allowed in the name of the database.
• In OED import jobs, the name of new databases based on imported data must match the EDM name. No spaces are allowed in the name of the database.

CEDE 12.0 Support

The Import API now supports CEDE 12.0 for database file of SQL server 2022.

CEDE™ (Catastrophe Exposure Database Exchange) is an open-source exposure data format from AIR. CEDE facilitates data exchange throughout "the insurance value chain and to encourage model development."

The Intelligent Risk Platform now supports importing CEDE import via the Import API. The service detects database file versions, and if SQL 2022, downgrades and restores the database to Unified Data Store (UDS) or Data Bridge, before converting the CEDE database to an EDM.

Model API

Create Model Job

The Create Model Job operation (GET /platform/model/v1/jobs) now returns the exposureVrationId of the exposure variation that was created or used for running the model job.

Risk Data API

Create Program

The Create Program operation (POST /platform/riskdata/v1/programsets/{programSetId}/programs) creates an inward program (inward reinsurance program).

An inward program is a collection of program treaties that represent contracts between the insurer and reinsurer. The inward program enables the insurer to evaluate exposure to risk within a variety of reinsurance structures, which pair an inward retrocession treaty with the subjects (exposures and risk sources) they cover.

This operation now supports the definition of erosion limits in the treaties object of the request:

{
  "treaties": [
    {
      "attributes": {
        "erosion": {
          "limitAmount": 0,
          "attachmentAmount": 0,
          "eventsOccurred": 0
        }
      }
    }
  ]
}

The erosion object includes three parameters.

Create Outward Program

The Create Outward Program operation (POST /platform/riskdata/v1/businesshierarchysets/{businessHierarchySetId}/programs) creates an outward program, a program that captures outward reinsurance structures.

An outward program is a collection of program treaties (contracts) through which losses are ceded to a reinsurer. The outward program enables you to model and quantify actual or proposed reductions in net exposure to a business hierarchy. These programs support proportional and non-proportional treaty templates, and custom treaties having user-defined CDL covers.

This operation now supports the definition of erosion limits in the treaties object of the request:

{
  "treaties": [
    {
      "attributes": {
        "erosion": {
          "limitAmount": 0,
          "attachmentAmount": 0,
          "eventsOccurred": 0
        }
      }
    }
  ]
}

The erosion object includes three parameters.

Get Program

The Get Program operation (GET /platform/riskdata/v1/programs/{programId}) returns the specified program.

A program defines a reinsurance structure that enables you to test different structure types, different subjects, or other deviations.

This operation now returns erosion limits in the treaties object of the response:

{
  "treaties": [
    {
      "attributes": {
        "erosion": {
          "limitAmount": 0,
          "attachmentAmount": 0,
          "eventsOccurred": 0
        }
      }
    }
  ]
}

The erosion object includes three properties.

Update Program

The Update Program operation (GET /platform/riskdata/v1/programs/{programId}) updates the specified program.

This operation now returns erosion limits in the treaties object of the response:

{
  "treaties": [
    {
      "attributes": {
        "erosion": {
          "limitAmount": 0,
          "attachmentAmount": 0,
          "eventsOccurred": 0
        }
      }
    }
  ]
}

The erosion object includes three properties.

Reference Data API

Create Grouping Set

The Create Grouping Set operation (POST /platform/referencedata/v1/groupingsets) creates a grouping set.

A grouping set is a collection of analysis settings that defines a template for creating analysis groups. The grouping set specifies rules setting for resolving the differences between settings in the constituent DLM and HD analysis results.

A grouping set is a resource that facilitates the creation and management of analysis group workflows. An analysis group is a collection of two or more analysis results or analysis groups that enable an insurer or reinsurer to better assess the risk to a customized portfolio of exposures. The analysis group may include analysis results generated using ALM, DLM, and HD models as well as other analysis groups. By combining event loss data from multiple analyses can view a unified loss result for exposures across diverse perils and regions.

Grouping sets facilitate the creation of account-level, HD+DLM grouping and marginal impact analysis workflows.

Grouping Workflows: The grouping set defines configurations so that the regionPerilSimulationSet parameter does not need to be specified for ELT-based model analysis.

Grouping sets facilitate the creation and management of marginal impact analysis. The Calculate Marginal Impact operation accepts (DOES IT?) a groupingSetId parameter which enables the creation marginal impact analysis based on PLT reference analysis results that combine HD or HD + DLM analysis results.

Combinations supported:

The grouping set specifies a reusable configuration for modeling analysis groups. The grouping set specifies configurations that facilitates the grouping analysis results using the Grouping API. Once defined, a grouping set can be used to quickly and easily define configuration setting used in grouping jobs.

Grouping sets are designed to facilitate the following scenarios:

• Specify the simulation profile to use for each DLM profile in an analysis group that combines DLM and HD profiles (for account grouping or marginal impact).
• Specify the simulation profile to use for each DLM profile in a marginal impact analysis using an HD reference analysis that needs to map a DLM model profile to an HD
• Specify the simulation profile to use for each DLM profile in a marginal impact analysis using a DLM reference analysis that needs to map the simulation profile to HD model profiles.

The grouping set defines a mapping between event rate scheme and simulation set (PEQT) mapping for every model and event rate scheme combination. [In this context, a model is defined as the combination of a region, peril, and version.]

A grouping set is a resource that facilitates the management of analysis groups account grouping or grouped marginal impact reporting. The grouping set defines a reusable set of analysis settings that can be applied to model jobs based on . The grouping set can define an event rate scheme that is used

A grouping set can be used to define

• Pre-define an event rate scheme for all Moody’s DLM/ALM models, to be used in the event of a rate scheme conflict while ELT grouping.
• Pre-define a period event quantile table (PEQT) for all Moody’s DLM/ALM models, to be used in the event of a rate scheme conflict while PLT grouping.
• Select the grouping set I wish to use in the grouping user interface.

Every grouping set is immutable. Once defined, grouping set configurations cannot be updated. The tenant can, however, create copies of existing grouping sets and redefine the configurations in those copies to support different use cases.

Admins can specify a grouping set as default (isDefault) or archive (isArchive).

{
  "groupingSetName": "KK_Storyparam",
  "groupingSetDetails": [
    {
      "peril": "Severe Convective Storm",
      "region": "Australia",
      "perilCode": "CS",
      "RegionCode": "AU",
      "modelRegionCode": "AUCS",
      "modelVersionCode": "10.0",
      "eventRateSchemeId": 48,
      "eventRateSchemeName": "RMS Stochastic Event Rates",
      "simulationSetName": "Australia Severe Convective Storm, Risklink 10.0",
      "simulationSetId": 59,
      "isDefault": false
    }
  ]
}

Update Grouping Set

The Update Grouping Set operation (PATCH /platform/referencedata/v1/groupingsets/{id}) supports .

A grouping set is immutable. Once defined, grouping set configurations cannot be changed.

{
  "isDefault": true,
  "isActive": false
}

The request accepts two optional body parameters:

Delete Grouping Set

The Delete Grouping Set operation (DELETE /platform/referencedata/v1/groupingsets/{id}) deletes the specified grouping set.

A grouping set is a collection of analysis settings that facilitate the creation of analysis groups. The grouping set specifies rules setting for resolving the differences between settings in the constituent DLM and HD analysis results.

Search Grouping Set

The Search Grouping Set operation (GET /platform/referencedata/v1/groupingsets) returns a list of grouping sets.

A grouping set is a collection of analysis settings that facilitate the creation of analysis groups. The grouping set specifies rules setting for resolving the differences between settings in the constituent DLM and HD analysis results.

This operation supports filtering by property values:

For each record that matches the query filter, the response returns a grouping set object:

[
    {
    "groupingSetName": "string",
    "groupingSetId": integer,
    "createdBy": "string",
    "createdAt": "string",
    "isActive": true,
    "isDefault": true
    }
]

Get Grouping Set

The Get Grouping Set operation (GET /platform/referencedata/v1/groupingsets/{id}) returns the specified grouping set.

A grouping set is a collection of analysis settings that facilitate the creation of analysis groups. The grouping set specifies rules setting for resolving the differences between settings in the constituent DLM and HD analysis results.

{
    "groupingSetName": "string",
    "groupingSetDetails":
        [
            {
                "peril": "string",
                "region": "string",
                "perilCode": "string",
                "RegionCode": "string",
                "modelRegionCode": "string",
                "modelVersionCode": "string",
                "eventRateSchemeId": integer,
                "eventRateSchemeName": "string",
                "simulationSetName": "string",
                "simulationSetId": integer,
                "isSeeded": boolean
            }
      ],
    "createdBy": "string",
    "createdAt": "string"
}

Search Analysis Results

The Search Analysis Results operation (GET /platform/riskdata/v1/analyses) returns a list of analysis results.

This operation now returns the owner, createdBy, and groupingSetId properties for each analysis result.

Get Marginal EP Metrics

The Get Marginal EP Metrics operation (GET /platform/riskdata/v1/analysis/{analysisId}/marginal-ep) returns exceedance probability (EP) metrics for a specified ELT-based or PLT-based marginal impact analysis.

This operation now returns up to 50 EP return periods. Previously, this operation returned the standard 12 EP points per curve: 2, 5, 10, 25, 50, 100, 200, 250, 500, 1000, 5000, 10000, 50000.

Get Marginal EP Metrics

The Get Marginal EP Metrics operation (GET /platform/riskdata/v1/analysis/{analysisId}/marginal-ep) returns exceedance probability (EP) metrics for a specified ELT-based or PLT-based marginal impact analysis.

This operation now supports the optional epType query parameter that enables the client to filter EP metrics by exceedence probability metric type. One of AEP (aggregate EP), CEP (stochastic conditional EP), OEP (occurence EP),SMOOTHED_AEP (Smoothed AEP), SMOOTHED_OEP (Smoothed OEP), TCE_AEP (tail conditional expectation AEP), TCE_OEP (tail conditional expectation OEP), and UNRECOGNIZED.

Get Marginal EP Metrics

The Get Marginal EP Metrics operation (GET /platform/riskdata/v1/analysis/{analysisId}/marginal-ep) returns exceedance probability (EP) metrics for a specified ELT-based or PLT-based marginal impact analysis.

This operation now returns smoothed metrics. Standard EP metrics are computed from a single period (AEP) or period/event (OEP), which can result in metrics that are unstable, noisy and, ultimately, ill-suited to decision making. Smoothed EP metrics produce marginal impact metrics that are better suited to PLT-based analysis.

Smoothed marginal metrics are available across all HD-supported financial perspectives For details. see Calculate Marginal Impact.

Calculate Marginal Impact

The [Calculate Marginal Impact]{ref:marginalimpact) operation (POST /platform/riskdata/v1/analysis/marginal-impact) calculates marginal impact analysis that measures the effect of adding additional accounts to an existing portfolio as differential losses.

This operation supports two distinct operations for calculating PLT-based marginal impact analysis. This optional settings object specifies the methodology used to calculate PLT metrics.:

• Standard metrics
• Smoothed metrics are better suited for decision making than raw single-period AEP or period/event OEP EP curves).

{
  "currency": {
    "currencyAsOfDate": "2025-05-28",
    "currencyCode": "USD",
    "currencyScheme": "RMS",
    "currencyVintage": "RL25"
  },
  "outputLevel": "ACCOUNT",
  "marginalImpactAnalysisIds": [266014],
  "jobName": "Test_MI_Bala",
  "eventRateSchemeIds": [12],
  "settings": {
    "pltMethodology": ["SMOOTHED", "STANDARD"]
  }
}

If unspecified, the operation produces STANDARD EP metrics.

The settings object includes the pltMethodology array parameter which accepts the following values SMOOTHED, STANDARD, or both.

Rollup API

Create Rollup Job

The Create Rollup Job operation (POST /platform/rollup/v1/jobs) creates a rollup analysis job for the specified inward program, program variation, or business hierarchy.

The operation now accepts an optional applyErosions parameter in the settings object that specifies a Boolean value. If true, erosions are applied to the rollup analysis. If false, the analysis uses the default per contract alignment. By default, false.

By applying "erosions", you can get more accurate information about the potential of future losses from underwritten contracts, especially in the case of event response use cases.

If specified, the roll-up analysis takes existing erosion of the aggregate limit, aggregate attachment, and prior events (for trigger-type) into account when calculating loss because any future losses will be limited to the contract limit less any losses suffered.

{
  "resourceUri": "platform/riskdata/v1/programs/1134342",
  "settings": {
    "includeProgram": true,
    "includeIntermediate": true,
    "includePricing": false,
    "applyErosions": false,
    "programProperties": {
      "alignInceptionDates": true,
      "marginalImpactProperties": {
        "isSegmented": true
      }
    }
  }
}

Tenant Data API

Search VPN Connection

The Search VPN Connection operation returns a list VPN connections.

A VPN connection is a set of configurations that define a secure, encrypted site-to-site connection between a tenant's on-premises SQL Server instances and their managed server instances on Data Bridge.

This operation now returns the tunnelStatus property which shows the status of the VPN connection.

Get VPN Connection

The Get VPN Connection operation returns the specified VPN connections.

A VPN connection is a set of configurations that define a secure, encrypted site-to-site connection between a tenant's on-premises SQL Server instances and their managed server instances on Data Bridge.

This operation now returns the tunnelStatus property which shows the status of the VPN connection.

Update VPN Connection

The Update VPN Connection operation updates the specified VPN connection.

A VPN connection is a set of configurations that define a secure, encrypted site-to-site connection between a tenant's on-premises SQL Server instances and their managed server instances on Data Bridge.