Obtain an OAuth 2.0 access token from your Guidewire tenant's authorization server using client credentials flow; store as YOUR_GW_TOKEN.
POST to /rest/claim/v1/claims with a JSON body containing lossDate, lossType, policyId, and reportedDate to open a new claim; capture the returned claimId.
Add exposures to the claim by POSTing to /rest/claim/v1/claims/{claimId}/exposures with coverageType and relatedTo fields.
Update claim fields (e.g., assignedAdjuster, status) via PATCH /rest/claim/v1/claims/{claimId} using a JSON Merge Patch body.
Retrieve the Swagger definition from <applicationURL>/rest/claim/v1/swagger.json via Swagger UI at <applicationURL>/resources/swagger-ui/ to verify available endpoints for your tenant's release.
Consult the ClaimCenter Cloud API Developer Guide at docs.guidewire.com/cloud/cc/ for the current release to confirm field names and enumerations before coding.
Known gotchas
Guidewire releases new API versions (e.g., 202503, 202511) on a quarterly cadence; an endpoint or field available in one release may be absent or renamed in another — always target the Swagger for your specific tenant version.
The /rest/ base path is tenant-scoped; attempting to use a generic hostname without the correct application URL returns 404 and is a common misconfiguration.
Certain coverage types require both an exposure and a corresponding reserve transaction before the claim transitions out of Draft status; omitting the reserve step causes workflow validation failures.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp