Duck Creek API
Duck Creek Technologies is a property and casualty (P&C) insurance core platform covering Policy, Rating, Billing, Claims, Distribution Management, and Reinsurance for carriers. An unofficial API lets you programmatically pull policies, quotes, endorsements, billing accounts and invoices, claims and assignments, producer and policyholder records—and push updates like new submissions, payments, FNOLs, and claim status changes back into Duck Creek.
What is Duck Creek?
Duck Creek Technologies is a property and casualty (P&C) insurance core platform used by carriers worldwide to run policy administration, rating, billing, claims, distribution, and reinsurance. The suite is designed for low-code configuration and an API-first architecture, giving carriers an environment where business logic can be decoupled from core code so customizations remain upgrade-safe across releases.
Core product areas include:
- Policy Management (Submissions, Quotes, Policies, Endorsements, Renewals, Cancellations)
- Rating Engine (Rate Books, Algorithms, Multi-State Rules, Endorsement Pricing)
- Billing Platform (Accounts, Invoices, Payments, EFT, Disbursements)
- Claims Management (FNOL, Claims, Coverages, Reserves, Payments, Assignments)
- Distribution Management (Producers, Agencies, Licensing, Commissions, Hierarchies)
- Reinsurance, Loss Control, Policyholder Portal, and Producer Portal
Common data entities:
- Users, Roles/Permissions (Underwriters, Adjusters, Producers, Customer Service)
- Submissions, Quotes, Policies (terms, coverages, exposures, forms)
- Insureds, Locations, Vehicles, and other risk objects
- Endorsements, Renewals, Cancellations, Reinstatements
- Billing Accounts, Invoices, Payments, Disbursements, Commission Statements
- Claims, Coverages, Reserves, Payments, Recoveries, Assignments
- Producers, Agencies, Licenses, Appointments, Commission Schedules
- Documents & Attachments (declarations, ACORD forms, claim photos, correspondence)
The Duck Creek Integration Challenge
Carriers rely on Duck Creek daily, but turning configured workflows and partner-mediated APIs into self-serve automation is non-trivial:
- Carrier-by-carrier customization: OnDemand and Active Delivery installs differ widely in product configuration, forms, rating algorithms, and business rules
- Configuration vs. code: Low-code product models, manuscripts, and inheritance trees mean every tenant exposes a different API surface despite a shared platform
- Partner ecosystem gates: Many integrations (LexisNexis, CoreLogic, ISO, Hyland, e-signature, payments) sit behind certified partner programs rather than open developer access
- Sparse self-serve APIs: Duck Creek advertises an API-first architecture with thousands of endpoints, but carrier-specific exposure, sandbox access, and documentation are typically negotiated, not public
- Authentication complexity: SSO (SAML/OAuth), MFA, and producer/policyholder portal sessions complicate headless automation
- Workflow rigor: Submissions, endorsements, and claim transactions move through multi-step state machines with approvals, effective dates, and document generation
- Data spread: Policy, billing, and claims systems each maintain their own object models that must be reconciled by account, policy number, and party
How Supergood Creates Duck Creek APIs
Supergood reverse-engineers authenticated browser flows, configured platform endpoints, and partner-mediated integrations to deliver a resilient API layer for your Duck Creek environment.
- Handles username/password, SSO/OAuth, and MFA (SMS, email, TOTP) securely
- Maintains session continuity with automated refresh and change detection across Policy, Billing, and Claims
- Normalizes responses across configured product models so you can integrate once and rely on consistent objects for policies, claims, and billing
- Aligns with carrier entitlements, role-based access, and document-handling rules to ensure compliant access
Use Duck Creek with AI agents: Duck Creek MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your modules, deployment model (OnDemand or Active Delivery), and authentication setup.
- Supergood Generates and Validates Your API
We deliver a production-ready Duck Creek adapter tailored to your carrier configuration and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Duck Creek evolves.
API Endpoints
Authentication
/authenticateAuthenticate with Duck Creek using username/password, SSO, or MFA and obtain a session token
Policies
/policiesList policies with terms, coverages, exposures, and forms across PolicyCenter
Policies
/create_policySubmit a new quote or bind a policy with insureds, locations, and rating inputs
Claims
/claimsRetrieve claims with coverages, reserves, payments, and assignments from ClaimCenter
Claims
/file_claimFile a first notice of loss (FNOL) with parties, incident details, and supporting documents
Billing
/billingPull billing accounts, invoices, payments, disbursements, and commission statements
Use Cases
Sync Policies and Claims Across Centers
- Pull policies, endorsements, and renewals from PolicyCenter - Reconcile claim records and reserves from ClaimCenter - Keep account, policy, and party identifiers consistent across systems
Automate FNOL Intake
- Capture first notice of loss from web, mobile, and partner channels - Create claims with coverages, parties, and incident details in ClaimCenter - Trigger assignment, reserves, and document generation downstream
Reconcile Billing and Disbursements
- Pull billing accounts, invoices, and payment activity from the billing platform - Match disbursements and commission statements to producers and agencies - Surface delinquencies, write-offs, and EFT exceptions for finance workflows
Power Partner and Producer App Integrations
- Expose policies, quotes, and claims data to producer portals and embedded apps - Submit quotes, endorsements, and FNOLs from third-party tools - Bridge certified partner integrations (data, e-signature, payments) into your stack
Technical Specifications
Authentication
Username/password, SSO (SAML/OAuth 2.0), and MFA (SMS, email, TOTP) handled securely; producer and policyholder portal sessions supported
Connectivity
REST APIs gated by Duck Creek partner certification; Supergood layers a normalized REST surface over your carrier-specific endpoints
Response format
JSON normalized across PolicyCenter, BillingCenter, and ClaimCenter; native XML/JSON Duck Creek payloads remain accessible when needed
Rate limits
Tuned to your carrier's OnDemand or Active Delivery capacity and partner agreements; backoff and queueing handled by Supergood
Session management
Automatic session refresh, token rotation, and re-authentication across Policy, Billing, and Claims tenants
Data freshness
Near real-time for policy, billing, and claim transactions; scheduled syncs available for bulk reconciliation
Security
TLS 1.2+, encrypted credential storage, role- and entitlement-aware access aligned to carrier RBAC and document handling rules
Webhooks
Event-driven callbacks for policy, billing, and claim state changes where the underlying configuration supports them; polling fallbacks otherwise
Latency
Sub-second for cached reads; transactional writes follow Duck Creek workflow and approval timing
Throughput
Scales with OnDemand cloud delivery capacity; batched operations for bulk policy, billing, and claims jobs
Reliability
Retries, idempotency, and transactional safety around endorsements, payments, and FNOL submissions
Adaptation
Per-carrier Gosu and Product Designer customizations affect schema; Supergood detects configuration drift and adapts adapters as products evolve
Frequently asked questions
Yes. Supergood supports both Duck Creek OnDemand SaaS and on-prem Active Delivery deployments. We adapt to your authentication setup, network topology, and partner certifications regardless of where Policy, Billing, and Claims are hosted.
Duck Creek's low-code product models, manuscripts, Gosu rules, and Product Designer configurations mean every tenant exposes a slightly different API surface. Supergood inspects your configured endpoints and inheritance trees and normalizes responses so you can integrate once against a stable schema.
Active Delivery's continuous upgrade cadence ships platform changes more frequently than legacy on-prem releases. Supergood monitors for schema, workflow, and endpoint drift and pushes adapter updates so your integration keeps working through Duck Creek upgrades.
Yes. Many integrations (LexisNexis, CoreLogic, ISO, Hyland, e-signature, payments) sit behind certified partner programs. Supergood bridges these partner-mediated flows alongside your core Policy, Billing, and Claims data so partner-driven enrichments and transactions remain accessible from a single API.
Both. Beyond reading policies, billing, and claims, you can submit new quotes, endorsements, payments, FNOLs, and claim status updates. Supergood respects Duck Creek's multi-step state machines, approvals, and effective-dating so writes follow the same workflow rigor as native transactions.