Submit a Verisk A-PLUS Property Report Claims request via the UnderWriting API for homeowners loss-history underwriting
domain: gateway.verisk.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register for the A-PLUS Property product with Verisk to receive a consumer_key and consumer_secret for the UnderWriting API.
POST to the token endpoint with Content-Type application/x-www-form-urlencoded, an Authorization header of Basic plus the base64-encoded consumer_key:consumer_secret, and body grant_type=client_credentials to receive a bearer access token (valid 60 minutes).
POST the search request to https://gateway.verisk.com/underwriting/aplusproperty/claims/v4 (or the gatewayuat host for testing) with the OrgId/ShipId from your account, insured first/last name, and current risk address, using the bearer token in the Authorization header.
Parse the returned matched claims (loss date, cause, amount paid) for the individual, business, or specific risk location.
Contact PLUWClientServices@verisk.com for the full request/response XML/JSON schemas and samples before building production payloads.
Known gotchas
The access token expires after 60 minutes and should be cached and reused rather than re-requested on every call, or you risk hitting rate limits.
V4 removed the Business fields present in V3 and added a StatusCode field to the response — don't reuse a V3 integration's schema.
UAT (gatewayuat.verisk.com) and production (gateway.verisk.com) are separate hosts with separate credentials — a UAT token will not authenticate against production.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?