1 of 7

Data Share

Pre-fill application questions, increase program profitability.

Authentic Application

To purchase an insurance policy, a customer must fill out an application with their businesses information which can take fifteen minutes to complete. Alternatively, we provide you with the option to pre-fill application questions with customer data you probably already have — this can reduce the time down to approximately 5 minutes.

Benefits of Pre-filling:

Improves accuracy of your insurance program. The performance of a program is correlated to the amount of accurate policyholder information. Using customer data from a trusted partner will help Authentic better price and underwrite your customers (customers can also edit and update any pre-filled fields that may be out of date).
Higher conversion rate for your insurance program. Fewer questions mean customers have to spend less time filling out their application.

Every application has three distinct parts:

Lead section: includes basic customer information that pre-qualifies them for a policy.
Policy section: assesses the customer's risk-profile, additional business operation specific questions and contains information such as limits and start date.
Exposure section: collects information for each location of operation.

Getting started with prefilling data

We recommend our partners start by passing us data for some of these
Once this is complete, partners are able to pass data for any additional fields we collect in our application; here is our

Data Sharing via URL

Here is a guide to pre-filling authentic application question fields through the URL

Forwarding data to your Authentic application flow is as simple as attaching one search parameter to your redirect URL:

https://[tenant_name].prod.authenticinsurance.com/apply?prefill_data=[payload]

The data parameter should be base64 encoded JSON with the following types in the following format:

For reference here is a tool to convert between JSON and base64 encoding: https://codebeautify.org/json-to-base64-converter

Which, encoded would look like this:

ewogICAgbGVhZDogewogICAgICBlbWFpbDogImxmcmFua0BhdXRoZW50aWNpbnMuY29tIiwKICAgICAgc3RhdGVDb2RlczogWyJPSCIsICJXWSJdLAogICAgICBidXNpbmVzc0NsYXNzQ29kZTogIjIwODMxIgogICAgfSwKICAgIHJlc3BvbnNlczogewogICAgICBleHBvc3VyZXM6IFt7CiAgICAgICAgaWQ6ICIxIiwKICAgICAgICBleHBvc3VyZU5hbWU6ICJidXNpbmVzc19sb2NhdGlvbiIsCiAgICAgICAgZmllbGRWYWx1ZXM6IHsKICAgICAgICAgICJBRERSRVNTIjogIjEwMCBzdHJlZXQsIFVOSVQgMiwgY2l0eSwgT0ggMzMzMzMsIFVTIiwKICAgICAgICAgICJTQUxFUyI6ICIxMDAwMDAiLAogICAgICAgICAgIkFSRUEiOiAiMjAwMCIKICAgICAgICB9CiAgICAgIH1dLAogICAgICBxdWVzdGlvbnM6IHsKICAgICAgICAiQlVTSU5FU1NfTEVHQUxfTkFNRSI6ICJBdXRoeSBJbnN1cmFuY2UgU2VydmljZXMsIEluYy4iLAogICAgICAgICJOQU1FIjogIkxpYW0gRnJhbmsiLAogICAgICAgICJQSE9ORSI6ICIyMDE0MjA2NzM1IiwKICAgICAgICAiTUFJTElOR19BRERSRVNTIjogIjIwMCBzdHJlZXQsIFVOSVQgNSwgRGF5dG9uLCBPSCAzMzMzMywgVVMiCiAgICAgIH0KICAgIH0KICB9

would then pass via the pre-fill data parameter as:

Parameter Naming Conventions for URLs

In our application, URL parameters are standardized to use snake_case (e.g., application_id) or kebab-case (e.g., application-id) rather than camelCase. This convention is followed to ensure consistency and to avoid potential issues with case sensitivity, which can sometimes cause confusion or errors in URL parsing. This practice aligns with common web development standards, similar to how UTM parameters (e.g., utm_source) are formatted. Importantly, this convention is consistent across all production & sandbox environments.

SMB Class Codes

Each SMB has an associated class code that we use to categorize the business to calculate the premium and help underwrite the risk

Class codes Authentic accepts:

CLASS_DESCRIPTION

CLASS_CODE

MARKET_GROUP_LONG

Physical Fitness Facility

Data Capture (Easy Webhook Set Up)

How we help you set up event data retrieval

Using webhooks, partners can send event data from our app to themselves. We have set up 8 data events for partners to use, and can field requests to make other events available. Partners can tie any combination of events to an endpoint.

Data events

funnel.start - customer visited the portal
funnel.lead_accepted - an application was generated for the customer. Email has been collected
funnel.lead_rejected - an application was generated and rejected for the customer. Email has been collected
funnel.quote_generated - at least one product was accepted for a quote
funnel.quote_declined - all products customer selected were declined when generating a quote
funnel.bind - customer purchased a policy
page.lead_info - a user has entered in all lead information besides products
page.exposure_final - a user has entered in all business locations and exposure information

See for sample events

Set up

Request us to create a consumer application for you via Slack or email
Access the consumer portal using the link and authentication information we will send you.
Navigate to "<> Endpoints" on the left sidebar if you are not there already. Click "+ Add Endpoint".

Data Capture (Easy Webhook Set Up)

How we help you set up event data retrieval

Data events

funnel.start - customer visited the portal
funnel.lead_accepted - an application was generated for the customer. Email has been collected
funnel.lead_rejected - an application was generated and rejected for the customer. Email has been collected
funnel.quote_generated - at least one product was accepted for a quote
funnel.quote_declined - all products customer selected were declined when generating a quote
funnel.bind - customer purchased a policy
page.lead_info - a user has entered in all lead information besides products
page.exposure_final - a user has entered in all business locations and exposure information

See for sample events

Set up

Request us to create a consumer application for you via Slack or email
Access the consumer portal using the link and authentication information we will send you.
Navigate to "<> Endpoints" on the left sidebar if you are not there already. Click "+ Add Endpoint".

Data Sharing via URL

Here is a guide to pre-filling authentic application question fields through the URL

Forwarding data to your Authentic application flow is as simple as attaching one search parameter to your redirect URL:

https://[tenant_name].prod.authenticinsurance.com/apply?prefill_data=[payload]

The data parameter should be base64 encoded JSON with the following types in the following format:

{
    lead?: {
      email?: string;
      businessClassCode?: string;
      stateCodes?: string[];
      productIds?: string[];
    }
    responses?: {
      exposures?: Array<{
        exposureName: string;
        fieldValues: Record<string, string>;
      }>;
      questions?: Record<string, string>;
    }
  }

For reference here is a tool to convert between JSON and base64 encoding: https://codebeautify.org/json-to-base64-converter

  {
    lead: {
      email: "lfrank@authenticins.com",
      stateCodes: ["OH", "WY"],
      businessClassCode: "20831"
    },
    responses: {
      exposures: [{
        exposureName: "business_location",
        fieldValues: {
          "ADDRESS": "100 street, UNIT 2, city, OH 33333, US",
          "SALES": "100000",
          "AREA": "2000"
        }
      }],
      questions: {
        "BUSINESS_LEGAL_NAME": "Authy Insurance Services, Inc.",
        "NAME": "Liam Frank",
        "PHONE": "2014206735",
        "MAILING_ADDRESS": "200 street, UNIT 5, Dayton, OH 33333, US"
      }
    }
  }

Which, encoded would look like this:

ewogICAgbGVhZDogewogICAgICBlbWFpbDogImxmcmFua0BhdXRoZW50aWNpbnMuY29tIiwKICAgICAgc3RhdGVDb2RlczogWyJPSCIsICJXWSJdLAogICAgICBidXNpbmVzc0NsYXNzQ29kZTogIjIwODMxIgogICAgfSwKICAgIHJlc3BvbnNlczogewogICAgICBleHBvc3VyZXM6IFt7CiAgICAgICAgaWQ6ICIxIiwKICAgICAgICBleHBvc3VyZU5hbWU6ICJidXNpbmVzc19sb2NhdGlvbiIsCiAgICAgICAgZmllbGRWYWx1ZXM6IHsKICAgICAgICAgICJBRERSRVNTIjogIjEwMCBzdHJlZXQsIFVOSVQgMiwgY2l0eSwgT0ggMzMzMzMsIFVTIiwKICAgICAgICAgICJTQUxFUyI6ICIxMDAwMDAiLAogICAgICAgICAgIkFSRUEiOiAiMjAwMCIKICAgICAgICB9CiAgICAgIH1dLAogICAgICBxdWVzdGlvbnM6IHsKICAgICAgICAiQlVTSU5FU1NfTEVHQUxfTkFNRSI6ICJBdXRoeSBJbnN1cmFuY2UgU2VydmljZXMsIEluYy4iLAogICAgICAgICJOQU1FIjogIkxpYW0gRnJhbmsiLAogICAgICAgICJQSE9ORSI6ICIyMDE0MjA2NzM1IiwKICAgICAgICAiTUFJTElOR19BRERSRVNTIjogIjIwMCBzdHJlZXQsIFVOSVQgNSwgRGF5dG9uLCBPSCAzMzMzMywgVVMiCiAgICAgIH0KICAgIH0KICB9

would then pass via the pre-fill data parameter as:

Parameter Naming Conventions for URLs

Data Share

Pre-fill application questions, increase program profitability.

Authentic Application

Benefits of Pre-filling:

Improves accuracy of your insurance program. The performance of a program is correlated to the amount of accurate policyholder information. Using customer data from a trusted partner will help Authentic better price and underwrite your customers (customers can also edit and update any pre-filled fields that may be out of date).
Higher conversion rate for your insurance program. Fewer questions mean customers have to spend less time filling out their application.

Every application has three distinct parts:

Lead section: includes basic customer information that pre-qualifies them for a policy.
Policy section: assesses the customer's risk-profile, additional business operation specific questions and contains information such as limits and start date.
Exposure section: collects information for each location of operation.

Getting started with prefilling data

We recommend our partners start by passing us data for some of these
Once this is complete, partners are able to pass data for any additional fields we collect in our application; here is our

Data Sharing via Widget

Here is a guide to pre-filling authentic application question fields through our embedded widget

You can pre-fill data about your customer by passing in their information to the prefillData key of the widget configuration:

authenticWidget.init({
  portal: {
    url: "https://<tenant-name>.<environment>.authenticinsurance.com",
  },
  customerId: "unique_cid1",
  prefillData: {
    lead: {
      email: "customer@email.com",
      stateCodes: ["OH"],
    },
    responses: {
      exposures: [{
        exposureName: "business_location",
        fieldValues: {
          "ADDRESS": "100 street, UNIT 2, city, OH 33333, US",
        }
      }],
      questions: {
        "BUSINESS_LEGAL_NAME": "Customer Business Name",
        "NAME": "Customer Full Name"
      }
    }
  }
});

The complete interface for PrefillData is shown below:

interface PrefillData {
  lead?: {
    email?: string;
    businessClassCode?: string;
    stateCodes?: string[];
    productIds?: string[];
  };
  responses?: {
    exposures?: Array<{
      exposureName: string;
      fieldValues: Record<string, string>;
    }>;
    questions?: Record<string, string>;
  };
};

Each exposure is uniquely identified by an ID. This can be as simple as the index of the element in the array or a unique UUID.

Please visit the section to find the full data dictionary of the fields that can be passed in. Specifically, please see the first table, Fields for Widget Integration.

analytics.track('Application Quotes Generated v2', {
  auth: {
    userId: 'us-east-1:27d3ecbe-5e18-c423-b01e-a20738bf0c09',
    isAuthenticated: false,
    isAdmin: false,
    adminTenantId: null,
    email: null
  },
  analytics: {
    sessionId: '04a646c3-64a4-8829-1e5d-b167h835b454',
    sessionReplayLink: null,
    urlParams: {},
    user: {
      id: 'us-east-1:27d3ecbe-5e18-c423-b01e-a20738bf0c09',
      properties: {
        tenantName: 'demo',
        tenantCustomerId: null,
        businessName: 'John\'s Business',
        name: 'John Smith',
        phoneNumber: 1234567890,
        mailingAddress: '41 E 11th St, Manhattan, NY 10003, US'
      }
    }
  },
  products: [
    {
      id: 'ebb9c622-a576-4340-9832-f95938d4c661',
      name: 'Gym Liability',
      isOffered: true
    },
    {
      id: '5c7a1bef-fca1-41f6-b177-bc91de17009d',
      name: 'Property',
      isOffered: false
    },
    {
      id: '137233b3-2e6e-4799-b794-d16f4b6990c6',
      name: 'Worker\'s Compensation',
      isOffered: false
    }
  ],
  prefillData: {
    responses: {
      questions: {
        BUSINESS_LEGAL_NAME: 'John\'s Business',
        NAME: 'John Smith',
        POLICY_START_DATE: new Date('2025-02-03T05:00:00.000Z')
      }
    }
  },
  lead: {
    stateCodes: [
      'OH'
    ],
    productIds: [
      'ebb9c622-a576-4340-9832-f95938d4c661',
      '5c7a1bef-fca1-41f6-b177-bc91de17009d'
    ],
    email: 'example@gmail.com',
    businessClassCode: '47011L'
  },
  application: {
    id: '3b72dbc4-bcb0-4d79-91b4-2072a8ec3522',
    status: 'APPROVED',
    step: 'QUOTE',
    responses: {
      exposures: [
        {
          id: 1,
          exposureName: 'business_location',
          fieldValues: {
            ADDRESS: '1 Main St, Cleveland, OH 45001, US',
            SALES: '200000',
            BPP_LIMIT_QP: '20000',
            AREA: '2000',
            EXPOSURE_CLASS_DESCRIPTION: 'Strength & Conditioning (CrossFit, HIIT, Bootcamp, Weightlifting, etc.)'
          }
        }
      ],
      questions: {
        EMAIL: 'example@gmail.com',
        CLASS_CODE: '47011L',
        CLASS_DESCRIPTION: 'Strength & Conditioning (CrossFit, HIIT, Bootcamp, Weightlifting, etc.)',
        MARKET_GROUP_LONG: 'All Other',
        MKTGRP: 'AO',
        MULTIPLE_STATES: 'No',
        ORIGIN_URL: 'https://demo.staging.authenticinsurance.com',
        TENANT_NAME: 'demo',
        TENANT_ID: 'bb60519f-7de5-80a6-ae91-4a26446f8a13',
        BUSINESS_LEGAL_NAME: 'John\'s Business',
        NAME: 'John Smith',
        POLICY_START_DATE: new Date('2025-02-03T05:00:00.000Z'),
        FRANCHISE_SELECTED: 'No',
        YRS_IN_BUSINESS: '4-6',
        FITNESS_STUDIO_FORBIDDEN_ACTIVITIES: 'None of the above',
        GENERIC_BUSINESS_MGMT_PRACTICES_DECLINE: 'None of the above',
        PRIOR_LOSS_BINARY: 'No',
        PL_CURRENT_COVERAGE: 'No',
        ATTACH_AL3020_DECGL1: 'No',
        EPLI_ELECT: 'No',
        ATTACH_AL3002_DECGL1: 'No',
        ADD_CONTRACTOR_ADDITIONAL_INSUREDS: 'No',
        ATTACH_CG2026: 'No',
        MAILING_ADDRESS: '41 E 11th St, Manhattan, NY 10003, US',
        PHONE: '1234567890'
      }
    },
    quotes: [
      {
        id: '963c6b2d-d50f-412a-8787-32ce39c577cc',
        productName: 'Professional Liability',
        limits: [
          {
            locationAddress: null,
            name: 'Professional Liability Deductible',
            amountPerOccurrence: 1000,
            amountInAggregate: null
          },
          {
            locationAddress: null,
            name: 'Professional Liability Limit',
            amountPerOccurrence: 1000000,
            amountInAggregate: 1000000
          }
        ],
        adjustments: {
          ACCOUNT_CREDIT_DISCOUNT_VALUE: -24.002499999999998
        },
        annualPremium: 456.05,
        underwritingNotes: {}
      },
      {
        id: 'c2e67d62-220f-4106-a446-d9bdb49aba84',
        productName: 'General Liability',
        limits: [
          {
            locationAddress: null,
            name: 'Damage to Premises Rented to You Limit',
            amountPerOccurrence: 300000,
            amountInAggregate: null
          },
          {
            locationAddress: null,
            name: 'General Liability Limit of Insurance',
            amountPerOccurrence: 1000000,
            amountInAggregate: 3000000
          },
          {
            locationAddress: null,
            name: 'Medical Payments Limit',
            amountPerOccurrence: 10000,
            amountInAggregate: null
          },
          {
            locationAddress: null,
            name: 'Personal and Advertising Injury Limit',
            amountPerOccurrence: 1000000,
            amountInAggregate: null
          },
          {
            locationAddress: null,
            name: 'Products-Completed Operations Limit',
            amountPerOccurrence: 1000000,
            amountInAggregate: 2000000
          },
          {
            locationAddress: null,
            name: 'Sexual Abuse & Molestation Limit',
            amountPerOccurrence: 300000,
            amountInAggregate: 600000
          }
        ],
        adjustments: {
          ACCOUNT_CREDIT_DISCOUNT_VALUE: -31.649000000000022
        },
        annualPremium: 601.33,
        underwritingNotes: {}
      },
      {
        id: '2d0fec86-cc0f-4f24-b414-0760a82fad02',
        productName: 'Property',
        limits: [
          {
            locationAddress: {
              street: '1 Main St',
              city: 'Cleveland',
              state: 'OH',
              zipCode: '45001',
              country: 'US'
            },
            name: 'All Other Perils Deductible',
            amountPerOccurrence: 1000,
            amountInAggregate: null
          },
          {
            locationAddress: {
              street: '1 Main St',
              city: 'Cleveland',
              state: 'OH',
              zipCode: '45001',
              country: 'US'
            },
            name: 'Business Personal Property Limit',
            amountPerOccurrence: 20000,
            amountInAggregate: null
          }
        ],
        adjustments: {
          ACCOUNT_CREDIT_DISCOUNT_VALUE: -6.620000000000006
        },
        annualPremium: 125.78,
        underwritingNotes: {}
      }
    ],
    quotesAnnualPremium: 1183.16,
    quotesPremiumFinanceEstimate: {
      downPaymentAmount: 236.63,
      financedAmount: 946.53,
      installmentAmount: 106.62,
      numInstallments: 10,
      firstInstallmentDueDateTimestamp: 1740960000000
    }
  },
  policies: []
});

Data Share

Authentic Application

Benefits of Pre-filling:

Every application has three distinct parts:

Getting started with prefilling data

Data Sharing via URL

SMB Class Codes

Class codes Authentic accepts:

Data Capture (Easy Webhook Set Up)

Data events

Set up

Data Capture (Easy Webhook Set Up)

Data events

Set up

Data Sharing via URL

Data Share

Authentic Application

Benefits of Pre-filling:

Every application has three distinct parts:

Getting started with prefilling data

SMB Class Codes

Class codes Authentic accepts:

Data Sharing via Widget

Commonly Prefilled Questions

Lead Fields

Policy Fields

Exposure Fields (Business Locations per Operation)

Fields for Widget Integration

Policy Fields

Sample Webhook Events

Sample payloads

Data Share

hashtagAuthentic Application

hashtagBenefits of Pre-filling:

hashtagEvery application has three distinct parts:

hashtagGetting started with prefilling data

Data Sharing via URL

SMB Class Codes

hashtagClass codes Authentic accepts:

Data Capture (Easy Webhook Set Up)

hashtagData events

hashtagSet up

Data Capture (Easy Webhook Set Up)

hashtagData events

hashtagSet up

Data Sharing via URL

Data Share

hashtagAuthentic Application

hashtagBenefits of Pre-filling:

hashtagEvery application has three distinct parts:

hashtagGetting started with prefilling data

SMB Class Codes

hashtagClass codes Authentic accepts:

Data Sharing via Widget

Commonly Prefilled Questions

hashtagLead Fields

hashtagPolicy Fields

hashtagExposure Fields (Business Locations per Operation)

hashtag Fields for Widget Integration

hashtagPolicy Fields

Sample Webhook Events

hashtagSample payloads

Authentic Application

Benefits of Pre-filling:

Every application has three distinct parts:

Getting started with prefilling data

Class codes Authentic accepts:

Data events

Set up

Data events

Set up

Authentic Application

Benefits of Pre-filling:

Every application has three distinct parts:

Getting started with prefilling data

Class codes Authentic accepts:

Lead Fields

Policy Fields

Exposure Fields (Business Locations per Operation)

Fields for Widget Integration

Policy Fields

Sample payloads