Integrate a Duck Creek Policy administration system for policy issuance via its API layer
domain: insurance-general · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with the Duck Creek OnDemand or on-premises API using the configured authentication method (typically OAuth 2.0 or API key depending on deployment)
Initiate a new submission by calling the Duck Creek submission API endpoint with insured details, line of business, and effective date
Populate risk data fields as required by the product configuration using the API request schema for the target product
Retrieve a quote by triggering the rating step and parsing the premium and coverage detail from the response
Bind the policy by calling the bind endpoint and capture the policy number returned in the response
Retrieve the issued policy document or document generation request from Duck Creek's document service
Known gotchas
Duck Creek's API schema is product-configuration-driven — the request and response field structure varies by carrier and product configuration, so generic schema assumptions will fail; always request the carrier-specific API schema or Swagger definition
Duck Creek OnDemand (cloud) and on-premises deployments may have different API versions and authentication mechanisms; confirm the deployment type before integration
Policy transactions such as endorsements and renewals have their own API flows that differ from new business submission; do not reuse the new business payload structure for mid-term changes
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