Nephila RiskStore

GetDealExpectedLossRequest

EventSets

The following routes are available for this service:
POST	/api/riskstore/eventset/deal-expected-loss	Get the deals expected losses by metarisk

"use strict";
export class DealExpectedLoss {
    /** @param {{sourceDealId?:number,perspectiveId?:number,metaRiskId?:number,elAgg?:number,elOcc?:number,pAtt?:number,pExh?:number}} [init] */
    constructor(init) { Object.assign(this, init) }
    /** @type {number} */
    sourceDealId;
    /** @type {number} */
    perspectiveId;
    /** @type {number} */
    metaRiskId;
    /** @type {number} */
    elAgg;
    /** @type {number} */
    elOcc;
    /** @type {number} */
    pAtt;
    /** @type {number} */
    pExh;
}
export class GetDealExpectedLossResponse {
    /** @param {{dealExpectedLosses?:DealExpectedLoss[],responseStatus?:ResponseStatus}} [init] */
    constructor(init) { Object.assign(this, init) }
    /** @type {DealExpectedLoss[]} */
    dealExpectedLosses;
    /** @type {ResponseStatus} */
    responseStatus;
}
export class GetDealExpectedLossRequest {
    /** @param {{sourceDealSystem?:string,asOf?:string,metaRiskIds?:number[],perspectiveIds?:number[],perspectiveTypeIds?:number[],sourceDealIds?:number[]}} [init] */
    constructor(init) { Object.assign(this, init) }
    /**
     * @type {string}
     * @description The source deal system (IGN) to get the date for */
    sourceDealSystem;
    /**
     * @type {?string}
     * @description The as of date to query */
    asOf;
    /**
     * @type {number[]}
     * @description The metarisks to query for */
    metaRiskIds = [];
    /**
     * @type {number[]}
     * @description The perspectives to query for */
    perspectiveIds;
    /**
     * @type {number[]}
     * @description The perspectives types to query for (0 - Vendor, 10 - Nephila 1.0, 16 - Nephila 2.0 etc...) */
    perspectiveTypeIds;
    /**
     * @type {number[]}
     * @description The source deal ids to query for */
    sourceDealIds = [];
}

JavaScript GetDealExpectedLossRequest DTOs

To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /api/riskstore/eventset/deal-expected-loss HTTP/1.1 
Host: riskstoreng-dev.nephila.com 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"sourceDealSystem":"String","asOf":"0001-01-01T00:00:00.0000000Z","metaRiskIds":[0],"perspectiveIds":[0],"perspectiveTypeIds":[0],"sourceDealIds":[0]}

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"dealExpectedLosses":[{"sourceDealId":0,"perspectiveId":0,"metaRiskId":0,"elAgg":0,"elOcc":0,"pAtt":0,"pExh":0}],"responseStatus":{"__type":"ServiceStack.ResponseStatus, ServiceStack.Interfaces","errorCode":"String","message":"String","stackTrace":"String","errors":[{"__type":"ServiceStack.ResponseError, ServiceStack.Interfaces","errorCode":"String","fieldName":"String","message":"String","meta":{"String":"String"}}],"meta":{"String":"String"}}}