Migrating from Digital Onboarding

This guide covers Liechtenstein Life Invest. Move offer creation from /graphql/partner to /graphql/partner-platform. Keep your existing Partner Life link. Continue completing and submitting the application in Partner Life.

1. Change the endpoint​

Use the same API base URL as your existing integration. For testing, use Stable.

2. Move the fields​

Use the table for the operation you call today. The new operation is always createOffer(input:).

If you currently use createOffer​

All paths below start inside the mutation's input argument. For the new API, LLI means liechtensteinLifeInvest.

Inside person.newCustomer:

If you currently use createUser​

Old paths below start inside user. New paths start inside input. For the new API, LLI means liechtensteinLifeInvest, and person means LLI.associatedPersons[].person.newCustomer.

The LLI contract language accepts DE_DE, EN_US, or DE_CH. Old FR and IT locale values have no matching contract language. Agree the document language before switching those customers.

Sustainability fields​

These paths are relative to investmentStrategy.sustainabilityDetails.

If you still use the older productConfiguration.aims input, contact us for the mapping before switching.

3. Add the required fields​

All paths below start inside input.liechtensteinLifeInvest. Some fields are new. Others were optional in the old API and are now required. If you already collect a value, move the actual value into the new field.

If hasCriticalIllness is true, also send criticalIllnessDetails. If policyReason or moneyOrigin is OTHER, send the corresponding policyReasonOtherText or moneyOriginOtherText.

Send these required values when creating the offer, before opening Partner Life. Do not use placeholder answers for customer declarations.

Keep the units correct​

• Money uses EUR cents: 10000 means EUR 100.00. Values from the old policyConfigurationV2 already use cents.
• If you still use the deprecated policyConfiguration input on createUser, its amounts use euros. Convert those amounts to cents once.
• Dates use YYYY-MM-DD.
• Fund percentages must total 100, with no duplicate funds and at most 10 funds.
• Send rebalancingType explicitly to preserve your current choice. Without a partner-specific default, the old createOffer uses NONE and the new API uses NORMAL when the field is omitted.

4. Update the response handling​

A customer record on an offer is separate from the customer online account. Keep the Partner Life login link for the broker. Remove any step that expects a customer login link from offer creation.

Match existing customer IDs​

Look up the customer by email to read both IDs:

query CustomerIDs($email: Email!) {
  customer(input: { email: $email }) {
    __typename
    ... on CustomerInterface {
      ID
      consumerID
    }
    ... on ErrorInterface {
      message
    }
  }
}

Match consumerID against the consumer ID you already store. Store ID for new Platform API requests. Do not replace one with the other.

Read the creation result​

Use this mutation for the new API:

mutation CreateLLIOffer($input: CreateOfferInput!) {
  createOffer(input: $input) {
    __typename
    ... on CreatedOffer {
      contractID
    }
    ... on ErrorInterface {
      message
    }
    ... on InputValidationError {
      invalidInput
    }
  }
}

Store contractID on success. Handle error results using __typename and message. Check top-level GraphQL errors as well.

5. Keep the Partner Life handoff​

1. Create the offer through the new API.
2. Keep the existing wait until the offer is available in Partner Life.
3. Open Partner Life using your existing login and offer link.
4. Complete and submit the application in Partner Life as you do today.

Check which identifier your existing offer link needs. The new creation result is contractID; the old offerId field is not returned. Do not assume these values are interchangeable.

The customer online account is created during policy pickup. No customer login step is needed when you create the offer.