Configure and consume the Guidewire PolicyCenter Cloud API to create and endorse a personal lines auto policy
domain: docs.guidewire.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate to PolicyCenter Cloud using OAuth 2.0; obtain an access token from your Guidewire Cloud tenant's identity provider and include it as a Bearer token in all API requests
Review the OpenAPI specification for your PolicyCenter version at the Swagger UI path (your PolicyCenter URL + /resources/swagger-ui/) to understand available endpoints and schemas for your tenant's configuration
Create a new submission via POST to the submissions endpoint with applicant, vehicle, and driver details; PolicyCenter returns a submission ID and job number
Advance the submission through the workflow stages (Gathering Info, Quote, Bind) using the appropriate action endpoints; each stage may require additional data payload (underwriting answers, payment information)
Retrieve the issued policy via GET /policies with query parameters for policy number or account; confirm the policy status is 'in force' before notifying the customer
To endorse the policy mid-term (e.g., add a vehicle), create a policy change job via POST to the policyChanges endpoint, supply the changes, and advance through Quote and Bind stages for the endorsement
Known gotchas
PolicyCenter Cloud API is versioned by release (e.g., 202407, 202503); the endpoint paths and payload schemas differ between versions — always target the API version matching your deployed PolicyCenter release
Many PolicyCenter implementations have custom extensions (Gosu code, configuration sets) that alter required fields or validation rules beyond the base documentation — coordinate with your Guidewire configuration team to get the actual required fields for your tenant
The Cloud API uses Swagger 2.0 specification; tools that expect OpenAPI 3.0 may require conversion — use the provided swagger.json directly rather than relying on auto-converted specs
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?