Skip to content

Guidewire

The test-estate safety rule: stand the test estate up only beside a test instance, never a production deployment. Its systems are throwaway test services with published credentials: change-me is every test credential. They are still encrypted and still ask for a login, because FACE refuses a connection that is not (see Connector security). Use a scratch machine or a scratch cluster.

Grade C · dataset: API (the vendor’s response payloads) · type guidewire

What it is

A Guidewire ClaimCenter tenant read over the Cloud API. In the test estate it holds the cargo claims. The connector reference is Enterprise SaaS and ERP.

Grade

C. Model only. There is no freely available local edition of the platform.

See the grade table for all 32 types.

Settings and credentials

From the connection catalogue. Settings are ordinary fields on the connection record. Credentials are kept in a sealed bundle and never returned.

Names
Typeguidewire
Settingsbase_url, username, tenant_id
Credentialspassword

The test connection

Quillmere cargo claims (ClaimCenter)

SettingTest value
base_urlhttps://claims.quillmere.invalid/rest
usernameface_reader
tenant_idquillmere

Credentials: password. In the test estate, every credential is change-me. Credentials are write-only: they go into the sealed credential bundle and are never returned.

Stand up the test system

The safety rule at the top of this page comes first: a scratch machine or a scratch cluster, never a production or platform one.

  1. Download guidewire.zip and unzip it. It holds /claim/v1/claims responses and expected.json.
  2. Open the payloads next to expected.json, or add the connection with the settings above, pointed at a ClaimCenter tenant you already have.

What FACE finds

Against a real tenant, FACE reads the Cloud API schemas. The dataset is /claim/v1/claims responses.

DatasetKindDomainPrimary keyRowsFields
claimscloud_api_resourceclaimsattributes.id414

expected.json in the download has the full model: every field with its logical type, the source’s native type and nullability.

How it joins the Quillmere universe

This source carries 3 of the universe’s shared keys. The same ID means the same thing in every source: a shipment here is the same shipment in the database, the event bus, the GPS track and the claim PDF.

Universe entityFields hereAlso in
carrierclaims.attributes.carrierCode_Extd365, document, files, mysql, objectstore, postgres, redshift, sharepoint, tms, yms
claimclaims.attributes.claimNumberfiles, salesforce, sharepoint
shipmentclaims.attributes.shipmentNumber_Extbigquery, d365, databricks, document, excel, files, github, iot, kafka, logisticsapi, mqtt, mysql, objectstore, postgres, redshift, salesforce, sap, servicenow, sharepoint, tms, whs, yms

Evidence it holds for the planted anomalies:

  • ANOM-2, A claim near its filing deadline. guidewire/claim_v1_claims.json in guidewire.zip, look for "carrierFilingDeadline_Ext": "2026-10-05" (state draft, filedWithCarrier_Ext false).

See all connectors at once for the walkthrough across every source.

Download

This is one of 25 zips: the 7 streaming types ship as replay recordings instead.

What is in the zip
  • guidewire/claim_v1_claims.json
  • guidewire/expected.json

The whole universe is universe.json. manifest.json lists every download with its size and SHA-256, and SHA256SUMS is the same list for sha256sum -c.