Back office and Mid Office travel policy integration

This section documents use-cases about integrating the policy details in partners' back-office and mid-office systems to streamline agent booking and improve frontline productivity.

Policy details

The following provides a mapping for key elements for integrating into partner mid-office systems with mapping to API attributes. The following parameters are all available from the policy API summary endpoint

Tax breakdown

The policy details endpoint contains a breakdown of the taxes payable on the policy. The total tax breakdown is calculated on the policy premium after discounts have been applied. An example is given below for Australian taxes. Round the resulted API return results to 2 decimal places to ensure accurate representation of the taxes payable on the transaction amount:

    "taxes": [
        {
            "name": "Stamp Duty",
            "amount": 6.11009174
        },
        {
            "name": "GST",
            "amount": 6.17180983
        }
]

Options

The policy details endpoint contains a detailed breakdown of options information that can be used to populate downstream into mid-office systems.

Cancellation option

The cancellation limit option provides the cancellation coverage selected (E.g $20,000) as well as the additional premium incurred:

    "policyCancellationLimitOption": {
        "id": 5536508,
        "coverLimit": 20000.00000000,
        "premium": 46.33000000
    },

Specified item option

The specified items contains the list of items, including item value been requested and total additional premium:

    "policySpecifiedItemOption": {
        "specifiedItems": [
            {
                "name": "Item1",
                "currency": {
                    "id": 1,
                    "symbol": "$",
                    "code": "AUD",
                    "description": "Australian Dollar",
                    "hasMinorUnits": true
                },
                "itemValue": 1234.00000000,
                "displayItemValue": "$ 1,234.00"
            },
            {
                "name": "Item2",
                "currency": {
                    "id": 1,
                    "symbol": "$",
                    "code": "AUD",
                    "description": "Australian Dollar",
                    "hasMinorUnits": true
                },
                "itemValue": 432.00000000,
                "displayItemValue": "$ 432.00"
            }
        ],
        "premium": 74.59000000
    },

Specified medical condition option

The specified medical condition provides a breakdown of which travellers have opted in for medical screening cover, additional excess payable if the specified condition occurs during the claimable event as well as the additional premium payable:

    "policySpecifiedMedicalConditionsOption": {
        "medicalScreenings": [
            {
                "id": "5536510",
                "referenceNumber": "0798659",
                "travellerGuid": "ec739c40-74ea-45db-bd39-8bd34fb6efd1",
                "screeningDate": "2023-09-17T23:42:00Z",
                "outcome": "OptInForCover",
                "excess": 100.00000000
            }
        ],
        "premium": 75.22000000
    }

Policy Detail flow

The sequence flow for retreiving policy details for a partner and brand is typically the following.

• client needs to have username and password to access list of policies associated with a partner account
• call is made from client to the user API endpoint to get an access token using user credentials (username and password). Sample requests and parameter details available at Authorization
• use this as a bearer token to make a call to the policy detail endpoint available at the Policies API
• policy detail endpoint responds with the details for the given policy number. The schema of the response details available at the policy detail endpoint