Quote and Purchase flows

This section documents use-cases about embedding quote and purchase paths and providing a more tightly integrated user experience, allow for improved user experience and increased conversion rates.

This can be used to support both standalone sales funnels as well as integration into bundled sales opportunities.

Quick start guide - Getting started

To get started with a basic quote request the following request can be sent to the Quotes API with a simple sample request. This will return a list of plans available for this quote request:

There are two quote types supported to retrieve single trip and annual multi-trip plans:

• SINGLETRIP
• MULTITRIP

A sample request is shown below, note that country codes are defined in the Country list API

1
{
2
    "stage": "INITIAL",
3
    "input": {
4
        "quoteType": "SINGLETRIP",
5
        "homeAddress": {
6
            "countryCode": "AUS"
7
        },
8
        "destinationCountryCodes": [
9
            "ESP"
10
        ],
11
        "policyHolders": [
12
            {
13
                "isPrimary": true,
14
                "isDependent": false,
15
                "age": 33
16
            }
17
        ],
18
        "departureDate": "2023-05-27",
19
        "coverEndDate": "2023-06-26"
20
    }
21
}

To set a specific plan on subsequent quote requests, which should be done before selecting additional options you can set the plan Id in the subsequent requests to be:

1
body.input.planId = body.prices[1].planId;

The planId will be specific to the brand code and specific products offered, it is recommended to retrieve this dynamically and not hard code it in the API integration.

Quote stages

Quote stages can be used to set stages in the quote, these can be useful for restoring the position

• INITIAL - This is used for initial quote creation after entering basic details for the quote
• BASEQUOTE - This is used for when a plan selected has been returned.
• OPTIONS - This is for when a plan has been selected and options are been added to the existing quote.
• DETAILS - This is for when traveller details are been entered.
• MEDICAL_SCREENING - This is for when traveller initiates medical screening and remains in the medical screening flow (including resume and completing screening).
• PAYMENT - This is for when payment is been taken on the quote.

Policy number on Payment

You can retrieve the policy number to display to the customer returned from the API upon purchase by utilising the policyNumber attribute returned as part of the response of the Purchase API.

An example return response showing an example of the policyNumber attribute been returned by the purchase API call is shown below:

1
    "quote": {
2
        "id": "274ba4ce-8937-462a-949a-1e87e845a23c",
3
        "isNew": false,
4
        "isPurchased": true,
5
        "hasConfigChanged": false,
6
        "isPurchaseInitiated": true,
7
        "clientSessionId": "a8235a14-406c-46a0-9ee2-456ce8e0cc9c",
8
        "policyNumber": "<PolicyNumber>",
9
        "stage": "PAYMENT",
10
     ...
11
    }

Quote and purchase flow

The sequence flow for retreiving a quote is typically the following. The sequence is the following:

• Client needs to have username and password to retrieve access token
• Call is made from client to the user API endpointto get an access token using user credentials (username and password). Sample requests and parameter details available at Authorization
• Use this token as a bearer token while making a call to retrieve a quote based on supplied parameters including trip dates, destination country, country of residence. (If applicable to the brand). A list of available products with detailed pricing information will be returned with all available plans. Quotes API
• Select a plan, add options to the quote and retrieve the updated pricing information Options
• Credit card tokenisation flow to the card token API Credit card tokenisation API
• Purchase request utilising the tokenised credit card information.Purchase API

Retrieving product benefits

The following sequence can be used to retrieve product benefits. It can include the following information:

• Benefit name
• Benefit description
• Benefit limit and sub-limits

To access plan benefits it is recommend using the Product benefits by Plan API. The plan ID parameter is passed back from the Quote response and applies to the individual plan documenting the detailed benefit and limits available.

This can be used to avoid hard coding benefit limits in integrated purchase paths.

Policy documentation

To provide detailed policy specific documentation, including product disclosure statements, the Products API can be used to provide contextual links to display to the customer. To access policy wording for a choosen insurance contract you can access it by going to PDS link.

Medical screening

It is recommended that a URL redirect be introduced to support medical screening of pre-existing conditions if this capability is required.

Accepting Terms and conditions

To accept terms and conditions it is advisible to use the property “hasAcceptedTermsAndConditions” and set it to “true” in the Quote input Request. Note that this value should be set to true once all the T&C’s options are selected by the user.

1
{
2
    "stage": "DETAILS",
3
    "input": {
4
        ...
5
        "hasAcceptedTermsAndConditions":true,
6
        ...
7
    }
8
}

Retrieving Quote on a hosted Purchase Path

In order to support the hosted purchase path usecases to retrieve a quote, then are few steps to follow. The potential usecases are:

• When redirecting to the hosted purchase path via email a quote flow
• When redirecting back to the hosted purchase path on completion of the medical screening flow

The example redirect URL will be like below:

1
https://<Partner Quote Line URL>/?token=<interchange token>

We recommend to make use of the interchange token end point to retrieve a Quote object for the token.

The sample response is here:

1
{
2
    "category": "Success",
3
    "data": {
4
        "quoteReferenceNumber": "QNIB002440",
5
        "quote": {
6
            "id": "2b8dbb77-84a6-4036-b1fa-90c98c9236a7",
7
            ...
8
            "input": {
9
            ...
10
            },        
11
        }
12
    }
13
}