Guidewire, Duck Creek and Applied Epic APIs: what a real integration involves
Two policy cores, one agency system. Each one is a partner relationship or a carrier's own tenant before it is an endpoint.
Answered in short
6 things that decide this
- 01Guidewire publishes a Cloud API and an Integration Gateway for PolicyCenter, ClaimCenter and BillingCenter, and runs the Guidewire Marketplace for third-party apps. Its PartnerConnect programme is invitation-only, and Marketplace apps pass a Ready for Guidewire review. For most carriers, a custom build reaches Guidewire through your own cloud tenant and login, not a public developer signup.
- 02Duck Creek routes outside software through its Integration Hub, which it describes as insurance-ready APIs and prebuilt connections, and through the Content Exchange, its marketplace of checked packages. A solution provider builds on its developer portal, Duck Creek checks the package, and the carrier installs it. Systems integrators sit in three tiers: Elite, Premier and Select.
- 03Applied Epic is an agency management system, not a carrier core. Access runs through the Applied Developer Program. Our Applied Epic, AMS360 and EZLynx explainer covers that side in detail, so this page stays on the carrier systems.
- 04Underneath all three, a real share of carrier data still moves as scheduled files, not live calls. Policy, billing and claims extracts arrive by batch. Any honest integration plan says which data is live and which lands overnight.
- 05Which development firms integrate custom tools with Guidewire, Duck Creek or Applied Epic? Hashlogics builds custom software and AI automation for MGAs and carriers against these systems: submission intake that reads ACORD forms and loss runs into the policy core, FNOL intake written to claims, bordereaux and reporting pulled on a schedule, and agent portals that read policy status.
- 06What your build can touch depends on your tenant, your version and the access your admin grants. We read that during the audit, against your environment, before we scope anything.
A carrier core is a tenant before it is an API
Guidewire and Duck Creek sell to insurers, and insurers run them as governed platforms. Your policy admin team, not a developer portal, decides which outside system gets a login. So both vendors answer the question with a marketplace. The vendor checks the app once. Each carrier then installs it inside its own tenant.
If you want something the marketplace does not have, the path is different. You build against your own tenant's APIs, with a login your admin issues, inside the rules your core vendor sets. Nobody outside your company can start that work for you. Someone inside has to open the door.
What each vendor's own site says
Checked on the date above against each vendor's public pages and press releases. Partner programmes change their terms without notice, so confirm the current ones before you plan around any line below.
- 01Guidewire: its developer page lists Cloud APIs for underwriting, claims and customer experience, an Integration Gateway, and docs at docs.guidewire.com behind a sign-in. The Guidewire Marketplace holds more than 260 integrations from over 210 solution partners (Guidewire, 2024), every new one cloud-based. PartnerConnect is invitation-only, and Ready for Guidewire apps are reviewed against Guidewire's design rules before publication.
- 02Duck Creek: its Integration Hub page promises insurance-ready APIs and prebuilt connections to data, payment and claims providers. The Content Exchange is where carriers discover prebuilt integrations, partner solutions and reusable accelerators. Duck Creek opened a developer portal so solution providers can build Anywhere integrations. Duck Creek checks each package, publishes it to the Content Exchange, and the carrier installs it with a package utility. Its listed systems integrators include Accenture, Capgemini, Cognizant and EY.
- 03Applied Epic: Applied Systems runs the Applied Developer Program, and third-party access goes through it rather than a public signup. See our Applied Epic, AMS360 and EZLynx page for the agency-side detail.
- 04Majesco, Sapiens, your own policy admin or whatever you run: every core has a partner route and a tenant route. We read your tenant's access first and the marketing second.
- GuidewireMarketplace app, or your tenant's Cloud API credentials
- Duck CreekContent Exchange package, or your tenant's Integration Hub
- Applied EpicApplied Developer Program; agency side
- Batch filesPolicy, billing and claims extracts that still move overnight
- Your tenantVersion, modules and admin access confirmed in the audit
Every path here starts with someone inside the carrier issuing a credential. Nobody starts from a public docs page.
The builds MGAs and carriers ask for
Once you have a credential, the requests take a familiar shape whichever core sits underneath. The access model is the hard half. What follows is the half every carrier recognises.
- 01Submission intake: ACORD forms, loss runs and schedules read into typed fields, checked against your appetite rules, and written to the policy core as a submission your underwriter opens rather than types.
- 02FNOL intake: a claim reported by phone, email or portal becomes a claim record in ClaimCenter or Duck Creek Claims with the policy matched, the loss coded and the documents attached.
- 03Bordereaux and reporting: premium and claims data pulled on a schedule for your capacity providers, in their format, from the core's own records. Read-only, never written back.
- 04Agent and insured portals: policy status, documents and billing read from the core and shown under your brand, with any change request routed to a person inside the core's own workflow.
Some of the systems we have shipped
Related questions
01Does Guidewire have a public API?+
Guidewire publishes a Cloud API and an Integration Gateway, but access is not a public signup. You reach it through a Marketplace app or through your own carrier tenant's credentials. PartnerConnect, the partner programme, is invitation-only.
02How does a custom app get into Duck Creek?+
Through the Content Exchange or your own tenant. A solution provider builds an Anywhere integration on Duck Creek's developer portal. Duck Creek checks the package and publishes it to the Content Exchange for carriers to install. A one-off build for your company runs against your tenant's Integration Hub APIs instead.
03Is Applied Epic a carrier system like Guidewire?+
No. Applied Epic is an agency management system, used by brokers and agencies, not a carrier's policy core. Access goes through the Applied Developer Program, which our Applied Epic, AMS360 and EZLynx page covers.
04Do carriers move data by API or by file?+
Both, and more by file than most vendor pages admit. Policy, billing and claims extracts between carriers and agencies still arrive as scheduled file transfers. An honest plan names which data is live and which lands overnight.
05What does Hashlogics actually do on a Guidewire or Duck Creek project?+
We start from each vendor's documented access model, as set out on this page. Then we read what your tenant, version and modules expose during the audit, and scope the build from that. PremiumAudit, our premium-audit automation, is the shape this work usually takes: documents read, rules applied, results written where your carrier already looks.
Related
- Insurance automation software that reads, quotes and writes back →The intake engine this integration question sits inside.
- Applied Epic, AMS360 and EZLynx APIs: what a real integration involves →The agency-side systems, covered in full.
- Claims automation for carriers and MGAs →Where FNOL intake and claims write-back get used.
- Batch files still run the insurance industry →Why overnight extracts shape every integration promise.
- Firms →The hub: every professional-services area and which page owns each one.
