Ellipse Gradient for Header

Guidewire Integration Guide

Guidewire integrates with enterprise systems primarily through product-specific REST APIs, with legacy SOAP, batch, file, and event-based options varying by deployment.

Guidewire integration options at a glance

Guidewire Cloud uses product-specific REST APIs as its primary integration mechanism for PolicyCenter, ClaimCenter, and BillingCenter. These APIs generally exchange JSON over HTTPS and use OAuth 2.0 bearer-token authentication with product- and scope-specific permissions. Older or self-managed InsuranceSuite deployments may also expose SOAP services, batch processing, messaging, document capabilities, or other integration-framework interfaces. Event notifications and outbound callbacks must be verified for the target product and resource. Martini can consume the relevant APIs, orchestrate scheduled or event-driven workflows, transform insurance data, apply validation and business rules, and route results to enterprise applications without relying on direct database writes.

Integration pointSupported by Guidewire?Common use casesHow Martini supports it
REST APIsYesGuidewire Cloud APIs provide product-specific access to Accounts, Policies, Jobs, Claims, Invoices, and Payments, subject to product, version, tenant, and permission configuration.Martini can consume Guidewire REST APIs from workflows, handle JSON requests and responses, apply mappings and business rules, and expose transformed results through Martini APIs.
AuthenticationYesGuidewire Cloud API access generally uses OAuth 2.0-style bearer tokens, registered clients, scopes, roles, and product-specific permissions over TLS-secured HTTPS.Martini can store environment-specific credentials in secure configuration, obtain and reuse access tokens, and separate development, test, and production settings.
SOAP APIsLegacySOAP and web-service interfaces remain relevant for some older or self-managed InsuranceSuite deployments and existing enterprise integrations.Martini can consume Guidewire SOAP services, transform XML payloads, and apply workflow-level validation and error handling where the required service contract is available.
Webhooks / outbound callbacksNot confirmedSome Guidewire deployment models use events, messaging, or outbound processing, but universal webhook coverage for Guidewire Cloud resources was not verified.Martini can receive webhook-style requests or callbacks when the target Guidewire product exposes the required mechanism; otherwise it can use scheduled API retrieval.
Bulk / async / batch APIsLimitedBatch and asynchronous processing exists in some Guidewire implementation patterns, but public bulk endpoint availability varies by product, resource, and release.Martini can process paginated API results in controlled batches, maintain checkpoints, and implement retry and reconciliation logic when a public bulk endpoint is unavailable.
File / attachment APIsLimitedDocument and attachment integration may be available through product-specific APIs or external document-management integrations, but it is not uniform across business-object APIs.Martini can retrieve or transmit content exposed by an approved API, transform metadata, and route files to downstream systems or storage.
Database / analytics accessNoDirect database integration is not the recommended Guidewire Cloud pattern and direct writes can bypass application rules and create upgrade risks.Martini should use supported APIs, approved exports, reporting interfaces, or an authorized warehouse architecture rather than writing to Guidewire application tables.
SDKs and custom integrationLimitedSelf-managed environments may use Guidewire tooling, Java components, messaging, or integration-framework interfaces around the core applications.Martini can consume the resulting REST or SOAP endpoints and orchestrate surrounding processes without requiring a dedicated Martini connector.

How Guidewire exposes data and business events

Guidewire REST APIs

Guidewire Cloud APIs are the primary integration mechanism and expose product-specific resources over HTTPS, generally using JSON. PolicyCenter, ClaimCenter, and BillingCenter have different resources, operations, schemas, and permissions.

Martini implementation pattern

Martini implementation pattern: Martini authenticates with the configured OAuth 2.0 mechanism, calls the relevant Guidewire API from a workflow, handles pagination and response status, maps the payload into a canonical or target model, and records identifiers and checkpoints.

Implementation sequence

Obtain or reuse a Guidewire access token
Call the product-specific REST resource
Process pagination and response status
Validate and transform the JSON payload
Write the result to the target system
Store identifiers and synchronization state

SOAP services

SOAP and web-service interfaces may remain available in older or self-managed InsuranceSuite architectures. They are legacy options for existing contracts or capabilities not exposed through the required REST API.

Martini implementation pattern

Martini implementation pattern: Martini consumes the documented SOAP contract, constructs the required XML request, invokes the service, parses the response, and routes SOAP faults or business validation errors through workflow error handling.

Implementation sequence

Load the approved SOAP service configuration
Build the XML request from the canonical model
Invoke the Guidewire SOAP operation
Parse the response or SOAP fault
Map the result to the target model
Log correlation and error details

Events and outbound notifications

Guidewire supports event, messaging, and outbound-processing patterns in some deployment models, but universal webhook coverage for Guidewire Cloud resources was not confirmed. Availability must be checked for the target product and event.

Martini implementation pattern

Martini implementation pattern: when a supported callback or notification exists, Martini receives the request through an API or webhook endpoint, validates its source and payload, retrieves current Guidewire data if necessary, and processes the event idempotently. If no event is available, a scheduled REST synchronization is used instead.

Implementation sequence

Receive the supported notification or callback
Validate authentication and event context
Retrieve the current Guidewire resource if required
Check the event or resource correlation key
Apply business rules and mapping
Acknowledge or record the processing result

Scheduled and batch synchronization

Batch and asynchronous processing varies by product, release, and deployment. Guidewire APIs may require paginated retrieval and controlled processing rather than a universal public bulk endpoint.

Martini implementation pattern

Martini implementation pattern: a scheduler starts a workflow that retrieves changed objects using supported filters, timestamps, statuses, or identifiers, processes pages in bounded batches, persists a checkpoint, and retries transient failures without duplicating business transactions.

Implementation sequence

Start the scheduled synchronization workflow
Load the last successful checkpoint
Retrieve the next filtered page
Map and validate each object
Write results and update processing state
Persist the checkpoint after successful completion

Common Guidewire integration patterns

Pattern 1: Synchronize CRM accounts and policy submissions

When to use this pattern

Use this pattern when Salesforce or another customer-facing application needs to create or update Guidewire customer information and initiate policy transactions. The flow should distinguish an Account update from a Job or Policy operation because Guidewire transactions may require ordered business steps.

Integration direction
Salesforce
Martini
Guidewire PolicyCenter
Example Mapping
Guidewire FieldCanonical FieldTarget Field
externalAccountIdcustomer.externalIdAccount external identifier
legalNamecustomer.nameAccount name
submissionTypepolicyTransaction.typeJob transaction type
effectiveDatepolicy.effectiveDatePolicy effective date
Martini implementation pattern

Martini receives a Salesforce request or scheduled change, validates required customer and submission fields, searches Guidewire for an existing Account, and creates or updates it before invoking the appropriate PolicyCenter Job operation. It applies product-specific business rules, returns Guidewire identifiers to Salesforce, and routes authorization, validation, conflict, and transient API failures separately.

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

Pattern 2: Reconcile BillingCenter invoices and payments

When to use this pattern

Use this pattern when finance or payment platforms require reliable BillingCenter Invoice and Payment data. It is suitable for scheduled incremental processing where duplicate postings, reversals, currency, and reconciliation status must be controlled.

Integration direction
Guidewire BillingCenter
Martini
SAP S/4HANA
Example Mapping
Guidewire FieldCanonical FieldTarget Field
invoiceNumberbilling.documentIdAccounting document reference
amountDuebilling.amountOpen amount
paymentStatusbilling.transactionStatusPayment status
currencybilling.currencyCodeTransaction currency
Martini implementation pattern

A scheduled Martini workflow retrieves changed Invoices and Payments through paginated BillingCenter APIs, maps monetary values and identifiers, checks integration state before posting, and sends approved transactions to SAP S/4HANA. It records acknowledgements, retries transient failures with backoff, and routes conflicts or reconciliation mismatches for review.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • pagination handling
  • data transformation
  • idempotency rules
  • retry and error handling

Pattern 3: Expose controlled claim information to customer service

When to use this pattern

Use this pattern when a portal, ServiceNow process, or customer-service application needs selected ClaimCenter information without exposing internal Guidewire structures directly. It supports controlled read access and authorized updates where the relevant API operations exist.

Integration direction
ServiceNow
Martini
Guidewire ClaimCenter
Example Mapping
Guidewire FieldCanonical FieldTarget Field
claimNumberclaim.referenceCase or request reference
claimStatusclaim.statusCase status
lossDateclaim.lossDateIncident date
assignedAdjusterclaim.ownerAssigned agent
Martini implementation pattern

Martini exposes a controlled API façade, authenticates and authorizes the caller, retrieves the required ClaimCenter resource, filters sensitive fields, and transforms the response into a stable service model. It applies correlation and duplicate checks for updates, while returning meaningful validation or authorization errors to the calling application.

Martini capabilities used
  • API exposure
  • API consumption
  • authorization
  • data mapping
  • field filtering
  • error handling

Pattern 4: Synchronize Guidewire data to an analytics platform

When to use this pattern

Use this pattern when policy, claim, account, billing, or payment data must be loaded into Snowflake or another approved reporting platform. It is appropriate for incremental synchronization where product-specific schemas and status changes must be normalized.

Integration direction
Guidewire
Martini
Snowflake
Example Mapping
Guidewire FieldCanonical FieldTarget Field
idsource.objectIdGuidewire source ID
updatedDatesource.modifiedAtLast modified timestamp
statusbusiness.statusNormalized status
policyNumberpolicy.numberPolicy number
Martini implementation pattern

Martini runs a scheduled workflow, retrieves each supported object through APIs or approved exports, normalizes product-specific fields, handles cancellations and reversals, and loads the result into the analytics ingestion process. A durable checkpoint, source identifier, and processing outcome support restart, reconciliation, and duplicate prevention.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • pagination
  • data mapping
  • checkpoint management
  • monitoring and error handling

Applications commonly integrated with Guidewire

Guidewire implementations commonly exchange insurance, financial, operational, and document data with adjacent enterprise applications. The exact direction and interface depend on the insurer’s products, deployment model, API configuration, and business processes.

Application Scenario Direction Martini Pattern
Salesforce Synchronize customer, opportunity, submission, policy, and claim-service information between CRM users and Guidewire. Salesforce → Martini → Guidewire Martini can receive Salesforce-originated requests or scheduled data, look up Guidewire Accounts by an external identifier, map submission data, and call the relevant PolicyCenter REST API. Policy and claim status can then be transformed and returned to Salesforce.
SAP S/4HANA Exchange BillingCenter invoices, payments, commissions, accounting data, and reconciliation results with enterprise finance processes. Guidewire → Martini → SAP S/4HANA A scheduled Martini workflow can retrieve paginated BillingCenter Invoices and Payments, normalize monetary values and identifiers, apply idempotency checks, and post approved transactions to SAP S/4HANA while recording reconciliation outcomes.
ServiceNow Coordinate operational requests, incidents, application support, and status information related to Guidewire environments. ServiceNow → Martini → Guidewire Martini can expose or consume controlled APIs that translate ServiceNow requests into approved Guidewire queries or operational workflows, apply authorization rules, and return stable status responses to ServiceNow.
Workday Exchange selected worker, organization, or finance-related information where corporate administration interacts with insurance operations. Workday → Martini → Guidewire Martini can orchestrate scheduled Workday extracts and Guidewire API calls, validate organizational identifiers, map only approved fields, and route the result to downstream enterprise processes.
Snowflake Consolidate policy, claim, billing, and operational data for analytics, actuarial reporting, and enterprise data products. Guidewire → Martini → Snowflake A scheduled Martini workflow can retrieve changed Guidewire objects through supported APIs or approved exports, normalize product-specific payloads, maintain checkpoints, and load curated data into Snowflake through the selected data-ingestion interface.
AWS S3 Store exported files, documents, reports, or staged integration data associated with Guidewire workflows. Guidewire → Martini → AWS S3 Martini can receive or retrieve document and export content when the Guidewire implementation exposes it, validate metadata, and route files or staged payloads to AWS S3 while preserving source identifiers and processing status.
DocuSign Support electronic signature processes for applications, policy documents, and customer communications. Guidewire → Martini → DocuSign Martini can transform an approved Guidewire policy or document request into a DocuSign workflow, retain correlation identifiers, and return signing status to the relevant policy process when the required document interfaces are available.
Duck Creek Support data migration, coexistence, or comparative transformation between insurance platforms during modernization or portfolio transitions. Guidewire → Martini → Duck Creek Martini can process controlled batch extracts from both platforms, map policy and claim models to a canonical structure, validate cross-system identifiers, and route exceptions for reconciliation during migration or coexistence.

How to build a Guidewire integration in Martini

Objective

Establish the Guidewire environment, product, API version, authentication flow, and permissions before implementing business logic.

Instructions in Martini

  • Record the target PolicyCenter, ClaimCenter, or BillingCenter environment and API version.
  • Register the integration client and confirm OAuth 2.0 scopes, roles, and permissions.
  • Store client credentials and environment settings in secure Martini configuration.
  • Test read and write authorization separately where both operations are required.

Objective

Select an event, callback, API request, or scheduled trigger based on what the target Guidewire deployment actually exposes.

Instructions in Martini

  • Verify whether the required product and resource provide an event or outbound callback.
  • Use a Martini API or webhook endpoint for supported inbound requests.
  • Use a scheduler when event coverage is unavailable or incomplete.
  • Define the frequency, concurrency, and checkpoint strategy for polling.

Objective

Consume the relevant Guidewire resource while respecting product-specific filtering, pagination, and transaction semantics.

Instructions in Martini

  • Call the documented REST resource or approved SOAP service.
  • Process response pages rather than assuming a collection fits in one response.
  • Use supported timestamps, statuses, identifiers, or filters for incremental retrieval.
  • Capture Guidewire identifiers, response status, and correlation information.

Objective

Coordinate calls, validations, lookups, transformations, target writes, and compensating or error paths in a maintainable Martini workflow.

Instructions in Martini

  • Separate Account, Policy, Job, Claim, Invoice, and Payment logic where their business rules differ.
  • Use conditional routing for validation, authorization, conflict, and transient failures.
  • Keep reusable transformations and service logic separate from product-specific orchestration.
  • Define the sequence required for multi-step insurance transactions.

Objective

Translate Guidewire payloads into a canonical or target model while preserving insurance-specific dates, money, statuses, and identifiers.

Instructions in Martini

  • Map standard and configured extension fields deliberately.
  • Validate required fields, enumerations, effective dates, currency, and decimal precision.
  • Distinguish null, omitted, cancelled, reversed, and corrected values.
  • Retain source identifiers for traceability and idempotency.

Objective

Send validated data to downstream applications, APIs, files, or approved data platforms without creating duplicate business transactions.

Instructions in Martini

  • Use lookup-before-create or stable external identifiers where appropriate.
  • Apply idempotency controls before posting Invoices, Payments, Policies, or other transactions.
  • Record target acknowledgements and Guidewire correlation identifiers.
  • Use approved APIs or export mechanisms rather than direct Guidewire database writes.

Common Guidewire data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
AccountRepresents a customer, organization, or policyholder account used across customer and policy processes.Salesforce, customer-service platforms, data warehouses, and billing systemsMartini can search by an external identifier, create or update the Account through the relevant product API, validate required party data, and retain the Guidewire identifier.
PolicyRepresents an insurance policy, including coverage, terms, status, and related parties.Salesforce, portals, data warehouses, reporting platforms, and downstream servicing systemsMartini maps policy attributes and effective dates, handles status and cancellation changes explicitly, and routes product-specific payloads to target systems.
JobRepresents a policy transaction such as a submission, quote, renewal, rewrite, cancellation, or change.Salesforce, underwriting applications, portals, and operational workflow systemsMartini orchestrates required transaction steps, validates dependencies, correlates external identifiers, and handles business validation errors separately from transient failures.
ClaimRepresents an insurance claim with loss information, parties, activities, exposures, and payments, primarily in ClaimCenter.Customer-service applications, portals, data warehouses, notification platforms, and finance systemsMartini can expose controlled claim queries, synchronize changes, apply authorization and field filtering, and preserve claim correlation identifiers.
InvoiceRepresents a billing document or amount due, primarily associated with BillingCenter.SAP S/4HANA, accounting platforms, payment services, customer portals, and data warehousesMartini retrieves invoices incrementally, maps monetary and status fields, applies duplicate checks, and routes posting or notification results.
PaymentRepresents a payment or payment transaction associated with billing activity.Payment processors, SAP S/4HANA, accounting platforms, reconciliation systems, and reporting storesMartini correlates payment and invoice identifiers, handles reversals and corrections, applies idempotency controls, and records reconciliation outcomes.

Authentication and security considerations

OAuth 2.0 and scoped access

Guidewire Cloud API integrations generally use registered clients, OAuth 2.0-style bearer tokens, product-specific scopes, roles, and permissions. A valid token may still lack authorization for a particular resource or write operation.

Environment isolation

Use separate clients, credentials, endpoints, and permissions for development, test, and production environments. Store client secrets and tokens in secure Martini configuration rather than workflow payloads or source definitions.

Transport and data protection

  • Use TLS-secured HTTPS for Guidewire Cloud API calls.
  • Limit access to the resources and operations required by each workflow.
  • Apply caller authentication and authorization when Martini exposes a Guidewire API façade.
  • Protect claim, policy, payment, and personally identifiable information in logs and error payloads.

Operational considerations for Guidewire integrations

Product and version differences

PolicyCenter, ClaimCenter, and BillingCenter have different resources, schemas, permissions, and transaction semantics. Record the target product, release, API version, and enabled configuration as part of the integration design.

Throughput and pagination

Use the documented pagination and filtering model for each API. Apply bounded concurrency and backoff because rate limits depend on the Guidewire environment, tenant, and gateway policies.

Idempotency and checkpoints

Use stable external identifiers, supported correlation fields, lookup-before-create logic, and durable checkpoints. Retries must not automatically create duplicate Accounts, Jobs, Claims, Invoices, or Payments.

Schema and transaction changes

Test required fields, extension fields, status values, effective dates, currency precision, cancellations, reversals, and multi-step insurance transactions. Monitor for additive schema changes and changes in API permissions.

Database restrictions

Do not use direct writes to Guidewire application tables. Use supported APIs, approved exports, reporting interfaces, or authorized warehouse architectures to preserve business rules and upgrade compatibility.

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

Orchestration beyond a script

Guidewire integrations often span product-specific APIs, CRM, finance, service, document, and analytics systems. Martini coordinates these calls in workflows with explicit sequencing, conditional routing, reusable services, and environment-specific configuration.

Reliable data movement

Martini provides a structured place to implement pagination, checkpoints, mapping, validation, idempotency, retries, and error paths instead of duplicating those concerns across point-to-point scripts.

Controlled APIs and maintainability

Martini can expose stable API façades that shield consumers from product-specific Guidewire structures while allowing developers to extend transformations and business rules when required. Integration assets remain deployable, observable, and easier to test and operate than isolated scripts.

Frequently asked questions

How can Guidewire be integrated with enterprise systems?

Guidewire Cloud is primarily integrated through product-specific REST APIs for PolicyCenter, ClaimCenter, and BillingCenter, using HTTPS, JSON, and OAuth 2.0-style bearer-token authentication. Older or self-managed InsuranceSuite deployments may also use SOAP, batch, messaging, document, or event-based interfaces depending on the implementation.

Can Martini integrate with Guidewire?

Yes. Martini can consume Guidewire REST APIs and legacy SOAP services, receive supported webhook or callback requests, expose APIs for controlled access, and run scheduled workflows for synchronization. The exact resources, events, and permissions must be verified for the target Guidewire product and release.

Do I need a connector to integrate Guidewire with Martini?

No. A dedicated Guidewire connector is not required. Martini can use Guidewire’s confirmed native integration mechanisms, including REST APIs, applicable SOAP services, supported callbacks, authentication methods, and scheduled API access.

Is there any extra Lonti cost to integrate Guidewire with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Guidewire. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Guidewire, cloud infrastructure, document platforms, payment providers, or other third-party systems.

Should a new Guidewire integration use REST or SOAP?

REST should generally be evaluated first for Guidewire Cloud because Cloud APIs are the primary integration mechanism. SOAP may remain appropriate for an existing self-managed InsuranceSuite integration or for a capability not exposed through the relevant REST API.

Can Martini receive Guidewire events or synchronize data on a schedule?

Martini can receive Guidewire notifications or callbacks when the target product and deployment expose the required mechanism, but universal webhook coverage is not confirmed. When events are unavailable, scheduled workflows can retrieve paginated data using supported filters, timestamps, statuses, or identifiers.

How does Martini handle Guidewire data mapping, errors, and duplicate transactions?

Martini can map product-specific JSON or XML payloads into canonical models, validate required fields, apply business rules, and route results to target systems. Workflows can distinguish authorization, validation, conflict, rate-limit, and transient failures, use backoff and retries, and apply stable identifiers, checkpoints, and idempotency controls to reduce duplicates.

Can Martini expose an API façade for Guidewire data?

Yes. Martini can expose a controlled API that retrieves selected PolicyCenter, ClaimCenter, or BillingCenter data, applies authorization and field filtering, transforms responses into a stable external model, and shields consumers from product-specific Guidewire structures. The underlying Guidewire resources and permissions must be available.

Related Martini documentation

Guidewire APIs

Workflows

Data Processing

Security

Operations

Build a maintainable Guidewire integration with Martini

Use Martini to connect Guidewire APIs and approved legacy interfaces with the applications, data platforms, and workflows that support your insurance operations.

EXPLORE MARTINI
BOOK A DEMO