Ellipse Gradient for Header

Duck Creek Integration Guide

Integrate Duck Creek insurance operations with enterprise applications through product-specific REST APIs, selected callbacks, file interfaces, and orchestrated workflows.

Duck Creek integration options at a glance

Duck Creek integration is centered on Duck Creek Anywhere and product-specific APIs for Policy, Billing, Claims, Rating, Distribution, and related insurance operations. REST is the preferred standards-based mechanism when the required resources are exposed. Selected products or deployments may also provide callback or event notifications, batch-oriented processing, file exchange, or document endpoints, but these capabilities must be confirmed for the tenant. Modern deployments may use OAuth-style or token-based authentication over HTTPS. Martini can consume these interfaces, externalize credentials, map insurance objects, orchestrate workflows, expose APIs, and coordinate retries, validation, and reconciliation.

Integration pointSupported by Duck Creek?Common use casesHow Martini supports it
REST APIsLimitedDuck Creek Anywhere and product-specific APIs can expose Policy, Billing, Claims, Rating, Distribution, and related resources. Exact operations and resource models depend on the product, release, tenant, and implementation.Martini can consume Duck Creek REST APIs from workflows, map responses to canonical models, expose orchestration APIs, and apply validation, routing, retries, and reconciliation.
Webhooks and outbound callbacksLimitedSelected products, resources, or customer deployments may provide event notifications or callbacks, but a universal webhook model for all policy, billing, and claims events was not confirmed.Martini can receive a confirmed Duck Creek callback through a webhook-triggered workflow, retrieve the current resource when needed, and route the event to downstream systems.
Bulk, asynchronous, and batch processingLimitedPortfolio, billing, claims, and migration workloads may use product-specific bulk endpoints, asynchronous services, scheduled polling, file exchange, or customer-provided integration services.Martini can orchestrate scheduled or asynchronous workflows, process pages or files in controlled batches, persist checkpoints, and route failed items for reconciliation.
File and attachment APIsLimitedPolicy documents, claim attachments, declarations, and correspondence may be available through product-specific document endpoints or managed file exchange.Martini can coordinate document metadata and binary transfers when supported, apply content and security rules, and connect file workflows to downstream applications.
AuthenticationLimitedModern Duck Creek API deployments may use OAuth-style or token-based authentication, client credentials, scopes, and HTTPS/TLS, with exact configuration managed by the tenant or API gateway.Martini can externalize endpoints, tokens, client credentials, and scopes through secure environment configuration and secrets management rather than embedding them in workflows.
SOAP APIsNot confirmedOlder or implementation-specific Duck Creek enterprise interfaces may expose SOAP, but a current universal SOAP API was not confirmed and REST should be preferred for new integrations.If the customer explicitly exposes a supported SOAP service, Martini can consume it using SOAP integration capabilities; the service contract and authentication must be verified first.
Database and analytics accessNot confirmedDirect access to Duck Creek production databases is not a confirmed standard integration boundary. Managed exports or supported APIs should be preferred for reporting and analytics.Martini can consume supported exports or APIs and load target data platforms, but should not assume direct access to Duck Creek internal databases.

How Duck Creek exposes data and business events

Duck Creek REST APIs

Duck Creek promotes API-based integration through Duck Creek Anywhere and product-specific APIs. REST is the most relevant integration method for exposed Policy, Billing, Claims, Rating, Distribution, and related resources, although the exact resource model and operations vary by product and tenant.

Martini implementation pattern

Martini implementation pattern: Martini workflows authenticate using tenant-specific configuration, retrieve or submit Duck Creek resources, validate insurance lifecycle fields, map payloads to canonical or target-system models, and persist correlation and checkpoint information for repeatable processing.

Implementation sequence

Authenticate against the configured Duck Creek API gateway
Receive a request or retrieve a resource from the Duck Creek REST API
Validate identifiers, transaction types, dates, and required fields
Map the Duck Creek payload to the target application model
Apply business rules for routing, status, and idempotency
Write the result to the target system and persist correlation data

Duck Creek callbacks

Selected Duck Creek products or customer deployments may provide event notifications or outbound callbacks. Public information does not confirm a universal webhook model across all policy, billing, and claims events, so availability must be verified for the target environment.

Martini implementation pattern

Martini implementation pattern: Martini exposes a controlled webhook endpoint, accepts only confirmed event formats, validates signatures or tokens when provided, retrieves the current Duck Creek resource when necessary, and routes the event through an idempotent workflow.

Implementation sequence

Receive the confirmed Duck Creek callback
Authenticate and validate the callback payload
Resolve the affected policy, claim, account, or billing identifier
Retrieve the current resource when the callback is notification-only
Map and route the current state to downstream systems
Acknowledge the callback and record processing status

Duck Creek batch processing

Insurance portfolios, billing transactions, claims updates, and migration workloads may require batch or asynchronous processing. A single public bulk API was not confirmed; implementations may use product-specific endpoints, scheduled polling, file exchange, or customer-provided services.

Martini implementation pattern

Martini implementation pattern: A scheduled or externally triggered workflow retrieves pages, files, or asynchronous results, processes items with bounded concurrency, stores checkpoints, and sends failures to reconciliation rather than repeating an entire batch.

Implementation sequence

Start the scheduled or externally triggered batch workflow
Retrieve the next page, file, or asynchronous result set
Validate and transform each insurance object
Apply idempotency and business validation rules
Write successful items to the target system
Store the checkpoint and route failed items for reconciliation

Duck Creek documents and attachments

Policy documents, claim attachments, declarations, and correspondence may be exposed through product-specific document endpoints or managed file exchange. A universal file or attachment API was not confirmed across Duck Creek products.

Martini implementation pattern

Martini implementation pattern: Martini coordinates document metadata and content references, transfers binary content only through approved endpoints, avoids sensitive logging, and correlates document IDs with policy, claim, submission, or envelope identifiers.

Implementation sequence

Receive document metadata or identify the document to retrieve
Authenticate to the confirmed document or file interface
Retrieve or submit content using the supported transfer method
Validate document identifiers, type, size, and destination
Write metadata and content to the target document service
Record the document correlation and processing outcome

Common Duck Creek integration patterns

Pattern 1: Synchronize submissions, quotes, and policies with Salesforce

When to use this pattern

Use this pattern when sales or distribution teams manage opportunities in Salesforce while Duck Creek handles submission, rating, quote, and policy processes. It supports bidirectional status synchronization while preserving insurance transaction semantics.

Integration direction
Salesforce
Martini
Duck Creek
Example Mapping
Duck Creek FieldCanonical FieldTarget Field
externalSubmissionIdsubmission.sourceReferenceSalesforce Opportunity ID
insuredNameaccount.nameSalesforce Account Name
quotePremiumquote.totalPremiumSalesforce Quote Premium
policyStatuspolicy.lifecycleStatusSalesforce Policy Status
Martini implementation pattern

A Martini API or workflow receives a Salesforce submission, validates required underwriting fields, maps it to the Duck Creek Submission or Quote model, and calls the available product API. The response is normalized and written back to Salesforce. Business rules distinguish quote, bind, renewal, endorsement, and cancellation states; external IDs prevent duplicate submissions, while transient failures use controlled retries and permanent validation failures are routed for review.

Martini capabilities used
  • workflows
  • API consumption
  • API exposure
  • data mapping
  • business rules
  • error handling

Pattern 2: Coordinate claims intake with ServiceNow

When to use this pattern

Use this pattern when ServiceNow manages service requests or operational cases and Duck Creek Claims manages claim creation and lifecycle data. It is suitable for claim intake, status synchronization, assignment updates, and resolution reporting.

Integration direction
ServiceNow
Martini
Duck Creek
Example Mapping
Duck Creek FieldCanonical FieldTarget Field
claimReferenceclaim.externalReferenceServiceNow Case Number
lossDateclaim.lossDateServiceNow Loss Date
claimStatusclaim.lifecycleStatusServiceNow Case State
claimNumberclaim.claimNumberServiceNow Claim Number
Martini implementation pattern

Martini validates a ServiceNow request, calls the confirmed Duck Creek Claims API, and returns the claim number and initial state. Later updates are driven by a confirmed callback or scheduled polling. The workflow preserves claim references and correlation IDs, rejects invalid lifecycle transitions, and uses idempotent create-or-update behavior so retries cannot create duplicate claims.

Martini capabilities used
  • workflows
  • API consumption
  • data mapping
  • validation
  • business rules
  • error handling

Pattern 3: Orchestrate billing payments with Stripe

When to use this pattern

Use this pattern when Duck Creek Billing is the system of record for billing transactions but Stripe processes authorized payment requests. It supports payment initiation, outcome updates, and controlled exception handling.

Integration direction
Duck Creek
Martini
Stripe
Example Mapping
Duck Creek FieldCanonical FieldTarget Field
billingAccountIdbillingAccount.identifierStripe Customer ID
paymentAmountpayment.amountStripe Payment Amount
currencyCodepayment.currencyStripe Currency
paymentReferencepayment.externalReferenceStripe Idempotency Reference
Martini implementation pattern

A Martini workflow receives an eligible billing transaction, validates amount and currency, submits the payment to Stripe, and maps the outcome back to Duck Creek Billing. Payment references are retained across retries, uncertain results are reconciled before another attempt, and failures are routed according to business rules rather than blindly retried.

Martini capabilities used
  • workflows
  • API consumption
  • data mapping
  • business rules
  • idempotency handling
  • error handling

Pattern 4: Distribute policy documents through DocuSign

When to use this pattern

Use this pattern when policy-related documents need signing or controlled customer distribution. It depends on the Duck Creek product exposing document metadata, content, or a supported file exchange mechanism.

Integration direction
Duck Creek
Martini
DocuSign
Example Mapping
Duck Creek FieldCanonical FieldTarget Field
policyNumberpolicy.identifierDocuSign Envelope Custom Field
documentReferencedocument.sourceReferenceDocuSign Document Reference
insuredEmailparty.emailDocuSign Recipient Email
envelopeStatussignature.lifecycleStatusDuck Creek Document Status
Martini implementation pattern

Martini retrieves or receives approved Duck Creek document references, creates a DocuSign envelope, and correlates envelope status back to the policy or submission. The workflow validates document type and recipient details, protects sensitive content from logs, and handles callback or polling failures with retry and reconciliation controls.

Martini capabilities used
  • workflows
  • API consumption
  • data mapping
  • file and document handling
  • business rules
  • error handling

Applications commonly integrated with Duck Creek

Duck Creek environments commonly participate in broader insurance, finance, customer-service, document, payment, and analytics architectures. The exact integration boundary depends on the licensed Duck Creek products, deployment, tenant configuration, and exposed APIs.

Application Scenario Direction Martini Pattern
Salesforce Synchronize opportunities, submissions, quotes, customer information, policy numbers, and lifecycle status between customer-facing sales processes and insurance operations. Salesforce → Martini → Duck Creek Martini receives a Salesforce submission or opportunity event through an API, validates and maps it to Duck Creek quote or submission resources, then synchronizes quote and policy outcomes back to Salesforce. External IDs, transaction types, and retry state are retained for idempotent updates.
ServiceNow Coordinate claims-related requests, customer-service cases, operational work, and status updates with Duck Creek Claims and policy processes. ServiceNow → Martini → Duck Creek A Martini workflow accepts a ServiceNow request, validates the claim payload, calls the relevant Duck Creek API, and returns the claim number or status. Polling or a confirmed Duck Creek callback can drive subsequent updates to ServiceNow.
DocuSign Coordinate policy documents, signing envelopes, customer correspondence, and signature status with insurance transactions. Duck Creek → Martini → DocuSign Martini retrieves document metadata or content references when the Duck Creek deployment exposes them, builds a DocuSign envelope request, and correlates signing status back to the policy or submission using document and envelope identifiers.
Stripe Coordinate payment initiation and payment outcomes between Duck Creek Billing and a payment service. Duck Creek → Martini → Stripe Martini receives an authorized billing transaction, submits the payment request to Stripe, applies payment-response rules, and updates Duck Creek Billing. Failed or uncertain outcomes are routed for controlled retry and reconciliation.
Microsoft Dynamics 365 Synchronize customer, broker, account, and policy-related information across insurance operations and relationship-management processes. Microsoft Dynamics 365 → Martini → Duck Creek Martini maps Dynamics 365 account or customer changes to Duck Creek Account and Policy-related resources, then returns policy and quote status through a controlled workflow with product-specific transformations.
SAP Coordinate finance, payment, accounting, and enterprise master-data processes with Duck Creek billing and insurance transactions. Duck Creek → Martini → SAP Martini retrieves billing or payment data from Duck Creek, transforms monetary values and transaction types into SAP structures, applies reconciliation rules, and records source identifiers for repeatable processing.
Workday Synchronize organizational or workforce information for insurers using Workday for corporate administration. Workday → Martini → Duck Creek Martini periodically retrieves approved organizational data from Workday, applies tenant-specific mapping and validation, and sends only the supported downstream information to Duck Creek or related enterprise services.
Snowflake Deliver policy, claims, and billing data to analytics, reporting, actuarial, and portfolio-analysis workloads. Duck Creek → Martini → Snowflake Martini retrieves supported Duck Creek API or managed-export data in pages or batches, normalizes policy, claim, and billing structures, and loads Snowflake with checkpoints, reconciliation keys, and controlled retry handling.

How to build a Duck Creek integration in Martini

Objective

Establish the Duck Creek endpoint, product scope, environment configuration, and authentication method before building mappings.

Instructions in Martini

  • Confirm the Duck Creek product, version, tenant, API base URL, and exposed resources.
  • Configure OAuth-style or token-based credentials through secure environment configuration when supported.
  • Store client credentials, tokens, scopes, and endpoint values in secrets rather than workflow logic.
  • Confirm TLS, gateway permissions, API quotas, and required downstream credentials.

Objective

Select the event, API request, schedule, polling process, or file exchange that starts the integration.

Instructions in Martini

  • Use a Martini API when another application submits a policy, claim, quote, or payment request.
  • Use a confirmed Duck Creek callback only for events supported by the target deployment.
  • Use scheduled polling or batch processing when callbacks are unavailable.
  • Define the polling filter, page strategy, schedule, and checkpoint key.

Objective

Receive the source payload or retrieve the current Duck Creek resource needed for reliable processing.

Instructions in Martini

  • Retrieve the current Policy, Claim, Account, Quote, Submission, or Billing Account when a notification contains only an identifier.
  • Implement the confirmed pagination, filtering, sorting, and incremental retrieval behavior.
  • Preserve source identifiers, transaction references, timestamps, and correlation IDs.
  • Avoid direct production database access unless a separately approved customer architecture explicitly provides it.

Objective

Coordinate API calls, branching, asynchronous processing, and target-system operations in a maintainable Martini workflow.

Instructions in Martini

  • Separate product-specific Duck Creek calls from common enterprise transformation logic.
  • Use conditional routing for quote, bind, renewal, endorsement, cancellation, payment, and claim states.
  • Control concurrency for large policy, claim, billing, or document workloads.
  • Persist checkpoints and processing status for batch or polling workflows.

Objective

Convert Duck Creek’s product-specific payloads into canonical or target application models without losing insurance semantics.

Instructions in Martini

  • Map nested insurance objects to the target model using versioned transformations.
  • Preserve policy and claim identifiers, transaction types, effective dates, statuses, currencies, and source references.
  • Normalize date-time formats, monetary precision, enumerations, and document references.
  • Use validation rules for required fields and product-specific constraints.

Objective

Protect insurance transactions from invalid lifecycle transitions, duplicate processing, and unsafe financial or contractual actions.

Instructions in Martini

  • Use external submission, policy transaction, claim, payment, document, or envelope references as idempotency keys.
  • Distinguish transient transport failures from business validation failures.
  • Require reconciliation before retrying uncertain payment or issuance outcomes.
  • Route rejected or incomplete items to an operational review path.

Common Duck Creek data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
PolicyRepresents an insurance contract and lifecycle transactions such as issuance, endorsement, renewal, cancellation, and reinstatement.Salesforce, ServiceNow, SAP, SnowflakeMartini preserves policy identifiers, transaction types, effective dates, statuses, and source references while mapping product-specific payloads to downstream models.
ClaimRepresents a reported loss and its lifecycle, including parties, coverage, payments, assignments, and status.ServiceNow, Salesforce, Snowflake, payment systemsMartini validates claim references and lifecycle states, applies idempotency keys, transforms nested claim data, and routes status or payment updates.
AccountProvides customer, insured-party, policy, or billing context associated with insurance activity.Salesforce, Microsoft Dynamics 365, SAP, SnowflakeMartini resolves source identifiers, maps account and party fields, applies data-quality rules, and synchronizes changes according to the customer’s ownership model.
QuoteRepresents a priced insurance proposal before policy issuance or binding.Salesforce, Microsoft Dynamics 365, SnowflakeMartini sends validated submission inputs to available rating or quote services, normalizes quote results, and correlates them to the originating opportunity or submission.
SubmissionRepresents an insurance opportunity or application submitted for underwriting and quotation.Salesforce, Duck Creek Rating, policy administration systemsMartini maps external submission fields, preserves external transaction IDs, applies business validation, and coordinates quote or policy progression.
Billing AccountRepresents billing arrangements, invoices, balances, and payment-related information associated with a customer or policy.Stripe, SAP, Snowflake, SalesforceMartini transforms monetary values, currency, payment references, and billing statuses, while controlling retries and reconciliation for financially significant transactions.

Authentication and security considerations

Tenant-specific authentication

Duck Creek authentication depends on the deployed product, API gateway, tenant, and customer configuration. Modern API deployments may use OAuth-style or token-based authentication, client credentials, scopes, and HTTPS/TLS, but the exact flow must be verified.

Secure Martini configuration

Martini workflows should externalize API URLs, credentials, tokens, scopes, and environment settings through secure configuration and secrets management. Credentials should not be embedded in mappings or workflow logic.

Insurance data protection

  • Use least-privilege API permissions and environment-specific endpoints.
  • Protect personally identifiable, financial, health, payment, and claims information.
  • Avoid logging policy documents, claim attachments, payment data, and sensitive payloads unnecessarily.
  • Confirm gateway authorization, callback validation, retention, and audit requirements with the Duck Creek implementation team.

Operational considerations for Duck Creek integrations

Product and tenant variation

Resource names, nested structures, required fields, authentication, and operations vary across Duck Creek products, releases, hosting models, and customer configurations. Confirm the target API contract before implementation.

Pagination, limits, and batching

Confirm page size, cursor or offset behavior, filtering, sorting, incremental fields, quotas, burst limits, concurrency restrictions, and maintenance windows. Use controlled concurrency and backoff rather than immediate repeated retries.

Idempotency and reconciliation

Protect policy issuance, claim creation, billing, payment, and document operations with stable business keys and source-system identifiers. Reconcile uncertain outcomes before repeating financially or contractually significant requests.

Schema and lifecycle changes

Version mappings and isolate product-specific transformations from common models. Preserve transaction type, effective date, status, currency, precision, and source references across quote, bind, renewal, endorsement, cancellation, claim, and payment lifecycles.

Testing

Test representative Policy, Claim, Account, Quote, Submission, and Billing Account payloads in each environment, including validation failures, pagination, callbacks, retries, duplicate messages, document transfers, and schema changes.

Why use Martini instead of scripts or point-to-point integrations?

Centralized orchestration

Martini provides a workflow layer between Duck Creek and enterprise applications, avoiding duplicated point-to-point logic for authentication, validation, mapping, routing, retries, and reconciliation.

Adaptable integration boundary

Because Duck Creek interfaces vary by product and tenant, Martini can consume the APIs and services actually exposed by the customer environment while keeping product-specific transformations separate from common enterprise models.

Reusable APIs and workflows

Martini can expose controlled APIs for submissions, claims, billing, or document operations and can reuse workflow logic across Salesforce, ServiceNow, payment, document, finance, and analytics processes.

Operational control

Centralized error handling, checkpoints, correlation identifiers, controlled retries, and monitoring make long-running insurance synchronization easier to troubleshoot and reconcile than isolated scripts.

Frequently asked questions

How can Duck Creek be integrated with enterprise systems?

Duck Creek can be integrated through Duck Creek Anywhere and product-specific REST APIs for Policy, Billing, Claims, Rating, Distribution, and related operations. Depending on the deployment, integrations may also use selected callbacks, batch or asynchronous services, managed file exchange, document endpoints, or customer-provided enterprise services. The available resources, authentication flow, and operations must be confirmed for the target product and tenant.

Can Martini integrate with Duck Creek?

Yes. Martini can integrate with Duck Creek by consuming its exposed REST APIs, receiving confirmed callbacks, coordinating product-specific batch or file interfaces, and transforming insurance objects for systems such as Salesforce, ServiceNow, payment services, document platforms, and analytics stores. A native Martini Duck Creek connector was not documented in the supplied research.

Do I need a connector to integrate Duck Creek with Martini?

No. A dedicated Duck Creek connector is not required. Martini can use Duck Creek’s confirmed native integration mechanisms, including product-specific REST APIs, available callbacks, file or document interfaces, and explicitly supported services, with authentication and endpoint details externalized through secure configuration.

Is there any extra Lonti cost to integrate Duck Creek with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Duck Creek with Martini. Integrations are subject to the provisioned capacity of the Martini environment. Separate costs may apply from Duck Creek, infrastructure providers, payment or document services, or other third parties depending on subscriptions, usage, and deployment model.

Which Duck Creek integration method should new implementations use?

REST APIs exposed through Duck Creek Anywhere or the relevant product API are the preferred starting point where the required resources are available. Callbacks, batch services, asynchronous processing, file exchange, or document endpoints may supplement REST for specific products or deployments. SOAP should be considered only when the customer explicitly exposes and supports a required legacy service.

Does Duck Creek provide webhooks or callbacks for insurance events?

Callback or event support may be available for selected products, resources, or event types, but universal webhook coverage across policy, billing, and claims events was not confirmed. Martini can receive a confirmed callback through a webhook-triggered workflow. If callbacks are unavailable, scheduled polling or batch synchronization can be used where the relevant API supports it.

How does Martini synchronize Duck Creek data and handle mapping?

Martini can retrieve or receive Duck Creek Policies, Claims, Accounts, Quotes, Submissions, and Billing Accounts, then map them to canonical or target-system models. Workflows can handle pagination, incremental retrieval, lifecycle rules, date and monetary normalization, source identifiers, checkpoints, and bidirectional status updates.

How are errors, retries, and duplicate transactions handled?

Martini workflows can distinguish transient transport errors from business validation failures, retry with controlled backoff, and route unresolved items for reconciliation. Idempotency should use external submission IDs, policy transaction references, claim numbers, payment references, or document and envelope IDs. Financial, policy issuance, and claim creation operations require reconciliation before repeating uncertain requests.

Related Martini documentation

APIs

Workflows

Data

Security

Operations

Connect Duck Creek with your enterprise systems

Use Martini to orchestrate Duck Creek APIs, callbacks, files, and insurance data workflows across your enterprise environment.

EXPLORE MARTINI
BOOK A DEMO