Guidewire API
Guidewire is the property and casualty (P&C) insurance core systems platform used by 570+ insurers in 40 countries to run policy administration, billing, and claims. This page is an independent design exercise that asks what a well-designed Guidewire 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 Guidewire 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 Guidewire 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 Guidewire?
Guidewire is the property and casualty (P&C) insurance core systems platform used by 570+ insurers in 40 countries to run policy administration, billing, and claims. Its flagship offering, InsuranceSuite, bundles PolicyCenter, ClaimCenter, BillingCenter, PricingCenter, and UnderwritingCenter as a set of core applications available individually or together. InsuranceNow provides an all-in-one cloud option for carriers that want a single integrated stack, while the Guidewire Marketplace and PartnerConnect program ecosystem extend the platform through 175+ partner applications and tens of thousands of trained implementation consultants.
Core product areas include:
- PolicyCenter (Submissions, Quotes, Policies, Endorsements, Renewals, Cancellations)
- ClaimCenter (Claims, FNOL, Exposures, Coverages, Reserves, Payments, Notes)
- BillingCenter (Billing Accounts, Invoices, Charges, Disbursements, Commissions)
- PricingCenter & UnderwritingCenter (Rating, Risk Assessment, Underwriting Workflows)
- InsuranceNow (All-in-one cloud platform for policy, billing, and claims)
- Guidewire Cloud, Data Platform, and Jutro Digital Platform (hosting, analytics, and digital experience)
An API for a platform like this would naturally organize around its core data entities:
- Policies (terms, periods, coverages, endorsements, premiums)
- Submissions & Quotes (lines of business, risks, rated premium, status)
- Claims (loss details, exposures, reserves, payments, recoveries, notes)
- Contacts (insureds, claimants, agents, vendors, payees)
- Billing Accounts, Invoices, Charges, and Disbursements
- Products & Risk Definitions (lines, coverages, rate tables, forms)
- Documents & Attachments (policy forms, loss reports, correspondence)
The Guidewire Integration Challenge
P&C carriers depend on Guidewire to run the business, but turning portal- and Cloud API-based workflows into reliable API automation is non-trivial:
- Cloud API access gates: Guidewire Cloud API is reserved for partners and customers; access is mediated through PartnerConnect and Marketplace certification rather than open self-serve credentials
- Carrier-specific customization: Product Designer, Gosu rules, and PCF screens vary by carrier; submissions, claims, and billing flows differ across InsuranceSuite implementations
- Data integration handler complexity: Inbound and outbound integrations rely on plugin handlers, message destinations, and event-driven hooks that need careful authoring per carrier
- Cross-app coordination: Submission-to-policy-to-billing-to-claim flows span PolicyCenter, BillingCenter, and ClaimCenter, each with its own data model and lifecycle states
- Authentication complexity: into the carrier IdP, MFA, and Cloud API client credentials all govern headless access
- On-prem vs. Guidewire Cloud variability: Older self-hosted InsuranceSuite installs use SOAP plugins and proprietary integration patterns, while newer Cloud tenants expose REST-based Cloud APIs with different shapes
- Document and forms handling: Policy declarations, loss documents, and correspondence require careful attachment, redaction, and audit handling
What a Guidewire API Could Look Like
If Guidewire 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 Guidewire: 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
/authenticateWould establish an authenticated session using carrier MFA, or Cloud API client credentials.
/policiesWould list policies from PolicyCenter with terms, periods, coverages, endorsements, and premiums.
/create_policyWould create submissions and bind policies in PolicyCenter, including risks, coverages, and rated premium.
/claimsWould retrieve claims from ClaimCenter with exposures, reserves, payments, recoveries, and notes.
/file_claimFile First Notice of Loss into ClaimCenter and create associated exposures and initial reserves.
/billingWould pull billing accounts, invoices, charges, disbursements, and commissions from BillingCenter.
Use Cases
Cross-Center Policy and Claim Sync
Keep PolicyCenter, ClaimCenter, and BillingCenter aligned by syncing policies, claims, and billing accounts in real time across InsuranceSuite apps without brittle plugin handlers.
Automated First Notice of Loss Intake
Programmatically file FNOL into ClaimCenter from agent portals, IoT telematics, or third-party intake forms, then create exposures, reserves, and notes in a single API flow.
Billing Reconciliation and Disbursements
Pull invoices, charges, payments, and commissions from BillingCenter to reconcile carrier ledgers, automate disbursements, and reduce billing exceptions across distribution partners.
Marketplace Partner App Integration
Connect PartnerConnect-certified apps and internal tooling into InsuranceSuite via a unified API, even when Guidewire Cloud API access is gated by partner approval.
Connect via No-Code Tools
Automate this platform from the no-code stack you already use.
Technical Requirements
Authentication
Would require OAuth 2.0 client credentials for Guidewire Cloud API plus into the carrier IdP, with MFA (SMS, email, TOTP) supported for portal-based access.
Connectivity
Would build on JSON REST Cloud API for InsuranceSuite on Guidewire Cloud and InsuranceNow; SOAP/XML plugin and message-destination integrations for self-hosted deployments. Cloud API access is partner-gated via PartnerConnect and Marketplace certification.
Response format
JSON for Cloud API (PolicyCenter, ClaimCenter, BillingCenter, PricingCenter, UnderwritingCenter); SOAP/XML for legacy plugin integrations on self-hosted InsuranceSuite.
Rate limits
Per-tenant throttling enforced by Guidewire Cloud; carrier-specific limits apply on self-hosted deployments based on app server capacity and integration handler concurrency.
Session management
Would need cloud API access tokens via OAuth 2.0 client credentials with automated refresh; sessions into PolicyCenter, ClaimCenter, and BillingCenter maintained with continuity across InsuranceSuite apps.
Data freshness
Real-time reads against PolicyCenter, ClaimCenter, and BillingCenter; event-driven push updates via integration handlers and message destinations as policies, claims, and billing accounts change.
Security
SOC 2 compliant Guidewire Cloud, role-based entitlements (underwriter, adjuster, billing analyst), carrier-specific audit controls, and document handling for policy declarations and loss correspondence.
Webhooks
Event messaging via Guidewire integration handlers, message destinations, and event-driven hooks; outbound notifications for policy lifecycle, claim status, and billing events configurable per carrier.
Latency
Design target: sub-second reads on Guidewire Cloud for policy, claim, and billing lookups; submission binding, FNOL creation, and rated premium calculations may take longer due to Gosu rule evaluation and Product Designer logic.
Throughput
Design target: bulk submission, claim, and billing operations supported via Cloud API and batch integration handlers; throughput scales with carrier tenant sizing and concurrency configured in PolicyCenter, ClaimCenter, and BillingCenter.
Reliability
Carrier-provisioned non-prod tenants for testing;
Versioning
Clear versioning and change management would matter as Guidewire evolves
Frequently asked questions
PartnerConnect certification is required to publish in the Guidewire Marketplace and to consume Cloud API directly as a vendor. Carrier-led integrations using a carrier's own access do not require partner approval, which is how most internal tooling and agent portals connect.
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 Guidewire 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.