Duck Creek API
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. This page is an independent design exercise that asks what a well-designed Duck Creek API could look like: the resources it would expose, the authentication it would need, and the workflows it could unlock. Below: a hypothetical endpoint design, the technical requirements a production implementation would face, the use cases programmatic access could serve, and where to start if your team needs this kind of access today.
This page is an independent analysis by Supergood of what a well-designed Duck Creek API could look like. It draws on publicly available information, vendor materials, and general integration experience in this category. Nothing on this page describes an existing Duck Creek product, and Supergood is not affiliated with or endorsed by the vendor. If the vendor offers an official API, we highly recommend it.
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
An API for a platform like this would naturally organize around its core 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: 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
What a Duck Creek API Could Look Like
If Duck Creek exposed a modern, general-purpose API, the integration challenges above suggest what it would need to get right. This is a design sketch, not documentation of anything that exists today:
- First-class authentication: session handling with support for MFA and enterprise sign-on where the platform uses them
- Consistent resources: normalized JSON schemas and pagination across the platform's core objects
- Reliable writes: idempotency keys and validation that mirrors the platform's own workflow rules
- Entitlement awareness: endpoints scoped to what each customer's licensing actually permits
The endpoint sketches, technical requirements, and use cases below flesh out this hypothetical design.
How AI agents could connect to software like Duck Creek: MCP servers for software without a public API →
Need This Kind of Access Today?
If your team needs this kind of access today, Supergood builds integrations on request, one customer at a time. We act at the direction of our customers, within the access they already hold. Customers bring their own accounts, licenses, and entitlements. If the vendor offers an official API, we highly recommend it.
- Schedule an Integration Assessment
A 30-minute session to review your product mix, licensing, and authentication model. - Scope the Integration
We design the access pattern around your workflows and entitlements. - Deploy with Monitoring
Go live with continuous monitoring as your platforms evolve.
Potential API Endpoints
Authentication
/authenticateWould authenticate with Duck Creek using username/password or MFA and obtain a session token
Policies
/policiesWould list policies with terms, coverages, exposures, and forms across PolicyCenter
Policies
/create_policyWould submit a new quote or bind a policy with insureds, locations, and rating inputs
Claims
/claimsWould retrieve 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
/billingWould pull 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
Connect via No-Code Tools
Automate this platform from the no-code stack you already use.
Technical Requirements
Authentication
Would require username/password and MFA (SMS, email, TOTP) handled securely; producer and policyholder portal sessions supported
Connectivity
Would build on REST APIs gated by Duck Creek partner certification;
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;
Session management
Would need 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
Design target: sub-second for cached reads; transactional writes follow Duck Creek workflow and approval timing
Throughput
Design target: 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
Versioning
Clear versioning and change management would matter as Duck Creek evolves
Frequently asked questions
Availability of official interfaces varies by product, plan, and licensing. Many platforms in this category gate access behind partner programs or paid modules, and there is often no broadly available, self-serve public API. Check the vendor's developer resources for current offerings.
The hard parts would be authentication (MFA, session management, enterprise controls), consistent schemas across the platform's products, and write semantics that reconcile the way the platform's own workflows do.
No. This page is an independent analysis by Supergood and is not affiliated with, sponsored by, or endorsed by the vendor. All product names and trademarks belong to their respective owners and are used for identification only. Nothing here documents an actual Duck Creek product or service.
Supergood acts at the direction of its customers, within the access those customers already have. We respect each customer's agreements with their software vendors, and how those agreements apply to a customer's use is a determination the customer makes. If the vendor offers an official API, we highly recommend it.
Supergood builds managed API access to enterprise software for customers on request, scoped to each customer's own licensing and entitlements. If your team needs programmatic access to a platform like this, schedule an integration assessment to discuss options.