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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Moody's RMS

Moody's RMS Location V1 API

The LocationV1 API from Moody's RMS — 30 operation(s) for locationv1.

Documentation Provider Profile APIs.io OpenAPI GitHub

Moody’s RMS Location 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 LocationV1. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a changelog.

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

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

57 operations 30 paths 33 schemas 13 DELETE15 GET16 POST13 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 Location 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 57

Across 30 paths, the API surfaces 57 operations — 13 DELETE, 15 GET, 16 POST, 13 PUT. Each is listed below with its method, path, parameters, and response codes.

LocationV1 57
GET
/v1/locations
Get locations
searchLocations 6 params → 200400403
POST
/v1/locations
Create location
createLocation 1 param body → 201400403
GET
/v1/locations/{id}
Get location
getLocation 2 params → 200400403
PUT
/v1/locations/{id}
Update location
updateLocation 2 params body → 204400403
DELETE
/v1/locations/{id}
Delete location
deleteLocation 2 params → 204400403
POST
/v1/locations/{id}/locationbidetail
Create BI peril
createLocationBiDetail 2 params body → 201400403
GET
/v1/locations/{id}/locationbidetail/{locationbidetailid}
Get BI peril
getLocationBiDetail 3 params → 200400403
PUT
/v1/locations/{id}/locationbidetail/{locationbidetailid}
Update BI peril
updateLocationBiDetail 3 params body → 204400403404
DELETE
/v1/locations/{id}/locationbidetail/{locationbidetailid}
Delete BI peril
deleteLocationBiDetail 3 params → 204400403
POST
/v1/locations/{id}/locationcondition
Add location condition
createLocationCondition 2 params body → 201400403
POST
/v1/locations/locationcondition/batch
Manage location conditions in batch
batchProcessLocationConditions 1 param body → 201400403405
GET
/v1/locations/{id}/locationcondition/{conditionid}
Get location condition
getLocationConditionById 3 params → 200400403
PUT
/v1/locations/{id}/locationcondition/{conditionid}
Update location condition
updateLocationCondition 3 params body → 204400403404
DELETE
/v1/locations/{id}/locationcondition/{conditionid}
Delete location condition
deleteLocationCondition 3 params → 204400403
POST
/v1/locations/{id}/coverage
Create location coverage
createLocationCoverage 2 params body → 201
GET
/v1/locations/{id}/coverage/{coverageid}
Get location coverage
getLocationCoverage 3 params → 200400403
PUT
/v1/locations/{id}/coverage/{coverageid}
Update coverage
updateLocationCoverage 3 params body → 204400403404
DELETE
/v1/locations/{id}/coverage/{coverageid}
Delete location coverage
deleteLocationCoverage 3 params → 204400403
POST
/v1/locations/{id}/locationeqdetail
Create EQ peril
createLocationEqDetail 2 params body → 201400403
GET
/v1/locations/{id}/locationeqdetail/{locationeqdetailid}
Get EQ peril
getLocationEqDetail 3 params → 200400403
PUT
/v1/locations/{id}/locationeqdetail/{locationeqdetailid}
Update EQ peril
updateLocationEqDetail 3 params body → 204400403404
DELETE
/v1/locations/{id}/locationeqdetail/{locationeqdetailid}
Delete EQ peril
deleteLocationEqDetail 3 params → 204400403
POST
/v1/locations/{id}/locationfldetail
Create FL peril
createLocationFlDetail 2 params body → 201400403
GET
/v1/locations/{id}/locationfldetail/{locationfldetailid}
Get FL peril
getLocationFlDetail 3 params → 200400403
PUT
/v1/locations/{id}/locationfldetail/{locationfldetailid}
Update FL peril
updateLocationFlDetail 3 params body → 204400403404
DELETE
/v1/locations/{id}/locationfldetail/{locationfldetailid}
Delete FL peril
deleteLocationFlDetail 3 params → 204400403
POST
/v1/locations/{id}/locationfrdetail
Create FR peril
createLocationFrDetail 2 params body → 201400403
GET
/v1/locations/{id}/locationfrdetail/{locationfrdetailid}
Get FR peril
getLocationFrDetail 3 params → 200400403
PUT
/v1/locations/{id}/locationfrdetail/{locationfrdetailid}
Update FR peril
updateLocationFrDetail 3 params body → 204400403404
DELETE
/v1/locations/{id}/locationfrdetail/{locationfrdetailid}
Delete FR peril
deleteLocationFrDetail 3 params → 204400403
POST
/v1/locations/{id}/cession
Create reinsurance cession
createLocationReinsuranceCession 2 params body → 201400403
GET
/v1/locations/{id}/cession/{cessionid}
Get reinsurance cession
getLocationReinsuranceCessionDetail 3 params → 200400403
PUT
/v1/locations/{id}/cession/{cessionid}
Update reinsurance cession
updateLocationReinsuranceCession 3 params body → 204400403
DELETE
/v1/locations/{id}/cession/{cessionid}
Delete reinsurance cession
deleteLocationReinsuranceCession 3 params → 204400403
POST
/v1/locations/{id}/locationtodetail
Create TO peril
createLocationToDetail 2 params body → 201400403
GET
/v1/locations/{id}/locationtodetail/{locationtodetailid}
Get TO peril
getLocationToDetail 3 params → 200400403
PUT
/v1/locations/{id}/locationtodetail/{locationtodetailid}
Update TO peril
updateLocationToDetail 3 params body → 204400403404
DELETE
/v1/locations/{id}/locationtodetail/{locationtodetailid}
Delete TO peril
deleteLocationToDetail 3 params → 204400403
POST
/v1/locations/{id}/locationtrdetail
Create TR peril
createLocationTrDetail 2 params body → 201400403
GET
/v1/locations/{id}/locationtrdetail/{locationtrdetailid}
Get TR peril
getLocationTrDetail 3 params → 200400403
PUT
/v1/locations/{id}/locationtrdetail/{locationtrdetailid}
Update TR peril
updateLocationTrDetail 3 params body → 204400403
DELETE
/v1/locations/{id}/locationtrdetail/{locationtrdetailid}
Delete TR peril
deleteLocationTrDetail 3 params → 204400403
POST
/v1/locations/{id}/locationwcdetail
Create WC
createLocationWcDetail 2 params body → 201400403
GET
/v1/locations/{id}/locationwcdetail/{locationwcdetailid}
Get WC
getLocationWcDetail 3 params → 200400403
PUT
/v1/locations/{id}/locationwcdetail/{locationwcdetailid}
Update WC
updateLocationWcDetail 3 params body → 204400403
DELETE
/v1/locations/{id}/locationwcdetail/{locationwcdetailid}
Delete WC
deleteLocationWcDetail 3 params → 204400403
POST
/v1/locations/{id}/locationwsdetail
Create WS peril
createLocationWsDetail 2 params body → 201400403
GET
/v1/locations/{id}/locationwsdetail/{locationwsdetailid}
Get WS peril
getLocationWsDetail 3 params → 200400403
PUT
/v1/locations/{id}/locationwsdetail/{locationwsdetailid}
Update WS peril
updateLocationWsDetail 3 params body → 204400403
DELETE
/v1/locations/{id}/locationwsdetail/{locationwsdetailid}
Delete WS peril
deleteLocationWsDetail 3 params → 204400403
POST
/v1/locations/{id}/buildingattribute
Create building attribute
createBuildingAttribute 2 params body → 201400403
GET
/v1/locations/{id}/buildingattribute/{buildingattributeid}
Get building attribute
getBuildingAttribute 3 params → 200400403
PUT
/v1/locations/{id}/buildingattribute/{buildingattributeid}
Update building attribute
updateBuildingAttribute 3 params body → 204400403404
DELETE
/v1/locations/{id}/buildingattribute/{buildingattributeid}
Delete building attribute
deleteBuildingAttribute 3 params → 204400403
POST
/v1/locations/geocode
Geocode address
geoCodeByAddress body → 200400403
POST
/v1/locations/{id}/geocode
Geocode or hazard location
geoCodeByLocationId 2 params body → 201400403
GET
/v1/locations/{id}/policyconditions
Get policy conditions by location
getPolicyConditions 2 params → 200400403

Schemas 33

The contract defines 33 schemas that model the data the API accepts and returns. The most detailed are LocationEqDetail (198 properties), LocationFrDetail (131 properties), LocationWsDetail (126 properties), LocationFlDetail (99 properties). Each schema is shown below with its type and property counts.

FacReinsurer
object
2 properties
Location
object
19 properties 2 required
Property
object
46 properties 1 required
LocationBuildingAttribute
object
25 properties
LocationCondition
object
3 properties
PolicyCondition
object
12 properties
BatchRequest
object
3 properties
LineOfBusiness
object
2 properties 1 required
LayerInfo
object
5 properties 4 required
LocationToDetail
object
67 properties
MetaLinks
object
2 properties 2 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
ExposureValue
object
3 properties
LossOccurrence
object
7 properties 1 required
ErrorMessage
object
3 properties
LocationWcDetail
object
24 properties
LocationCoverage
object
18 properties
Producer
object
Agent or brokerage firm that produced a policy.
2 properties 1 required
LocationSearchResult
object
2 properties
LocationWsDetail
object
126 properties
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
LocationSearchItem
object
2 properties
Link
object
3 properties 3 required
Address
object
65 properties
LocationBiDetail
object
7 properties
LocationFlDetail
object
99 properties
PolicyConditionCriteria
object
7 properties
Meta
object
5 properties
ReinsuranceCession
object
14 properties
BuildingAttribute
object
28 properties
LocationFrDetail
object
131 properties
LocationTrDetail
object
68 properties
LocationEqDetail
object
198 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Moody's RMS publishes across the network.

Moody's RMS Platform APIs
AE Profile APIs.io
Moody's RMS Climate On Demand API
AE Profile APIs.io
Moody's RMS Platform MCP Server
AE Profile APIs.io
Moody's RMS Account V1 API
AE Profile APIs.io
Moody's RMS Account V2 API
AE Profile APIs.io
Moody's RMS Aggregate PortfolioV1 API
AE Profile APIs.io
Moody's RMS Aggregate PortfolioV2 API
AE Profile APIs.io
Moody's RMS Analysis GroupsV1 API
AE Profile APIs.io
Moody's RMS Analysis GroupsV2 API
AE Profile APIs.io
Moody's RMS Branch V1 API
AE Profile APIs.io
Moody's RMS Cedant V1 API
AE Profile APIs.io
Moody's RMS Client IP API
AE Profile APIs.io
#LocationV1
← Back to M APIs
API Details
ID
moodys-rms:moodys-rms-locationv1-api
Base URL
https://api-use1.rms.com/platform
Docs
https://developer.rms.com/platform
Provider
Moody's RMS
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=moodys-rms-locationv1-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/moodys-rms-locationv1-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Moody's RMS Location 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.