1. Configure Integration in Feathery

1. Navigate to your Feathery form → Integrations tab
2. Select Guidewire

2. Authentication Configuration

Feathery supports multiple authentication mechanisms depending on your Guidewire deployment:

OAuth 2.0 (Recommended)

Used for Guidewire Cloud and modern deployments.

Supported flows:

• Client Credentials Flow (most common for server-to-server)
• Authorization Code Flow (if acting on behalf of a user)

Required fields:

• Token URL (e.g., https://<tenant>.guidewire.net/oauth/token)
• Client ID
• Client Secret
• Scopes (e.g., pc:read pc:write, cc:read cc:write)
• Audience (if required by your tenant)

Behavior:

• Feathery automatically handles:
  • Access token retrieval
  • Token refresh
  • Retry on expiration

API Key / Bearer Token

Used in some private or legacy setups.

• Static token passed via Authorization: Bearer <token>
• Suitable for internal APIs or gateways

Basic Authentication

Typically used for on-premise Guidewire or older versions.

• Username + password
• Sent via base64-encoded header

mTLS (Optional / Advanced)

• Mutual TLS for enterprise deployments
• Requires certificate upload and configuration

3. Select Guidewire System & API Version

Choose which Guidewire system you’re connecting to:

Supported Systems

• PolicyCenter (Policy lifecycle, submissions, quotes)
• ClaimCenter (Claims, exposures, FNOL)
• BillingCenter (Accounts, invoices, payments)

Supported Versions

• Guidewire Cloud (latest) - fully supported (recommended)
• Guidewire 10.x+ (REST APIs enabled) - supported
• Guidewire 8.x–9.x - SOAP support

4. Configure API Actions

Define what actions Feathery should perform when the form is loaded or submitted.

Common Action Types

Prefill (Read)

• Fetch data from Guidewire to populate form fields
• Example:
  • Get Account by ID
  • Retrieve Policy details
  • Load Claim information

Configuration:

• Endpoint: GET /policy/v1/policies/{policyId}
• Input mapping: Feathery field → path/query param
• Output mapping: API response → Feathery fields

Create

• Create new Guidewire records

Examples:

• Create Submission (PolicyCenter)
• FNOL → Create Claim (ClaimCenter)
• Create Account (BillingCenter)

Configuration:

• Endpoint: POST /policy/v1/submissions
• Request body mapping: Feathery fields → JSON payload

Update

• Update existing records

Examples:

• Update policy contact info
• Add claim notes
• Modify billing account

Configuration:

• Endpoint: PATCH /claim/v1/claims/{claimId}
• Partial payload updates supported

Trigger Actions / Workflows

• Bind quote
• Issue policy
• Assign claim
• Generate invoice

Example:

• POST /policy/v1/submissions/{id}/quote
• POST /policy/v1/submissions/{id}/bind

5. Field Mapping

Map Feathery form fields to Guidewire API fields.

Features

• Nested JSON mapping (e.g., insured.address.street)
• Conditional mapping (based on form logic)
• Data transformation:
  • Formatting dates
  • Enum mapping
  • Boolean normalization

6. API Call Behavior

Feathery supports robust API execution controls:

Request Types

• REST (JSON-based)
• GraphQL (if exposed via gateway)
• SOAP (via custom connector)

Methods

• GET, POST, PUT, PATCH, DELETE

Advanced Features

• Retry logic (configurable attempts & backoff)
• Timeout handling
• Error branching (e.g., route user if API fails)
• Idempotency keys (for safe retries)

7. Webhooks & Event Handling

Feathery can also react to Guidewire events:

• Receive webhook callbacks (via middleware or API gateway)
• Trigger form updates or workflows
• Sync status changes (e.g., claim approved)

8. Testing & Validation

• Use Feathery’s Test Mode to simulate API calls
• Inspect:
  • Request payload
  • Response body
  • Authentication headers
• Validate mappings before going live

9. Go Live

1. Click Connect
2. Enable integration in production environment
3. Monitor logs and API responses