Partner Life Single Sign-On

Partner Life is the comprehensive portal for partners to manage contracts, support requests, customer information, and policy changes. This guide explains how to integrate your existing authentication system with Partner Life using the Platform GraphQL API.

Prerequisites​

Before you begin, ensure you have:

• Your API Key
• Your Partner ID (the insurance system broker ID, e.g., 123000, 23330-2)
• The Partner IDs of your sub-brokers and employee accounts (found in their welcome emails or in the colleague section of your Partner Life account)

Integration Steps​

1. Basic Setup​

First, set up access to the Platform GraphQL API as described in the Platform GraphQL API Guide.

2. Generate Magic Links​

Use the createPartnerLifeMagicLink mutation to generate direct access links to Partner Life:

mutation CreatePartnerLifeMagicLink($input: CreatePartnerLifeMagicLinkInput!) {
  createPartnerLifeMagicLink(input: $input) {
    ... on PartnerLifeMagicLink {
      url
    }
    ... on ErrorInterface {
      message
    }
  }
}

Example input — logging in the partner identified by the x-partner-id header:

{
  "input": {
    "alreadyMultiFactorAuthenticated": true,
    "acceptPartnerLifeTermsAndConditions": true,
    "acknowledgePartnerLifePrivacyPolicy": true
  }
}

Example input — logging in a sub-partner or colleague account:

{
  "input": {
    "partnerLifewareId": "123456",
    "alreadyMultiFactorAuthenticated": true,
    "acceptPartnerLifeTermsAndConditions": true,
    "acknowledgePartnerLifePrivacyPolicy": true
  }
}

3. Authentication Flow​

The basic authentication flow works as follows:

4. Multi-Factor Authentication​

If your system already implements MFA, you can skip Partner Life's MFA check by setting alreadyMultiFactorAuthenticated to true:

Auto-Activation of Accounts​

For partners with a Partner ID but no active Partner Life account, you can automatically activate their account by setting both acceptPartnerLifeTermsAndConditions and acknowledgePartnerLifePrivacyPolicy to true.

Before activating, ensure the partner has accepted:

• Terms and Conditions
• Privacy Policy

Deep Linking​

A magic link accepts a redirect parameter — a URL-encoded Partner Life path. The advisor is logged in and lands there instead of on the dashboard.

https://partner.life.li/en/magic-link/<Magic Link Token>?redirect=<URL-encoded path>

Destinations​

The last two write the offer as the page loads. Right when the product is already settled; for an exploratory jump they leave an offer behind for every conversation that went nowhere.

<Customer ID> is the ID createCustomer returns, or the one customer resolves from an email address. <Contract ID> comes from createOffer. If an ID is unknown, or the broker account is not licensed to reach that customer, the advisor is told so — your software receives no signal either way.

Example, fully encoded:

https://partner.life.li/en/magic-link/<Magic Link Token>?redirect=%2Fmy%2Foffers%2Fnew%3FcustomerId%3D<Customer ID>

Product Codes​

Only the two product-scoped paths need one.

A code names no tariff, so it survives a product moving to a new tariff generation. The advisor gets the newest generation their account is licensed for; where a cross-border or gross variant exists, the standard tariff is chosen.

Error Handling​

The mutation returns a union type. Always handle the error cases:

Security Best Practices​

1. Protect magic link URLs — they are single-use authentication tokens. Do not log or cache them.
2. Use server-side calls only — never call the API from client-side code; your API key would be exposed.
3. Validate MFA claims — only set alreadyMultiFactorAuthenticated to true when your system has genuinely verified the user with multiple factors.
4. Minimal scope — only request magic links for partners within your broker tree. The API enforces this, but your integration should validate upfront.

Need Help?​

If you don't have access to Partner Life or need assistance, contact partner support.