Migrating to the Vertical Insure Landing Page

This document describes the steps required to move away from the USSCI quote page and begin redirecting users to the Vertical Insure landing page.

Build the landing page URL

Your contact at Vertical Insure will tell you what the base of the URL you are building will be. It will be in the following form:

    https://landing.verticalinsure.com/$partner/$product

If you are offering multiple products, you will get multiple base URLs, one for each product.

Users can use this base URL to reach a quote page. On the page will be a form that they can fill out in order to receive a quote. Once they have received the quote, there will also be a checkout form which will allow them to pay for and receive their policy.

In order to help save the user time and increase the likelihood that they will complete the checkout process, it helps to provide information that you've already collected from the user. The Vertical Insure landing page supports a query string, where each 'key' is the 'name' of a form field and each 'value' is the value which will be prefilled into that form field.

For example, if you wanted to provide the first name and last name of the customer, you would include a query string like:

    ?customer.first_name=John&customer.last_name=Smith

Dates should be formatted like "yyyy-MM-dd':

    ?policy_attributes.event_start_date=2030-12-25

Values with special characters should be URL encoded:

    ?policy_attributes.organization_name=My%20Organization

If your quote form takes an array (like a list of teams, for example), you can set a value for a field inside an element of the array by using the index like this:

    ?policy_attributes.teams.0.insurable_amount=99.99

States should be provided as the 2-character abbreviation.

    ?customer.state=MN

You can refer to the quote form itself to see which fields are available, and to the corresponding quote API documentation to see what each field is named and what value is meant to be, but for your convenience, here are the fields supported for the team-registration product quote form:

• customer.first_name
• customer.last_name
• customer.email_address
• customer.phone_number
• customer.street
• customer.postal_code
• customer.city
• customer.state
• customer.country
• policy_attributes.organization_name
• policy_attributes.teams.$index.team_name
• policy_attributes.teams.$index.insurable_amount
• policy_attributes.event.name
• policy_attributes.event.type
• policy_attributes.event.location
• policy_attributes.event.address.street
• policy_attributes.event.address.city
• policy_attributes.event.address.state
• policy_attributes.event.address.zip
• policy_attributes.event.event_start_date
• policy_attributes.event.event_end_date

Notes on offering SportsFee registration cancellation assurance

Our SportsFee product is a 'special case' of the registration cancellation product we offer to other partners, which means it uses the same form and the same URL as other registration cancellation products, but it has a few extra requirements. Only certain partners can quote and bind SportsFee protection, and there are a few extra required fields which are not visible in the quote form because the partner is meant to provide them. Those two extra required fields are:

• policy_attributes.sports_fee_club_name
• policy_attributes.sports_fee_sports_club_id

The other fields supported for SportsFee registration-cancellation are:

• customer.first_name
• customer.last_name
• customer.email_address
• customer.phone_number
• customer.street
• customer.postal_code
• customer.city
• customer.state
• customer.country
• policy_attributes.event_start_date
• policy_attributes.event_end_date
• policy_attributes.insurable_amount
• policy_attributes.participant.first_name
• policy_attributes.participant.last_name

Test the landing page URL

Once the URL is built, you may follow it in order to see if the form populates correctly with the information provided.