How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Moody's RMS Treaty V1 API

The TreatyV1 API from Moody's RMS — 11 operation(s) for treatyv1.

Moody’s RMS Treaty V1 API is one of 50 APIs that Moody’s RMS publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include TreatyV1. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a changelog.

This API exposes 18 operations across 11 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version March, 2023.

Requests are made against a single base URL, https://{host}/riskmodeler.

18 operations 11 paths 11 schemas 3 DELETE7 GET6 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
March, 2023
Base URL
https://api-use1.rms.com/platform
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Moody's RMS Treaty V1 API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (RMS_Auth). By default, every request must be authenticated.

  • RMS_Auth — An API key is a token that enables a client application to make requests to tenant applications running on Intelligent Risk Platform.

Paths & Operations 18

Across 11 paths, the API surfaces 18 operations — 3 DELETE, 7 GET, 6 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

TreatyV1 18
GET
/v1/treaties
Get treaties
getTreatiesByFilters 5 params → 200400403404
POST
/v1/treaties
Create treaty
createTreaty 1 param body → 201400403404
GET
/v1/treaties/count
Count treaties
getExposureCountTreaty 1 param → 200400403
GET
/v1/treaties/getbytype
Get treaties by type
getTreaties 3 params → 200400403404
GET
/v1/treaties/{id}
Get treaty
getTreaty 2 params → 200400403404
PUT
/v1/treaties/{id}
Update treaty
updateTreaty 2 params body → 204400403
DELETE
/v1/treaties/{id}
Delete treaty
deleteTreaty 2 params → 204400403404
POST
/v1/treaties/{id}/convertcurrency
Convert currency by treaty
convertCurrencyTreaty 2 params body → 202400403
POST
/v1/treaties/{id}/copy
Copy treaty
copyTreaty 2 params body → 201400403404
POST
/v1/treaties/{id}/lob
Create LOB by treaty
createTreatyLob 2 params body → 201400403
GET
/v1/treaties/{id}/lob/{lobid}
Get LOB by treaty
getTreatyLob 3 params → 200400403404
DELETE
/v1/treaties/{id}/lob/{lobid}
Delete treaty LOB
deleteTreatyLob 3 params → 204400403404
POST
/v1/treaties/lob/batch
Manage treaty LOBs in batch
batchProcessTreatyLobs 1 param body → 200400403
GET
/v1/treaties/{treatyId}/lossoccurrences
Get loss occurrences by treaty
getLossOccurrences 2 params → 200400403404
POST
/v1/treaties/{treatyId}/lossoccurrences
Create loss occurrence
createLossOccurrence 2 params body → 201400403404
GET
/v1/treaties/{treatyId}/lossoccurrences/{lossOccurrenceId}
Get loss occurrence by treaty
getLossOccurrence 3 params → 200400403404
PUT
/v1/treaties/{treatyId}/lossoccurrences/{lossOccurrenceId}
Update loss occurrence
updateLossOccurrence 3 params body → 204400403
DELETE
/v1/treaties/{treatyId}/lossoccurrences/{lossOccurrenceId}
Delete loss occurrence
deleteLossOccurrence 3 params → 204400403404

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are Treaty (31 properties), LossOccurrence (7 properties), Currency (4 properties), ErrorMessage (3 properties). Each schema is shown below with its type and property counts.

Treaty
object
A reinsurance contract between an underwriter and a primary insurer that applies to a collection of related exposures. Under the terms of the treaty, the prima…
31 properties 4 required
TreatySearchResult
object
2 properties
ExposureValue
object
3 properties
LossOccurrence
object
7 properties 1 required
ErrorMessage
object
3 properties
BatchRequest
object
3 properties
LineOfBusiness
object
2 properties 1 required
CopyTreatyInfo
object
2 properties 1 required
Producer
object
Agent or brokerage firm that produced a policy.
2 properties 1 required
Currency
object
4 properties 4 required
Cedant
object
A risk-holding party (insurer/reinsurer) that is transferring a portion of risk to another risk-holding party (reinsurer/retrocessionaire).
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

moodys-rms-treatyv1-api-openapi.yml Raw ↑

Other APIs Moody's RMS publishes across the network.

Moody's RMS Platform APIs
Moody's RMS Climate On Demand API
Moody's RMS Platform MCP Server
Moody's RMS Account V1 API
Moody's RMS Account V2 API
Moody's RMS Aggregate PortfolioV1 API
Moody's RMS Aggregate PortfolioV2 API
Moody's RMS Analysis GroupsV1 API
Moody's RMS Analysis GroupsV2 API
Moody's RMS Branch V1 API
Moody's RMS Cedant V1 API
Moody's RMS Client IP API
Where this information came from

This is an independent, third-party profile of Moody's RMS Treaty V1 API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.