Skip to main content Skip to complementary content
Qlik Resources

Guidewire BillingCenter (Lite)

Guidewire BillingCenter is Guidewire’s insurance billing system with prebuilt models and flexible architecture to support all existing and future policyholder transactions.

For more information about the API, see Guidewire Cloud API Documentation.

Supported update methods

For more information, see An overview of target update methods.

Landing tasks:

  • Change data capture (CDC)

  • Reload and compare

Replication tasks:

  • Change data capture (CDC) using Change Tables

  • Full load

Landing data in a data lake tasks:

  • Change data capture (CDC)

  • Reload

Preparing for authentication

To access your Guidewire data, you need to authenticate the connection with your account credentials.

Information noteMake sure that the account you use has read access to the tables you want to fetch.

Creating the connection

For more information, see Connecting to SaaS applications.

  1. Fill in the required connection properties.

  2. Provide a name for the connection in Connection name.

  3. Select Open connection metadata to define metadata for the connection when it has been created.

  4. Click Create.

Connection settings
Setting Description
Data gateway

Select a Data Movement gateway if required by your use case.

Information note

This field is not available with the Qlik Talend Cloud Starter subscription, as it does not support Data Movement gateway. If you have another subscription tier and do not want to use Data Movement gateway, select None.

For information on the benefits of Data Movement gateway and use cases that require it, see Qlik Data Gateway - Data Movement.
JWT Payload JSON Web Token payload is a set of claims. Each claim is a key/value pair that represents information that the bearer of the token claims to be true.
Signing Algorithm The algorithm to sign the JWT.
Private Key The private key to sign the JWT.
Token URL Token URL.
Token Request Body The body to send to the Token URL. Use <signed> as a variable for the signed JWT Payload.

Example: grant_type=urn:ietf:params:oauth:grant-type:jwt-bearer&assertion=<signed>
Base URL The base URL for this source. This is the common part of the endpoints preceding /bc/rest/.
User Context User context.

The contents of this field will be base64-encoded and included as GW-User-Context header. If a user context is not needed, leave the field empty.

For more information, see JWTs for services with user context.

Supported datasets

The following datasets are supported. For more information about the datasets, see Guidewire Cloud API Documentation.

  • Agency Bill Plans

  • Billing Plans

  • Commission Plans

  • Delinquency Plans

  • Payment Allocation Plans

  • Payment Plans

  • Return Premium Plans

  • Disbursements

  • Suspense Payments

  • Batch Processes

  • Database Consistency Checks

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!

Leave your feedback here